The Cold War
Guides GitHub

What Is Rezilienz?

Rezilienz is a Flat-file Headless CMS designed for modern content workflows, specifically optimized for long-form editorial content, complex taxonomies, and agent-friendly content delivery.

While it provides a rich administrative interface for content creation, it remains strictly headless in its architecture.

1. Decoupled Architecture

Rezilienz follows the "Headless" philosophy by maintaining a strict separation between the Body (where content is managed) and the Head (where content is presented).

  • The Body (apps/admin): A sophisticated administrative dashboard (Wizard v3) built with Alpine.js and Toast UI. It handles content authoring, media management, and metadata classification.
  • The Head (apps/blog): A dedicated presentation layer that renders content into a beautiful, responsive blog.

Because these are decoupled, you can easily replace the blog head with a mobile app, a static site generator, or a JavaScript framework (Next.js/React) without changing a single line of code in the CMS.

2. API-First Foundation

The core of Rezilienz is its Python API (api/), built with FastAPI.

  • All content operations—creating, updating, and listing pages—happen through standardized endpoints.
  • The admin interface interacts with the system as a "client," just like any third-party application would.
  • The configuration is centralized in config.ini, allowing the system to adapt to different environments without code changes.

3. Flat-File and Git-Friendly

Unlike traditional CMSs that trap content in a relational database, Rezilienz uses a Flat-file storage model.

  • Markdown + YAML: Content is stored as human-readable Markdown files with YAML frontmatter.
  • Version Control: Because content is just files, the entire "database" can be tracked in Git, providing instant versioning, branching, and easy deployments.
  • No DB Overhead: By decoupling from heavy databases (like the original ArangoDB implementation), Rezilienz remains fast, portable, and easy to back up.

4. Agent-Friendly Content Negotiation

Rezilienz is built for the future of the web, where content is consumed by both humans and AI agents.

  • Smart Rendering: The system can detect the Accept header in incoming requests.
  • Markdown Delivery: While humans see a polished HTML page, an AI agent can request text/markdown and receive a perfectly cleaned, token-efficient version of the content optimized for LLM processing.
  • Zero-Overhead Metadata: The "zeroth-article" architecture treats index.md as a manifest entity, ensuring consistent metadata across single posts and complex composite dossiers.

5. Rich Editorial Tools

Despite being headless, Rezilienz does not sacrifice the authoring experience.

  • Wizard v3: A "distraction-free" editor that prioritizes visual hierarchy.
  • Composite Posts: Support for "fragments," allowing long-form content to be managed as multiple related Markdown files while being rendered as a single cohesive unit.
  • Integrated Media Gallery: Direct management of hero images, covers, and inline assets with automatic path resolution.

6. Hybrid Rendering: Dynamic & Static

Rezilienz offers the best of both worlds by providing two distinct modes of operation:

  • Dynamic Head (apps/blog/*.php): A PHP-based head that provides real-time previews, dynamic routing, and sophisticated content negotiation (Markdown for Agents).
  • Static Build (cli-tools/): A high-performance build pipeline that generates a pure static version of the site into apps/blog/dist/. This allows you to host the production site on any simple file server (Nginx, S3, GitHub Pages) while keeping the dynamic CMS on a protected internal server.

7. "Antisocial-Friendly" (Resilient) Philosophy

Rezilienz is designed for a less brittle web. It is "antisocial" by default to ensure maximum stability and independence:

  • Offline-First & LAN-Ready: If the global internet or major CDNs (like Cloudflare) go down, a Rezilienz site remains fully functional on a local network. It is built to survive in "disconnected" or "Small Web" environments.
  • No Presumed Dependencies: The core software makes no external calls (no Google Fonts, no remote tracking, no CDNs). All necessary assets are bundled locally.
  • Freedom of Choice: This is a separation of concerns. While the base software is self-contained, users are free to add their own external dependencies (CDN fonts, Unsplash images, or analytics) in the frontend head. Rezilienz provides a clean, independent foundation, but it doesn't dictate your frontend choices.

8. Storage Agnosticism

Rezilienz does not care where your files live. Through config.ini, you can map the content and asset directories to any location:

  • Local Folders: Standard filesystem storage.
  • Network Mounts: Collaborative storage over a LAN or NAS.
  • Synced Folders: Use Dropbox or Syncthing to sync content across machines without a central server.
  • Total Flexibility: Because content is stored as flat files, you own the location. There is no database lock-in.
  • The Git Funnel: Automated commit & push for an unbreakable audit trail and easy version control.
  • The SFTP Funnel: Reaching "dumb" storage (NAS/Linux servers) over SSH without needing a remote Rezilienz instance.

9. Future Storage Roadmaps: The "Write Funnels"

Rezilienz is designed to be storage-agnostic via a future "Funnels" abstraction layer. This will allow the CMS to further bridge the gap between local and distributed storage:

  • The Proxy Funnel: A simple, signed API bridge for secure in-house or corporate environments.
  • The IPFS Funnel: True decentralization via content-addressing and pinning.
  • The PHP Bridge: Reaching ubiquitous PHP environments (shared hosts/legacy servers).
  • The P2P Engine: Serverless peer-to-peer synchronization.

Note: All remote funnels can be hardened using Transport Tunnels (Tailscale, Tor, Wireguard) for maximum resilience.

TL;DR: Rezilienz provides the management power of a traditional CMS with the flexibility, portability, and future-proofing of a headless, API-driven, flat-file architecture—while remaining fiercely independent, resilient, and static-capable.