Updates wait for a developer
Routine text, image or article changes become tickets, emails or code edits.
Payload
CMS.
A useful website your team can keep useful.
Publish articles, update pages, manage projects and organise media without asking a developer for every content change.
See what a CMS changes ↓01 / Plain-language definition
What is a CMS?
A Content Management System is the private editing area behind a website.
Your team signs in to create or update agreed types of content. The CMS stores that information in a consistent structure; the public website presents it through the designed interface.
You control the content. The layout, responsive behaviour and technical system remain protected from accidental edits.
02 / Recognise the need
When does a CMS
become useful?
A CMS is valuable when publishing is recurring work. A small website that changes once a year may not need one.
Publishing is inconsistent
Pages are assembled differently because there is no shared content structure.
Several people edit content
The team needs clear responsibilities for drafting, reviewing and publishing.
Content is growing
Articles, projects, people, locations or resources are becoming difficult to organise.
The same information appears twice
A change has to be copied across several pages, increasing the chance of stale content.
The current CMS gets in the way
Editors avoid updates because the interface is confusing or too much can break.
03 / Your content workspace
Manage what changes.
Explore a representative CMS dashboard. Content types are shaped around the organisation rather than hidden inside one generic page editor.
Example Payload CMS configuration by AMUI
Content overview
The content that powers your website.
Pages14
Articles27
Case studies8
People12
Content
Type
Status
Updated
Rebrand launch
Article
Published
Today
Greenhouse project
Case study
Draft
2h ago
About our studio
Page
Published
Yesterday
Anna Nováková
People
Published
3 days
Try the navigation abovePages, articles, case studies, people, media and users can each have different fields, permissions and workflows. What appears in the CMS depends on what your project actually needs.
04 / A routine task
Edit. Preview.
Publish.
Try the example. Change the content and publish it to the preview without editing code.
Article / Editing draftcontent / articles / edit
Website preview/news/a-new-chapter-for-our-studio
CLIENT / JOURNAL
A new chapter for our studio
We have updated our studio to give our team more space to collaborate, meet clients and build the next generation of projects.
Access without unnecessary risk
The right control
for each role.
Editors can manage routine content without receiving access to users, configuration or technical controls they do not need.
Choose a role
Administrator
Full control over content, users and website configuration.
Permissions
Administrator accessWhat remains yours
Independent publishing.
A maintained system.
A CMS removes dependency for routine content—not every technical responsibility. Hosting, backups, updates and larger design changes still need clear ownership.
- Update agreed page content
- Create articles, projects or profiles
- Upload and select media
- Preview and publish
- Manage content in multiple languages where included
- Content structure and editorial UX
- Website design and development
- Migration and redirects
- Permissions and integrations
- Hosting setup, maintenance and future changes
05 / AMUI work in practice
Naše Horoměřice.
Client-controlled publishing connected to a custom website.
AMUI built the website with Payload CMS so the team can publish and maintain structured content without code changes for every article or update.
Read the case study ↗Publishing workflow
- 01Sign in
- 02Create or update content
- 03Review and publish
- 04Website updates
06 / How we build it
Website and CMS.
Designed together.
The goal is not to install software. It is to give visitors a useful website and your team a manageable publishing process.
Understand what changes
We review the content your team publishes, who owns it, how often it changes and where the current process causes friction.
Design the content structure
We define useful content types and fields—for example articles, people, projects or locations—rather than giving editors one unstructured page builder.
Build the website and CMS together
The public website and editing experience are connected. Preview, permissions, media and publishing workflows are included where the project needs them.
Plan migration and launch
If content already exists, we review exports, URLs, images and field mapping. Migration and redirects are agreed before launch.
Train and hand over
We test the important editing tasks with your team and provide guidance for routine publishing, responsibilities and support.
A practical first conversation
Make publishing
part of the work.
Show us what your team publishes today and where the process slows down. We can help determine whether a CMS is useful and what it should manage.
Book a free 15-min call