{"id":"md_hello-world","slug":"hello-world","section":"md","title":"Hello World — Content Engine","renderMode":"prose","content":"\nThis is THE **Content Engine** — a minimal Next.js application that renders Markdown and HTML artifacts through a unified URL scheme.\n\n## What It Proves\n\nThe reader's experience is **format-agnostic**. Whether the content was written in Markdown or exported as a self-contained HTML file, the URL is the same and the presentation is consistent.\n\n- `/blog/hello-world` — this post, rendered from Markdown\n- `/showcase/dashboard-demo` — an HTML artifact, rendered in an iframe\n\n## Features\n\n### Markdown Support\n\nThis engine uses **ReactMarkdown** with **remark-gfm** for GitHub-flavored Markdown:\n\n- Tables\n- Strikethrough\n- Task lists\n- Autolinks\n\n### Code Blocks\n\n```typescript\n// Example code block\nfunction greet(name: string): string {\n  return `Hello, ${name}!`;\n}\n```\n\n### Blockquotes\n\n> \"The reader cannot tell (and does not care) which format produced the page.\"\n> — Architectural Duality Document\n\n### Lists\n\n1. Standalone proof-of-concept\n2. DB cache layer (Molino integration)\n3. GAS DocAPI ingestion\n4. Auth-gated Studio\n\n- No GAS dependency in standalone mode\n- Filesystem is the source of truth\n- Git-tracked and version-controlled\n\n## Next Steps\n\n1. Build the standalone app\n2. Verify `/blog/hello-world` renders\n3. Add an HTML artifact to `/showcase/`\n4. Integrate into Molino staging\n\n---\n\n*This document is part of the Content Engine specification.*","metadata":{"author":"","date":"2026-07-04T06:57:53.332Z","tags":[],"readingTime":2,"title":"Hello World — Content Engine"}}