Quick product and launch note after checking the repo, the HN framing, and the live site behavior:
I think the product is clearer in the README than it is in the actual first-touch journey.
The broad claim, “spiritual successor to WordPress,” gets attention, but the sharper truth in the README is stronger: TypeScript CMS on Astro/Cloudflare that keeps the extensibility and admin upside while fixing the plugin security model with sandboxed workers.
That is the part that feels category-changing.
Then on the live site, I got dropped into admin/playground flow pretty quickly, which makes cold understanding harder than it should be.
If I were changing 2 things first:
- tighten the top line around the plugin-security/extensibility wedge
- make the root experience explain the product before sending people into the app surface
Broader GTM thought: the repo has enough traction already that this is less a “get attention” problem and more a “convert curiosity into immediate understanding” problem.
If that direction resonates, this also feels narrow enough that a tiny README/homepage copy PR could be useful.
Quick product and launch note after checking the repo, the HN framing, and the live site behavior:
I think the product is clearer in the README than it is in the actual first-touch journey.
The broad claim, “spiritual successor to WordPress,” gets attention, but the sharper truth in the README is stronger: TypeScript CMS on Astro/Cloudflare that keeps the extensibility and admin upside while fixing the plugin security model with sandboxed workers.
That is the part that feels category-changing.
Then on the live site, I got dropped into admin/playground flow pretty quickly, which makes cold understanding harder than it should be.
If I were changing 2 things first:
Broader GTM thought: the repo has enough traction already that this is less a “get attention” problem and more a “convert curiosity into immediate understanding” problem.
If that direction resonates, this also feels narrow enough that a tiny README/homepage copy PR could be useful.