Designing in the Open: The Broadsheet Aesthetic and Our Honest v0.1 Ledger
Print heritage meets systems engineering
The word press is right there in our name. Before the web was a tangle of JavaScript bundles and cloud billing dashboards, publishing was ink on warm newsprint, set in optical-size serif faces and structured by crisp hairlines and double rules.
Our design system pairs Newsreader (an optical-size editorial serif), Schibsted Grotesk (for dense admin UI and body copy), and IBM Plex Mono (for commands, crates, and colophons) on a warm newsprint palette (#f3eee4 in Daylight, #111214 in Night Edition) accented with Oxide Rust (#a8401b) and Press Blue (#2a3bd0).
Software websites shouldn't read like pitch decks. They should read like field manuals written by the engineers building the tool.
Why we publish a 'Doesn't work yet' column on our homepage
Open-source infrastructure earns trust by being specific about its boundaries. On our homepage and in our README.md, right next to the list of what ships in v0.1 today, we maintain an explicit list of what does not work yet: third-party PHP plugins cannot run in a Rust binary, there is no WooCommerce replacement yet, and the Wasm plugin sandbox is still on the roadmap.
If you try migrating a WordPress site to Daypress v0.1 and hit a broken shortcode or missing meta field, file a Migration Report on GitHub. Every real-world export makes the compiler smarter.
