← Back to marketplace

Parser build queue

26 targets across 4 waves, drawn from the PRD's 249-site SaaS research. Waves run by descending aggregate coverage — pick the top unbuilt target in the earliest wave.

0 of 26 parsers shipped · 0 of 26 signatures verified. See coverage map →

Wave 1

Docs platforms, high-leverage

5 targets · 121 sites covered

  • nextjsdocs
    55 sites observed

    __NEXT_DATA__ script payload; MDX-driven routes

    Sig: plannedParser: planned
  • mintlifydocs
    36 sites observed

    x-mintlify-client-version response header; /llms.txt present

    Sig: plannedParser: planned
  • docusaurusdocs
    17 sites observed

    <meta name="generator"> (verify strippable signal)

    Sig: plannedParser: planned
  • readmedocs
    7 sites observed

    footer attribution plus files.readme.io CDN host

    Sig: plannedParser: planned
  • gitbookdocs
    6 sites observed

    x-gitbook-route-site response header

    Sig: plannedParser: planned
Wave 2

Docs platforms, long tail

9 targets · 33 sites covered

  • zendesk-guidedocs
    7 sites observed

    via: zorg response header for help portals

    Sig: plannedParser: planned
  • hugodocs
    5 sites observed

    generator meta tag (verify strippable signal)

    Sig: plannedParser: planned
  • sphinxdocs
    5 sites observed

    Python ecosystem theme markers; Sphinx or Read the Docs generator meta

    Sig: plannedParser: planned
  • mkdocsdocs
    5 sites observed

    Python ecosystem theme markers; MkDocs generator meta

    Sig: plannedParser: planned
  • ferndocs
    3 sites observed

    footer or asset attribution

    Sig: plannedParser: planned
  • antoradocs
    3 sites observed

    Asciidoc-based multi-version docs markup

    Sig: plannedParser: planned
  • astrodocs
    3 sites observed

    _astro/ asset paths or generator meta

    Sig: plannedParser: planned
  • vitepressdocs
    1 sites observed

    <meta name="generator" content="VitePress">

    Sig: plannedParser: planned
  • nextradocs
    1 sites observed

    Next.js-based MDX docs framework marker

    Sig: plannedParser: planned
Wave 3

CMS-backed Resources and Blog, high-leverage

5 targets · 85 sites covered

  • wordpressresources
    38 sites observed

    /wp-json/wp/v2/posts REST API plus /feed/

    Sig: plannedParser: planned
  • sanityresources
    21 sites observed

    cdn.sanity.io asset host

    Sig: plannedParser: planned
  • contentfulresources
    16 sites observed

    images.ctfassets.net asset host

    Sig: plannedParser: planned
  • hubspot-cmsresources
    6 sites observed

    hs-scripts and hs-forms markers

    Sig: plannedParser: planned
  • webflow-cmsresources
    4 sites observed

    cdn.prod.website-files.com asset paths

    Sig: plannedParser: planned
Wave 4

CMS-backed Resources and Blog, long tail

7 targets · 15 sites covered

  • notion-cmsresources
    5 sites observed

    embedded Notion content blocks inside Webflow or Next.js fronts

    Sig: plannedParser: planned
  • payloadresources
    3 sites observed

    backend CMS for Next.js fronts

    Sig: plannedParser: planned
  • contentstackresources
    2 sites observed

    images.contentstack.io asset host

    Sig: plannedParser: planned
  • prismicresources
    2 sites observed

    asset-host or API signature

    Sig: plannedParser: planned
  • strapiresources
    1 sites observed

    backend CMS for Next.js fronts

    Sig: plannedParser: planned
  • datocmsresources
    1 sites observed

    asset-host signature

    Sig: plannedParser: planned
  • storyblokresources
    1 sites observed

    asset-host signature

    Sig: plannedParser: planned

Status pills show the effective state derived from this marketplace's inventory and the live signature registry, not the static fields on the upstream PARSER_ROADMAP constant. Hover a pill that disagrees with upstream to see both values. Generated 2026-06-29T13:02:15.015Z.