Cookest
Contributing

Documentation Roadmap

Coverage snapshot, priorities, and contribution workflow for Cookest documentation

Documentation Roadmap

This page tracks current documentation coverage across the Cookest docs site and highlights what should be written next.

Legend: ✅ Complete = current and usable, 🔄 Partial = exists but needs expansion or refresh, ❌ Missing = planned but not yet documented.

Coverage matrix

SectionPageStatusNotes
Rootindex🔄 PartialGood landing page, but ecosystem summary can still be expanded.
Rootroadmap🔄 PartialProduct roadmap exists, but it is separate from docs coverage planning.
User Guideoverview✅ CompleteSolid entry page for end-user docs.
User Guideregistration✅ CompleteCovers onboarding flow.
User Guidemeal-planning✅ CompleteCore user journey is documented.
User Guidepantry✅ CompletePantry workflows are covered.
User Guideshopping✅ CompleteShopping-list flow is documented.
User Guidecooking-mode✅ CompleteDetailed cooking walkthrough exists.
Architectureoverview✅ CompleteGood system-level intro.
Architecturerepositories✅ CompleteUpdated for the multi-crate backend workspace and image-gen service.
Backendgetting-started✅ CompleteSetup path is documented.
Backendenvironment✅ CompleteIncludes App API image-gen configuration.
Backendauthentication✅ CompleteAuth flow is covered.
Backendfood-api✅ CompleteNow includes the App API browse proxy note.
Backenddatabase✅ CompleteSchema coverage exists.
Backendpdf-pipeline✅ CompletePDF ingestion pipeline is documented.
Backend / Endpointsindex✅ CompleteEndpoint map includes image generation.
Backend / Endpointsauth✅ CompleteStable and documented.
Backend / Endpointsprofile✅ CompleteStable and documented.
Backend / Endpointsrecipes🔄 PartialAI generation is now covered, but older recipe examples still need a full source-backed refresh.
Backend / Endpointsimage-generation✅ CompleteNew async image-generation page added.
Backend / Endpointsmeal-plans✅ CompleteStable and documented.
Backend / Endpointsinventory✅ CompleteStable and documented.
Backend / Endpointsshopping-list✅ CompleteStable and documented.
Backend / Endpointssubscription✅ CompleteStable and documented.
Backend / Endpointsstores✅ CompleteStable and documented.
Backend / Endpointsai-chat✅ CompleteRequest/response shapes and agentic tools are now source-aligned.
Mobileoverview✅ CompleteHigh-level app documentation exists.
Mobilearchitecture✅ CompleteScreen/state layering is documented.
Mobilescreens✅ CompleteIncludes Generate Recipe and image-generation updates.
Mobiletheme✅ CompleteDesign system guidance is present.
Mobilestate-management✅ CompleteRiverpod structure is documented.
Mobileapi-integration✅ CompleteAPI wiring is documented.
ETLoverview✅ CompleteCovers the pipeline clearly.
CUCLoverview✅ CompleteGood library intro.
CUCLdesign-tokens✅ CompleteToken documentation exists.
CUCLcomponents✅ CompleteExpanded to cover the full 50-component library.
CUCLbest-practices✅ CompleteUsage guidance exists.
CUCLcontributing✅ CompleteContribution entry point exists.
AI & Automationquick-setup✅ CompleteUseful onboarding page.
AI & Automationoverview✅ CompleteGood section overview.
AI & Automationskills🔄 PartialNeeds periodic refresh as skill inventory changes.
AI & Automationinstructions🔄 PartialUseful, but should stay aligned with active agent conventions.
AI & Automationmcp-server🔄 PartialShould be revisited when tools or auth flows change.
AI & Automationauto-docs✅ CompleteCovers the automation workflow.
Contributingguide✅ CompleteCore authoring rules are documented.
Contributingbest-practices✅ CompleteWriting best practices exist.
Contributingtranslations🔄 PartialProcess exists, but language coverage is still uneven.
Contributingdocs-architecture✅ CompleteTechnical docs-site structure is documented.
Contributingdocs-roadmap✅ CompleteThis coverage tracker page.
Legacy UI Componentsoverview🔄 PartialOlder section overlaps with CUCL and should eventually be consolidated.
Legacy UI Componentsdesign-tokens🔄 PartialStill useful, but duplicated by CUCL docs.
Legacy UI Componentsreact🔄 PartialBasic getting-started guide only.
Legacy UI Componentsflutter🔄 PartialBasic getting-started guide only.
Legacy UI Componentscli🔄 PartialUseful but narrow.
Legacy UI Componentscomponents🔄 PartialLegacy reference that overlaps with cucl/components.
PT mirrorpt/index✅ CompleteLanding page exists.
PT mirrorpt/user-guide/*✅ CompleteCore user-guide mirror exists.
PT mirrorpt/backend/*🔄 PartialBackend mirror exists, but recent endpoint updates are not fully mirrored yet.
PT mirrorpt/mobile/*✅ CompleteMain mobile section is mirrored.
PT mirrorpt/cucl/*🔄 PartialCore pages exist, but the component reference now lags EN.
PT mirrorpt/contributing/*🔄 PartialGuide exists, but roadmap parity is missing.
DEde/index🔄 PartialOnly the landing page exists.
ESes/index🔄 PartialOnly the landing page exists.
FRfr/index🔄 PartialOnly the landing page exists.
Plannedpt/backend/endpoints/image-generation❌ MissingPortuguese mirror for the new image-generation page.
Plannedpt/backend/endpoints/ai-chat refresh❌ MissingNeeds the corrected request/response schema and tool list.
Plannedpt/backend/endpoints/recipes refresh❌ MissingNeeds the AI recipe generation section.
Plannedpt/contributing/docs-roadmap❌ MissingPortuguese roadmap parity.
Plannedmobile/demo-mode❌ MissingDemo mode deserves its own page or subsection.
Plannedbackend/browse-proxy❌ MissingCould be broken out into a dedicated App API proxy page.
Plannedarchitecture/deployment❌ MissingRepo relationships are covered, but deployment topology is not.

Priority tiers

P0 — Write next

  • Portuguese parity for the updated English backend endpoint pages
  • Portuguese mirror for contributing/docs-roadmap
  • English page for mobile demo mode and MockApiInterceptor

P1 — High-value follow-ups

  • Dedicated deployment/runtime architecture page
  • Dedicated browse-proxy page for App API ↔ Food API routing
  • Deeper image-gen microservice internals (queueing, job lifecycle, storage)

P2 — Nice-to-have improvements

  • Refresh diagrams with more runtime detail
  • Add screenshots or UI captures to high-traffic mobile pages
  • Consolidate or cross-link the legacy ui-components/ section with CUCL

How to contribute docs

  1. Start with Documentation Guide.
  2. Verify every API field, component prop, or workflow against source code before writing.
  3. Keep pages in Fumadocs-style MDX and use callouts for important warnings/info.
  4. Update the relevant meta.json whenever you add a new page.
  5. If you add or update an English page, plan the Portuguese mirror as part of the same docs batch whenever possible.
  6. Re-scan edited files for stale examples, wrong field names, or leftover legacy terminology before opening a PR.

Do not guess request/response fields or component props. If a detail is uncertain, verify it in source first or mark it for follow-up in this roadmap.

On this page