OYNKcms
OYNKcms is the content management system we built and run. This site is published from it, and it is what we build client websites on. It exists because the usual answer, WordPress, puts the editor, the plugins and the public website in the same place — and a lot of what we get asked to fix starts there. Your team can edit it from a browser, or from their own Claude or ChatGPT, and nothing goes live until a person publishes it.
The site owns the design. The CMS owns the words.
Every section of a site we build declares what can be edited about it: a heading, a paragraph, an image, a button. Nothing else. There is no page builder and no layout panel, so there is no field that can move a column, swap a font or push a page out of shape. Your team changes what the site says. The design stays the one that was built and tested.
That sounds like a restriction until you inherit a site three different people have each ‘tweaked’ through a page builder. The restriction is the point. It is what stops the fiftieth edit quietly undoing the work that went into the first.
Useful, and kept on a lead.
Anyone with a login can connect Claude, ChatGPT or another assistant that supports MCP to OYNKcms. It asks which websites and which permissions the assistant may have, and an assistant can never do more than the person who connected it.
Given write access but not publishing, an assistant proposes its changes into a change set, and a person reads the difference and decides whether it goes live. Disconnecting one happens in settings and takes effect immediately.
Four differences that matter once a site is live.
01
A WordPress site carries its own admin: a login page, a database and PHP running on the same server that answers your visitors. The way we build with OYNKcms, the public website is plain files with no database behind them. The editor lives on a separate server, so there is no login on your domain for anyone to try.
02
WordPress gets most of its features from plugins: third-party code installed into the site, running with access to it, each on its own update schedule. Here the features are part of the site we build, and the CMS is one system with one owner. There is no plugin to fall out of date and take something with it.
03
The editor never ships to your visitors. What reaches a browser is the page we built, with nothing added by the system that manages it. This site, measured on 10 September 2026, loads with zero bytes of unused JavaScript and zero bytes of unused CSS.
04
Everything published can be exported as plain JSON, and the website itself is ordinary files on ordinary hosting that you own on handover. If you ever move on, you take both.
What your team actually uses.
01
Changes save as a draft while you work. Save a version when you want a point to come back to. Preview shows the draft inside the real site, in the real design, before anyone else sees it.
02
Someone can write and edit all day without being able to put anything live. A change set sends several pages live together, or none of them.
03
A search panel scores each page for SEO and for how well AI search tools can read it, as it is being written rather than in an audit six months later.
04
Navigation and redirects are managed alongside the pages, so an old address never has to wait for a developer, and an activity log records what happened.
This site, running on OYNKcms.
From our own P.E.E.R. audit of 90 URLs on 10 September 2026. The CMS does not make a site fast — the build does. What OYNKcms does is stay out of the page, so there is nothing of its own for a visitor to download.
Performance score, out of 100
CO₂e per page view, on verified green hosting
Unused JavaScript and unused CSS
Not just ours.
Two client websites moved onto OYNKcms in September 2026. Same rule as this one: the site owns the design, the CMS owns the words.
01
Moved off Wix and rebuilt by hand. Its 19 pages and four case studies live in OYNKcms, and the case studies are a collection, so a new one gets its own page when it is published.
02
A B Corp and ESG consultancy. Its 14 pages sit in OYNKcms alongside two case studies and five client testimonials, each kept as a collection, so adding another does not mean editing a page.
We still build on it when it is the right tool.
This is not a crusade. The Beanz Barn booking system is a WordPress plugin we wrote, integrated with WooCommerce, and we still maintain it. If your team already lives in WordPress and it is doing its job, we will tell you so rather than sell you a migration.
Where it stops being the right tool is usually the same place: a brochure site carrying a page builder, a dozen plugins and a maintenance bill, doing a job plain files would do faster and for less. If that sounds familiar, what a website really costs is worth reading first.
OYNKcms, specifically.
Yes, that is what it is for. Your team signs in, changes the words, images and pages the site was built to let them change, previews the result in the real design and publishes. We set up the logins and permissions with you at handover.
Nothing your visitors would notice. The public site is built as plain files and served on its own, so it keeps working. Editing and publishing wait until the CMS is back.
No. Everything published can be exported as plain JSON, and the website is ordinary files you own on handover. Moving to something else is work, as any move is, but nothing is held back.
When there is a reason to, usually because a team already knows it and edits content every day. The Beanz Barn booking system is a WordPress plugin we wrote and still maintain. For most brochure and service sites, OYNKcms with a hand-built front end is faster to load and cheaper to keep.
Yes, over MCP, which Claude and ChatGPT both support. You choose which websites and permissions each assistant gets, it can never exceed your own access, and you can disconnect it whenever you like.
Get started
Tell us what the site has to do and who needs to change it. We will tell you whether OYNKcms is the right fit, or whether what you already have is.
Or email hello@oynk.co.uk