1---2template: home3slug: /4page_id: home5title: PageQuarry6description: Repo-native publishing for React sites with humans and AI agents sharing one block-based workflow.7---8 9{% hero10    eyebrow="Repo-Native Publishing"11    title="A React Site Framework with a Block-Based Markdown CMS."12    deck="PageQuarry is an open-source React framework for teams that want humans and AI agents publishing in the repo without reopening layout decisions. Developers define blocks, templates, navigation, and SEO in code. Writers and agents fill those blocks in markdown."13    aside="Get Started opens the repo. Look Under the Hood reveals the exact homepage markdown now driving this page."14    actionHref="https://github.com/juan-deere-4000/pagequarry"15    actionLabel="Get Started"16/%}17 18{% metrics %}19{% metric20    label="Runs"21    value="Inside Your React Repo"22/%}23{% metric24    label="Publishing Surface"25    value="Markdown Blocks with Validation"26/%}27{% metric28    label="Shared Workflow"29    value="Humans and Agents Use the Same Path"30/%}31{% /metrics %}32 33{% sectionCopy34    eyebrow="Product Boundary"35    title="What You Actually Install and Run."36%}37PageQuarry is not a hosted admin panel. It is a React codebase with a block-based publishing layer wired into the repo. You clone it, define the presentation system in React, and publish pages from markdown.38 39That boundary matters. React owns layout, templates, navigation, metadata, and styling. Markdown owns content entry inside approved blocks.40 41{% linkItem42    href="/case-studies"43    label="Examples"44    summary="Inspect example patterns and the public artifact behind this site."45/%}46{% linkItem47    href="/howto/editorial/publishing-workflow"48    label="Publishing Guide"49    summary="Read the command flow a human or agent actually follows."50/%}51{% linkItem52    href="/homepage-markdown"53    label="Homepage Markdown"54    summary="Open the exact source currently driving this homepage."55/%}56{% /sectionCopy %}57 58{% sectionCopy59    eyebrow="Agent Workflow"60    title="What an Agent Actually Does."61    tone="subtle"62%}63An agent does not invent a page from scratch. It opens a draft file, calls approved blocks, fills the allowed fields, runs the check command, and submits the page for review. The surrounding design system never moves.64 65The point is to give humans and agents the same constrained publishing surface instead of asking either one to restyle the site on every edit.66 67- Open a draft in submit-here68- Reuse approved blocks instead of inventing layout69- Run the check command before acceptance70- Submit or edit the page into the published archive71{% /sectionCopy %}72 73{% sectionCopy74    eyebrow="React Example"75    title="Define the Presentation Once."76%}77A developer builds the hero, CTA, FAQ, comparison row, or release-note block once. That React component owns spacing, type, interaction states, and visual rhythm.78 79After that, every page can reuse the same presentation instead of re-solving design in content.80{% /sectionCopy %}81 82{% sectionCopy83    eyebrow="Markdown Example"84    title="Publish New Pages Without Opening the Layout."85    tone="subtle"86%}87People and AI tools call that block from markdown by filling approved inputs. The content changes, but the presentation stays locked to the React implementation.88 89That is the core promise of PageQuarry: faster publishing without giving up control of the site.90{% /sectionCopy %}91 92{% sectionCopy93    eyebrow="Supporting Infrastructure"94    title="The Rest of the System Stays Out of the Editor."95%}96Templates, navigation, footer copy, redirects, metadata defaults, and validation live in code. That supporting infrastructure is what makes the markdown surface small enough for fast human and agent edits.97 98- Templates decide which blocks belong on which page types99- Navigation and metadata stay stable across edits100- Published source stays visible and reviewable in the repo101- Validation catches bad routes and broken block calls before they ship102{% /sectionCopy %}103 104{% process105    eyebrow="Publishing Path"106    title="How a Change Moves from Draft to Production."107%}108{% step109    title="Draft the Page"110    body="Start in a markdown draft, choose existing blocks, and fill the content fields those blocks allow."111/%}112{% step113    title="Check and Accept It"114    body="Run the validation step, then submit a new page or edit an existing one into the approved archive."115/%}116{% step117    title="Build from Approved Content"118    body="The live site ships from accepted page data instead of whatever ad hoc working files happen to be in the repo."119/%}120{% /process %}121 122{% quote123    quote="React owns the frame. Markdown owns the fill."124    attribution="PageQuarry"125    context="Product Boundary"126/%}127 128{% cta129    title="Open the Repo and Try the Workflow."130    body="Clone the project, inspect the block system, and ship a page through the same publishing flow this site uses."131    actionHref="https://github.com/juan-deere-4000/pagequarry"132    actionLabel="View on GitHub"133/%}134