This docs surface now connects the docs folder, product modules, code paths, and delivery tracks so the next action is always visible.
documentation lanes
product modules
edit surfaces
active locales
Read the structure map, open the paired task trackers, edit the right code surface, then finish with build verification and worklog updates.
Confirm the source of truth
Open the structure map, PRD, menu, and architecture docs before changing product behavior.
Choose the paired trackers
Open both the development-track checklist and the task completion file for the module you are touching.
Implement in the right layer
Move from route surface to query flow to database only when the change truly requires it.
Verify and document the finish
Build, smoke-check, update task progress, and record the work so the docs stay as current as the code.
Documentation lanes
Use four lanes so strategy, implementation, and operations stay connected instead of becoming separate piles of files.
Docs lane
Fix product intent, structure, and operating rules before a page or API starts drifting.
Outcome
Shared source of truth for product direction and system shape
Docs lane
Define visual language, page mood, image plans, and experience-level expectations for public surfaces.
Outcome
Premium UI direction that stays anchored to brand and feature intent
Docs lane
Pair step-by-step implementation checklists with task completion files so status and finish quality are both visible.
Outcome
Execution rhythm, progress visibility, and completion-first discipline
Docs lane
Keep setup, database policy, deployment flow, and recovery steps reproducible as the app grows.
Outcome
Operational consistency across development, database, and deployment work
Program module atlas
Each public or member-facing module now points back to the route, the primary code surface, and the tracking document that should be updated with it.
Landing, platform story, premium brand direction, and entry routing.
Primary code
src/app/[locale]/page.tsx
Tracking doc
docs/task/01-home.md
Publishing, official news, tutorials, detail pages, and editorial UX.
Primary code
src/app/[locale]/posts/*
Tracking doc
docs/task/02-posts.md
Collaboration boards, recruitment flow, and team-first discovery.
Primary code
src/app/[locale]/projects/*
Tracking doc
docs/task/03-projects.md
Room discovery, live participation, and streaming-oriented collaboration.
Primary code
src/app/[locale]/live/*
Tracking doc
docs/task/04-live.md
Rooms, language spaces, moderation rules, and social alignment.
Primary code
src/app/[locale]/community/*
Tracking doc
docs/task/05-community.md
Guides, platform understanding, and the structured starting point for contributors.
Primary code
src/app/[locale]/docs/*
Tracking doc
docs/task/06-docs-guide.md
Human-centered campaigns, premium trust visuals, and transparent support flow.
Primary code
src/app/[locale]/volunteer/*
Tracking doc
docs/task/10-volunteer.md
Authenticated overview, user actions, profile, live control, and workspace tools.
Primary code
src/app/[locale]/dashboard/*
Tracking doc
docs/task/07-auth-profile.md
Where we edit
Keep each change inside the right surface so route logic, data policy, copy, images, and verification can evolve without becoming tangled.
Page composition, loading and empty states, metadata, and UI-level behavior.
Query composition, permission-aware data flow, and server-side business rules.
Schema, procedures, reproducible SQL, and database operating rules.
Locale-specific messaging, fallback quality, and contributor-facing clarity.
Local-first public imagery, SVG support artwork, and sourcing history.
Execution sequence
This is the working order that keeps docs, implementation, and verification aligned every time we push a module forward.
Open the structure map, PRD, menu, and architecture docs before changing product behavior.
Open both the development-track checklist and the task completion file for the module you are touching.
Move from route surface to query flow to database only when the change truly requires it.
Build, smoke-check, update task progress, and record the work so the docs stay as current as the code.
