⚡ Zero-Bundle HTMX Server-Side Renderingrullst-core

Ultra-fast declarative UI generated with zero client-side bundle overhead. Powered by Rullst's compile-time `html!` macro and Axum static dispatch.

Here is an in-depth breakdown of how Rullst unifies all 5 web paradigms natively, eliminating framework lock-in: 1. ⚡ Zero-Bundle HTMX SSR (Rullst Native Standard): - Paradigm: Declarative HTML5 attributes with compile-time `html!` macro. - Footprint: 0 KB JavaScript bundle. Sub-millisecond TTFB. - Ideal For: SEO landing pages, SaaS dashboards, and CRUD apps. 2. 🔴 LiveView Server-Driven UI (`rullst::live` — Phoenix & Dioxus pattern): - Paradigm: Bidirectional WebSocket state synchronization over Tokio. - Footprint: Zero client-side logic. State lives in server RAM; DOM diffs are pushed to the browser in real-time. - Ideal For: Live feeds, chats, reactive counters, and notifications. 3. 🏝️ Reactive Wasm Islands (`rullst::island` — Leptos & Yew WASM/Signals pattern): - Paradigm: Client-side WebAssembly micro-frontends mounted pontually. - Footprint: Isolated WASM bytecode running in the browser VM. - Ideal For: Rich Markdown editors, canvas games, offline calculations, and charting. 4. 🎨 Zero-Build Semantic CSS (Pico.css v2 Engine — `/pico-demo`): - Paradigm: Classless semantic HTML5 styling with automatic OS Dark/Light theme detection. - Footprint: 0 KB JS, 0 Node.js / NPM build step, instant styling for pure HTML tags. - Ideal For: Backend developers wanting clean, accessible UIs with zero JS toolchains. 5. 📄 File-Based Classic Templates (Jinja2 / Tera Engine — Loco & Rails pattern — `/templates-demo`): - Paradigm: External HTML files located in `templates/*.html` with layout inheritance. - Footprint: Decoupled presentation layer for frontend designers. - Ideal For: Teams migrating from Django, Laravel, Rails, or Loco.rs.

Welcome to The Sovereign SaaS Blog & Publisher. Explore the top navigation bar to test the available front-end foundations, the Hybrid ORM, local Rullst Studio (http://127.0.0.1:5555), Nexus CMS (/nexus), Capital Billing, and Security RASP demonstrations. The example uses task-local tenant scoping as a development fixture. Production applications must derive membership from authenticated identity and keep cross-tenant negative tests in their own authorization model.