--- title: "Docs Feature Coverage Audit Implementation Plan" description: "For agentic workers Use superpowersexecuting-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking." canonical_url: "https://support.3dimli.com/superpowers/plans/2026-07-08-docs-feature-coverage-audit" md_url: "https://support.3dimli.com/superpowers/plans/2026-07-08-docs-feature-coverage-audit.md" source: "docs/superpowers/plans/2026-07-08-docs-feature-coverage-audit.md" x_aeo_version: "1.0" estimated_tokens: 1649 --- # Docs Feature Coverage Audit Implementation Plan > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Audit `D:\3DBAE\3DIMLI-Docs` against the app repo at `D:\3DBAE\3DIMLI` and add missing user-facing feature coverage using the existing Docusaurus docs organization. **Architecture:** Keep helpdesk docs audience-first. Put product creation content under `creating-products`, role workflows under `managing-your-dashboard`, external/provider setup under `integrations` or payment-gateway settings, and short procedural articles under `Guides` only when they are cross-sectional. **Tech Stack:** Docusaurus 3, Markdown/MDX docs, filesystem-generated sidebars, category metadata in `_category_.json`, validation through `npm run typecheck` and `npm run build`. --- ### Task 1: Booking Product Coverage **Files:** - Create: `docs/creating-products/booking.md` - Create: `docs/managing-your-dashboard/seller-area/booking/_category_.json` - Create: `docs/managing-your-dashboard/seller-area/booking/overview.md` - Create: `docs/managing-your-dashboard/seller-area/booking/availability.md` - Create: `docs/managing-your-dashboard/seller-area/booking/bookings-calendar.md` - Create: `docs/managing-your-dashboard/meetings.md` - Modify: `docs/creating-products/overview.md` - Modify: `docs/getting-started/Why-3DIMLI.mdx` - Modify: `docs/faq/general-questions/platform-basics.md` - [x] **Step 1: Confirm source facts** Read `prisma/schema/booking.prisma`, the `ProductType.Booking` enum, the seller booking route list, and `D:\3DBAE\3DIMLI\docs\booking-product-type\README.md`. - [x] **Step 2: Add product type page** Document what a Booking product is, seller prerequisites, core settings, buyer flow, supported meeting/location modes, payments, refund/access notes, and related pages. - [x] **Step 3: Add seller booking dashboard pages** Cover catalog/service types, availability schedules, date overrides, bookings/calendar, workflows/reminders at a high level, and appearance settings. - [x] **Step 4: Add buyer meetings page** Explain where purchased appointments, webinars, and sessions appear and how buyers find access details. - [x] **Step 5: Cross-link** Add Booking to product-type lists and platform-basics docs. ### Task 2: Website Builder Coverage **Files:** - Create: `docs/managing-your-dashboard/website-builder/_category_.json` - Create: `docs/managing-your-dashboard/website-builder/overview.md` - Create: `docs/managing-your-dashboard/website-builder/pages.md` - Create: `docs/managing-your-dashboard/website-builder/content-blocks.md` - Create: `docs/managing-your-dashboard/website-builder/website-options.md` - Modify: `docs/Guides/customize-store-branding.md` - [x] **Step 1: Confirm source facts** Read website-builder routes, `prisma/schema/website_builder.prisma`, and current app docs under `D:\3DBAE\3DIMLI\docs\website-builder`. - [x] **Step 2: Add role-neutral dashboard section** Document Pages, Content Blocks, and Website Options for both seller and buyer website-builder routes, including draft/unpublished/published behavior and home page basics. - [x] **Step 3: Cross-link store branding** Point branding readers to Website Options when they need page/theme-level customization. ### Task 3: Dashboard Assistant and BYOK Coverage **Files:** - Create: `docs/managing-your-dashboard/assistant.md` - Create: `docs/managing-your-dashboard/settings/ai-provider-keys.md` - Modify: `docs/integrations/3dimli-mcp-connector.mdx` - Modify: `docs/creating-products/AI-Optimization.md` - [x] **Step 1: Confirm source facts** Read `prisma/schema/assistant.prisma`, assistant dashboard routes, BYOK provider-key UI, and `knowledge-base/ai/dashboard-assistant-design.md`. - [x] **Step 2: Add assistant docs** Explain the in-dashboard assistant, local browser chat history, starter allowance, BYOK provider keys, zero-data-retention marking, docs search, and confirmed-action behavior. - [x] **Step 3: Clarify MCP vs dashboard assistant** Update MCP docs so users understand when to use the remote connector versus the in-dashboard assistant. ### Task 4: Payment Gateway Coverage Update **Files:** - Modify: `docs/managing-your-dashboard/settings/payment-gateway/overview.md` - Create: `docs/managing-your-dashboard/settings/payment-gateway/link-paystack-account.md` - Create: `docs/managing-your-dashboard/settings/payment-gateway/link-octo-account.md` - Create: `docs/managing-your-dashboard/settings/payment-gateway/link-freedompay-account.md` - Modify: `docs/getting-paid/countries-and-paymentmethods.md` - [x] **Step 1: Confirm source facts** Read `PaymentGatewayName`, seller settings gateway wrappers, and gateway implementation notes for Paystack, Octo, and FreedomPay. - [x] **Step 2: Update gateway matrix** Reflect current gateway names, connection method, gateway availability, and the one-active-gateway rule. - [x] **Step 3: Add missing setup pages** Document user-facing setup steps without exposing internal trust-model details that are not useful to sellers. ### Task 5: Verification and Repeat Audit **Files:** - Modify as discovered by build/link errors. - [x] **Step 1: Run docs checks** Run `npm run typecheck` and `npm run build`. - [x] **Step 2: Review changed-file navigation** Confirm new docs appear through generated sidebars and no broken links are introduced. - [x] **Step 3: Repeat route-vs-doc gap scan** Re-run the app route inventory and docs keyword scan for remaining uncovered surfaces, then create the next batch if high-value gaps remain. ### Task 6: API Tokens Coverage **Files:** - Create: `docs/managing-your-dashboard/settings/api-tokens.md` - Modify: `docs/managing-your-dashboard/settings/_category_.json` - Modify: `docs/managing-your-dashboard/settings/integrations.md` - Modify: `docs/integrations/3dimli-mcp-connector.mdx` - Modify: `docs/getting-started/SettingUpYourStore.md` - [x] **Step 1: Confirm source facts** Read buyer and seller API token routes, the shared token settings component, seller license-verification token component, and token action behavior. - [x] **Step 2: Add settings page** Document MCP tokens, full vs custom scopes, persistent vs 180-day expiry, one-time token display, revoke/regenerate behavior, and seller license-verification tokens. - [x] **Step 3: Cross-link** Link API Tokens from Settings Integrations, MCP docs, and stale seller setup payment-method guidance.