PHACKTS Documentation Engine
This example demonstrates every capability of the PHACKTS content system. Every word you see on this page comes from content.json — a single, human-readable data file. The rendering engine reads this file and produces a complete, SSR-first documentation site with zero hardcoded prose.
Inline Segments
Every paragraph is an array of segments. Segments compose — you can combine properties to create rich inline content without any shortcodes or HTML.
Terms & Definitions
Add "term" to any segment to create a hover tooltip. On desktop, a card appears above the word. On mobile, a centered definition card appears. Try hovering over this term to see it in action. Terms are rendered as <dfn> elements for semantic correctness, and they’re keyboard-focusable for accessibility.
Links & Code
Add "href" for links: PHACKTS on Codeberg. External links automatically open in new tabs. Add "code": true for inline code like npm run build or file names like index.html. Add "strong": true for bold emphasis.
Properties compose. This is a linked code term — three properties on a single segment, all rendering correctly.
Danger Highlights
Code segments can be highlighted with semantic colors. The "highlight": "danger" property produces a red warning badge, useful for marking things users should avoid:
Content Blocks
Sections contain an array of blocks. Each block type serves a different structural purpose.
Callout Blocks
Four callout styles are available, each with its own color and icon:
Code Blocks
Code blocks render with a language label and a copy-to-clipboard button:
Cards wrap blocks in a styled container. Here’s a card containing a heading and a code block:
Quick Start
Support Cards
The "support" block type renders contact cards with action buttons. Email, phone, and web types are supported:
Reading List
The "reading-list" block type renders a responsive grid of external links, each with a bullet indicator and hover animation: