CMS development
Your CMS shouldwork the wayyour team does.
Updating a page should not mean finding a developer, guessing which field to change or waiting for three people to forward the same file. We design content management around the people who use it — from straightforward website editing to custom admin tools with real business logic.
02The real problem
When the next update turns into a small project.
Content lives in spreadsheets, approvals happen in chats, the same information is copied to several places, and someone is afraid to touch the admin because the layout might break. A better system starts by understanding those friction points.
Sometimes the answer is a cleaner content model in your current platform. Sometimes it is a new CMS. We help define the difference before development begins.
Less chasing. Fewer duplicates. Clearer ownership.
03People first
One system. Different jobs.
A writer needs clear fields. A reviewer needs to see what changed. A manager needs to know what is live. A developer needs structure that stays predictable as the site grows. We map those real tasks before drawing the dashboard.
Roles and approval functions are scoped to the selected CMS, not assumed by default.
04Choosing the route
Not every project needs the same kind of CMS.
Your main task is editing pages, articles, images and reusable site sections.
Content-first website
We can build an organized website with a visual content workflow and a lightweight publishing setup.
Your team manages structured records, business rules, approvals, data connections or internal operations.
Custom workflow
Here the admin interface and backend are designed around the actual process, rather than treated as an add-on to a website.
We choose an architecture after looking at the content, users and integrations. A visual website editor is not a substitute for a full custom operations system.
05Content model
Content needs structure, not just empty text boxes.
A project is not just a paragraph. It may have a client, industry, services, results and related materials. Once those pieces are defined clearly, your team can find, update and reuse them without rebuilding every page by hand. We shape fields, categories and relationships around what your business actually publishes.
- ArticleAuthorTopic
- ProjectServiceIndustry
- AssetPage
Example: update a project summary once; its connected pages can use that same approved information where the architecture supports it.
Clear fields · Useful relationships · Less repeated work.
06Editor experience
Make an update. See what changes.
People should know which field controls which part of the page. We design editing screens around clear labels, useful content groups and a reliable preview wherever the chosen system supports it. The goal is simple: your team spends time improving content, not decoding the admin panel.
Typical everyday tasks
07Reusable sections
Flexible pages. A consistent website.
Your team should be able to assemble useful pages without recreating the design system every time. We define the sections and content fields you really need, then make them reusable in the selected CMS. Editors gain practical freedom; the site keeps its typography, spacing and responsive behavior.
Example modules
The available editing controls depend on the implementation and are specified before build.
08Publishing
Give every change a clear path.
Some teams publish immediately. Others need a draft, a reviewer and approval before an update goes live. We map that path, define who should be able to change what and keep routine work understandable. If your project requires version history, notifications or audit records, those become explicit requirements rather than vague promises attached to the word “CMS”.
- ReviewOptionalChecks the draft in context
- LiveThe update is published
Appropriate access. Clear decisions. Fewer surprises.
09Integrations
Content rarely lives on its own.
A request from the website may need to reach your CRM. A document may need to appear in several sections. An update may have to trigger another team’s workflow. We identify those dependencies and design the right integrations where they bring real value.
- WebsitePages and articles publish from one source.
- Lead form & emailA request from the site reaches the right inbox.
- CRMNew leads arrive in your CRM through its API.
- Document libraryOne document appears in several sections.
- AnalyticsMeaningful actions are measured.
Every connection is scoped, tested and documented; we do not assume every project needs them all.
10Migration
Changing the system should not mean starting from zero.
If you already have pages, articles, images and search visibility, migration starts with an inventory, not the Export button. We map content types and URLs, identify what needs cleaning, plan redirects where addresses change and test the new publishing flow on real materials. We also review metadata, internal links and relevant structured data before launch.
- /news/2021/new-office.html301Article/articles/new-office/
- /about-us.php301Page/about/
- /team/anna-lee/Same URLPerson/team/anna-lee/
- /uploads/brochure_v3.pdf301Document/library/brochure/
- /services?id=7301Service/services/audit/
- InventoryPages, articles, files and their URLs
- MappingContent types, fields and new addresses
- Test importReal materials in the new publishing flow
- 301 redirectsWhere addresses change
- VerificationMetadata, internal links, structured data
Know what moves. Know what changes. Check what goes live.
Migration impact is assessed and monitored; rankings and traffic cannot be guaranteed.
11Architecture
A simple editing experience takes thoughtful engineering.
For suitable content-led sites, our Nuxt-based approach gives your team organized content editing while serving visitors fast, pre-built pages and optimized images. Nuxt Content and Nuxt Studio can support this editorial route; Nuxt/Vue builds the visible interface, and Cloudflare delivers the generated site.
When the job includes complex permissions, workflows, private data or operational records, we scope a separate CMS/backend architecture.
- Editor & content sourceOrganized content and an agreed editing workflowNuxt Content · Nuxt Studio
- Website frontendThe visible interface, built from reusable componentsNuxt · Vue
- DeliveryPre-built pages and optimized images served to visitorsCloudflare
- Complex permissions
- Workflows
- Private data
- Operational records
We do not call a visual page editor a full business platform.
- Nuxt 4
- Vue 3
- Nuxt Content
- Nuxt Studio
- Nuxt Image
- Cloudflare Pages
12Handoff
We hand over more than a login.
A CMS project is complete when the people who use it understand what they can change and how to keep it running. The final scope is defined around the selected solution, but the practical handoff can cover:
Content model
An agreed content model and editing scenarios.
Editor screen
A usable editor interface and reusable components where relevant.
Tested sample page
Built and tested site/backend functions and agreed integrations.
Transfer checklist
Migration and launch checks when replacing an existing system.
Concise guide
A walkthrough, concise guidance and the boundaries of ongoing support.
We test the workflow with real content before calling it finished.
13Start
What is your team trying to make easier?
Tell us what you manage today, who needs to update it and what keeps getting in the way. We will help define whether you need a better content structure, a new editorial setup or a custom management system.