docs(roadmap): mdx-content-system phase + GSC-validated content paths - #500
docs(roadmap): mdx-content-system phase + GSC-validated content paths#500bntvllnt wants to merge 2 commits into
Conversation
90d GSC analysis (sc-domain:ui.vllnt.ai/.com) of real search demand:
- seo-content-engine: SYNC note with the highest-impact CAPTURE paths
the data proves and that don't exist yet (/alternatives/radix,
/alternatives/mui, a /react/{component} framework-qualified
namespace), plus the honest finding that "AI UI development" has
zero head-term demand today — a recall/GEO bet, not a capture play.
- Later: multiselect + filter-bar component gaps (GSC demand exists,
no component in the registry today).
Planning/analysis only — no page built (per direction).
|
ntk preview
Built from |
…aths
Adds the full MDX-max plan and the GSC-validated SEO paths as roadmap
work, per the roadmap convention.
New phase `mdx-content-system` [PLANNED] (7 tasks, sequenced before
seo-content-engine):
- Shared MDX component map, extended frontmatter schema (JSON-LD from
frontmatter), generic /guides|/vs|/react [slug] shells, sitemap via
content glob, an author guard for the MDX evaluate() bracket hazard,
and migration of the 3 shipped TSX /vs pages onto the MDX shell.
- Outcome: a new content page = one .mdx file drop (no TSX, no sitemap
edit), i18n-ready via fr.mdx with zero code change.
seo-content-engine: +7 tasks (.9-.15) for the GSC-proven paths —
/vs/radix, /vs/mui, /react/{callout,floating-action-button,code-block},
/guides/ai-ui pillar (+ mobile coming-soon), /guides/streaming-ui +
/guides/design-tokens, and the assistant-ui namespace migration.
Namespace decisions recorded: /vs = tools+libs, /alternatives =
direct competitors, /integrations = how-to-use, /guides = evergreen
reference, /blog = dated articles.
bntvllnt
changed the title
Review disposition: keep draft, bounded rework before readyVerdict: do not close as stale/superseded. The roadmap direction still fits the current Blocking before ready:
Verified clean:
Validation evidence:
No merge/release action taken. This is a draft-disposition comment, not an approval. |
1 participant
What
Adds the MDX-max content architecture and the GSC-validated SEO paths to
ROADMAP.md, per the roadmap convention. Docs-only — no code, no pages built.Why
Asked to propose new site paths to improve SEO/impact, grounded in real Search Console data. A 90d GSC pull (
sc-domain:ui.vllnt.ai/.com) drove every path below.New phase —
mdx-content-system[PLANNED]Sequenced before
seo-content-engine(which now declaresneeds:it). 7 tasks:ComponentGrid,CompareTable,Faq, …) — today every caller passes the empty default, which is the real gappageFrontmatterSchema(faq[],componentSlugs[],type: +guide|vs|react) → JSON-LD emitted by the shell from frontmatter, never the MDX body/guides/[slug],/vs/[slug],/react/[slug]shells → a new page is one.mdxfile drop (no TSX, nostaticRoutes()edit)content/pages/**globevaluate()hazard (inline`<X>`code-spans break JSX pages)/vspages onto the MDX shell, URLs unchangedInfra discovery:
MDXContentalready supports acomponentsmap +enableMDX(auto-detects JSX, falls back toReactMarkdown+remarkGfm), andgetPageContentalready falls back<locale>.mdx→ default → flat. i18n is opt-in per page: shipen.mdx, addfr.mdxlater with zero code change.seo-content-engine— +7 tasks (.9–.15)/vs/radix/vs/mui/vs/assistant-ui→/alternatives/assistant-ui+ 301/react/{callout,floating-action-button,code-block}react <component>/guides/ai-uipillar (+ mobile coming-soon)/guides/streaming-ui,/guides/design-tokensNamespace decisions recorded
/vs= tools+libs ·/alternatives= direct competitors ·/integrations= how-to-use ·/guides= evergreen reference ·/blog= dated articles.Also
Later:multiselect+filter-bar— GSC demand with no component today.Pre-existing drift found (flagged, NOT fixed here)
family-pages,component-sidebar) — convention says exactly one.docs/specs/doesn't exist — all 5 spec refs dangle; 3 pre-date this PR.Notes
Closes #Nbefore merge (kept draft).