pradox_builder

Use case

This very site is built with it. News and projects live as Markdown in an Obsidian vault, the builder renders them to static HTML, served behind an nginx container. Mandatory legal pages (imprint, privacy, cookies) stay hand-written — the builder never touches them.

What's done so far

• Markdown-to-HTML pipeline with bleach allowlist and ReDoS-safe tag stripping
• YAML frontmatter parser, paginated collections for news and projects
• Multi-tag schema with dynamic client-side JS filter (4 top topics)
• Status and source badges on project cards
• Safe sync workflow between Obsidian vault and repo, deploy.sh with selective build-output sync and 18 smoke tests
• 52 pytest tests, Mozilla Observatory A+ on the rendered site

In progress

Frontend polish (card layouts, image workflow), optionally a live preview server for the editor loop, eventually a cheatsheets and blog section.