Quick Start
Get the portal running locally, verify key routes, and run the same checks used before push.
Browse implementation guides for Next.js App Router, TypeScript, metadata SEO, UI architecture, and PM2 release operations. Each article includes practical sections, command snippets, and related reading paths.
Start with this recommended path to understand setup, architecture, and release flow without context switching.
Get the portal running locally, verify key routes, and run the same checks used before push.
Use one checklist for pre-deploy, restart, and post-deploy checks.
Install dependencies with reproducible settings and verify build readiness.
Tune search relevance, filtering behavior, and fallback paths.
Restart and verify the portal safely with PM2.
Configure site URL and runtime flags without exposing secrets.
Run and inspect production build output before restart.
Follow a consistent branch-to-validation loop for daily work.
Render readable examples with clear labels and reliable copy actions.
Implement dark/light persistence without hydration flicker.
Configure metadata, robots, and canonical URLs for public indexing.
Use a predictable error payload so UI states and retries are deterministic.
Use a small curl matrix to validate critical public routes.
Apply tokens for spacing, color, and typography across docs UI.
Document naming, ownership, and commit conventions used in this codebase.
Keep header, sidebar, and footer navigation consistent across routes.
Design stable list responses for query, filters, and sorting.
Apply keyboard, focus, and semantic patterns in docs pages.
Track each request from route handler to rendered state and logs.
Structure docs fields for cards, article pages, and search.
Keep route payloads and UI consumers aligned with shared TypeScript types.
Keep changelog entries factual and tied to shipped scope.
Design no-results states that help users recover quickly.
Prepare rollback steps when release quality drops.