What exists, what is next, and what is deliberately out of scope.
Now
Status: 0.1.0. pholio init creates a project, pholio dev previews it
while you edit, pholio build writes the static site and pholio check
compares a build with committed output. The content format covers every
component on the
components page, and every build publishes the files AI
agents look for.
Next
- Link and image checks. Stop the build on an internal link to a page that
doesn't exist, on a missing image and on a
Screenshotwhose dark image is missing. - The planned keys.
base_urlwith canonical links and Open Graph;theme.default_schemeandtheme.custom_css;search.enabled; icon links innav;strict_content. - Extension points.
slotsfor sidebar, table of contents and page footer, andcomponentsfor tags registered in PHP. - More languages. Interface translations beyond English and German, and more bundled grammars for code blocks.
- More consumers, to find the assumptions that only look general.
Out of scope
These are decisions, not omissions.
- No source extraction. No docblock parsing, no API reference generation. Documentation is written, not derived.
- No MDX. Tags carry attributes and nest; they never import or evaluate.
- No runtime PHP. The output is static files. A PHP runtime in production is never required.
- No package manager. Pholio is copied in, not installed. That is what "zero dependencies" has to mean to be worth saying.