Files
explorer-monorepo/frontend/ROUTING_CONVENTIONS.md
defiQUG f46bd213ba refactor: rename SolaceScanScout to Solace and update related configurations
- Updated branding from "SolaceScanScout" to "Solace" across various files including deployment scripts, API responses, and documentation.
- Changed default base URL for Playwright tests and updated security headers to reflect the new branding.
- Enhanced README and API documentation to include new authentication endpoints and product access details.

This refactor aligns the project branding and improves clarity in the API documentation.
2026-04-10 12:52:17 -07:00

35 lines
1.3 KiB
Markdown

# Explorer Routing Conventions
This frontend intentionally uses one canonical public route per explorer surface.
## Canonical Paths
- Collections are plural: `/blocks`, `/transactions`, `/addresses`, `/tokens`, `/operations`
- Dynamic page segments are named for the identifier they accept:
- `/blocks/[number]`
- `/transactions/[hash]`
- `/addresses/[address]`
- `/tokens/[address]`
- Search is first-class and canonical at `/search`
## Legacy Aliases
- `/more` is a compatibility alias only.
- The canonical route is `/operations`.
- New links, UI copy, docs, and static assets should point to `/operations`.
## Navigation Rules
- Use named buckets instead of vague overflow labels.
- Prefer `Explore`, `Data`, and `Operations` over catch-all labels like `More`.
- If a route appears in the navbar, use the same label everywhere else unless there is a strong product reason not to.
## Router Guardrail
The canonical public router is `src/pages`.
- New public routes should be added in `src/pages` unless there is a compelling architectural reason not to.
- `src/app/globals.css` remains the shared stylesheet source and is imported from `src/pages/_app.tsx`.
- New route aliases should be handled centrally in `next.config.js` redirects.
- Avoid introducing duplicate public routes that expose the same content under different names.