i.visual editing
Drag, drop, ship. No 'approximations'.
Bliss uses a real-time preview that matches the published output exactly: same HTML, same CSS, same fonts. What you arrange is what gets shipped.
Make a website without losing a weekend.
A CMS for the open web, made for people who care where their content lives. Your pages stay portable, with optional HTML backups committed to a GitHub repo you own.
early access · we're letting folks in slowly
The Product · In Three Parts
Three things,
done well.
A field guide to what makes Bliss different from the rest.
An essay · 20 July 2026
ii.backed up to GitHub
A copy you keep, always.
Connect a GitHub repo and Bliss commits an HTML backup of every page you publish. A plain, portable copy you own, in a format that outlives any platform. No 'export' button you'll fight with three years from now.
iii.plain HTTP, plain content
Use it from anywhere. No SDK required.
Building a mobile app, a Discord bot, or an analytics pipeline? Same content, plain JSON over HTTPS. Cache it, query it, and archive it like you would any other resource on the open web.
From the Team
Bliss Studio.
Published by Strands Services Limited
United Kingdom
20 July 2026
Re: On vendor lock-in, keeping a copy, and why we're building yet another CMS.
Dear reader,
We built Bliss because we got tired of CMSes that treat your content like a hostage: locked behind vendor APIs, stuck inside proprietary dashboards, and shipped with 'export' buttons that lose half the formatting on the way out.
Bliss keeps your content as structured data, and if you connect a repo it commits an HTML backup of every published page to GitHub you own. The visual editor is a friendly layer on top, but what you ship is always yours to keep.
If you're a developer who likes nice tools, or a designer who doesn't mind a peek at the code, this is built for you.
Yours sincerely,
The Bliss Studio team
on behalf of the makers
✻ ✻ ✻