Start with the changes you make often
A service business may update hours and descriptions. An architecture studio adds projects, details and galleries. A car rental company changes fleet and availability. Before choosing a CMS, list these tasks and who will perform them. The goal is independence for real updates, using fields and workflows that make sense to the team.
Separate content from page design
Editing a heading or replacing a cover does not have to change spacing, typography or grids. A custom theme can control presentation while the dashboard manages content. On the new Moreira Rangel website, the studio has fields for project copy, details, covers and images. Publishing new work does not require redesigning every page.
A gallery also tells a story
Image order can change how a project is understood. Check whether the editor supports ordering, replacing and identifying images, and whether the design supports the intended sequence. Photographs, drawings and 3D visuals should be described accurately. Before publishing, review the full page on a phone and computer, including captions and alternative text.
Decide who prepares and who publishes
Not everyone needs the same permissions. Ask how drafts, review and restoring an earlier version work. Check how access is created and recovered. Independence requires more than a login: it needs clear instructions and a way to correct mistakes without losing work.
Clarify maintenance before handover
Having a CMS does not mean every future change is included. Distinguish content editing, new functionality, design changes and technical updates. The proposal should explain responsibilities, costs and support. With NOVYST CMS, installation, theme and modules are defined for each project; it is not a free-form visual editor or a way to install WordPress themes.
Try a real task during review
Before approving the website, choose a task: publish a project, replace a photo or update contact details. Complete it in the review environment and check the result. This demonstrates the dashboard’s usefulness better than a long feature list. Include the fields, permissions and instructions your team actually needs in the proposal.