NNexusDocumentation
Live demo
GuideCustomize

Remove Demo Content

Safely remove sample routes, catalogs, data, and assets after your real application structure is ready.

8 min readCustomizeUpdated for Nexus 0.1
On this page 4

What you will learn

  • Remove unused modules without broken links.
  • Identify catalog-driven references.
  • Keep the build and release clean.

Remove in dependency order

A route may also be referenced by navigation, topbar search, documentation, tests, or a catalog. Remove references before deleting the page.

  1. Remove the sidebar item from lib/navigation.ts.
  2. Remove related entries from the matching lib/*-catalog.ts file.
  3. Remove links from pages and components.
  4. Remove or update tests that intentionally cover that feature.
  5. Delete the unused route and feature component.
  6. Remove assets only after confirming no remaining reference.
  7. Run pnpm check.

Find references

Search by both route and component name before deletion.

bash
rg -n "/calendar|CalendarShowcase|calendar-" app components lib tests

Keep useful foundations

A demo page can be removed while its general-purpose patterns remain useful. Keep shared dialog, form, table, status, and responsive patterns if real features depend on them.

Continue learning