A small, secure CMS for businesses that need a website and a blog, not a plugin ecosystem.
Most sites don't need thousands of plugins. They need pages people can edit, a blog, good search rankings, and nothing that turns up in next week's security alert.
This CMS does a few things well instead. One installation serves many websites. Public pages are plain HTML, built on the server. Pages are made from sections of set types, so editing the words can't break the layout. And an AI agent can write content with the same permissions as the person it's working for. That's how much of this site was drafted, before I reviewed it and published it.
suiteresources.com and blog.suiteresources.com run on the same installation. Adding a site means adding a record, a domain and a certificate, not a new server. Each site has its own theme, navigation and content, and nothing is shared between them.
A page is a stack of sections, each of a set type: hero, text, image and text, feature grid, pricing, contact form, search, recent posts and more. Authors write the words, and the design stays consistent.
Posts with bylines, tags, monthly archives, on-site search, previous and next links, and page numbering that search engines actually index.
Every edit to a live page keeps the previous version, deletions can be undone, and a changed or retired web address redirects to the new one instead of showing an error.
Search-result descriptions, link previews and duplicate-page handling, plus Google Analytics, Google Ads conversion tracking and AdSense for each site. A consent banner sets Google's privacy defaults before any tracking code loads.
AI agents reach every feature through an MCP server and can do exactly what their person can do, and nothing more. Sharing a post to LinkedIn is its own action, never a side effect of publishing it.
The big platforms are popular, and their popularity is exactly what makes them targets. Their plugins add features nobody asked for and security holes everybody inherits. For a business that needs a website and a blog, that's the wrong trade.
So the aim here is simplicity. The public site is plain HTML built on the server, with no JavaScript build step. It loads quickly on a slow connection, search engines can read it, and it's small enough to understand. The editor is a separate application behind a single sign-on, where search engines never reach it. Content is written in Markdown, and any raw HTML pasted in is shown as text rather than run, so a copied snippet can't sneak in a script.
It's also an honest test of the platform it's built on. Sign-in, deployment, usage tracking and AI access come from AI Application Manager, so the CMS itself is mostly the content structure and the editor. If that approach works anywhere, it should work on the site that makes the case for it.
No comments on the site. Discussion happens on LinkedIn, on purpose. Posts can be shared there with commentary you write. Comments on the site may come later, moderated by a person.
No RSS feed or newsletter yet. Both are planned, and neither is built.
No plugin marketplace. New features arrive as new section types, built and tested before they reach a live site.
It isn't a drag-and-drop page builder. You arrange sections and write what goes in them. That limit is what keeps every page consistent.
From a draft page to a live one, and who is allowed to make that move.
How it works