Skip to main content

Components Overview

Route: /dev/components-overview

Non-production only

Built-in /dev pages are available only outside production. The shared /dev layout returns notFound() when isProduction() is true; see Environment Helpers.

Components Overview answers one simple question: where is each page-builder component used?

It scans published Strapi pages in the current locale, collects component UIDs from the content dynamic zone, and groups pages under each component. This is useful before changing or removing a component because you immediately see which real pages can be affected.

Components Overview developer page

Why It Is Useful​

When a page-builder component changes, the risk is rarely in the component alone. The risk is in the content already using it.

This page gives you a quick impact map:

  • Which components are still used.
  • Which pages use a given component.
  • Which pages QA should check after a component change.

It is also handy after imports or migrations to confirm that expected component UIDs appear in published content.

Notes​

  • Only published pages are listed.
  • Results are locale-specific.
  • For visual component examples, use Components Showcase.