Editing website content with a CMS lets your team update text, images and blog posts when the necessary fields are available and their accounts have the right permissions. A CMS is the administration area where content is entered through forms or a visual editor. Who can publish a change, and when visitors can see it, depends on the agreed workflow.
Before handover, test a complete task from editing a paragraph to seeing it on the public website. On the Cargo Shark blog, the client edits the content and our team reviews and publishes the changes. This example explains what independent editing involves when the agency handles the final publishing step.
What should your team be able to edit?
Start with the content that changes during the year. A firm that publishes completed work needs fields for project descriptions and photographs. A team writing a blog needs a title, introduction, article body and category. If you frequently update prices or opening hours, record where those details appear on the website.
For each type of content, decide who enters it and who confirms that it is accurate. You can then assess whether the proposed administration area supports the work. Having a CMS account does not by itself mean that every field you need has been provided.
Make this list when discussing website development. Ask the developer to demonstrate one of your regular updates using the amount of text and the type of images your team will actually work with.
How does editing work on the Cargo Shark blog?
For freight company Cargo Shark, we connected the blog to a CMS configured for its content and approved design. An editor can open an existing article or start a new one. They enter the title, category and short introduction, then work on the article in a visual editor.
The editor supports subheadings, links, images, lists and tables. Separate fields hold the SEO title and description. The visible article title and the introduction on its listing card remain separate, so the editor can identify which part of the presentation they are changing.
Saving a new article keeps it as a draft. Our team reviews the content and prepares it for publication within the existing template. Changes to an article that is already live also wait for the next website publication. The client can therefore prepare content without changing the page layout, fonts or colours.
Enter content
The editor writes the article and adds its materials.
Save
The change is stored in the CMS. The public website is unchanged.
Review
The agency checks the content and presentation before publication.
Publish
The agency publishes the checked website version.
Check live
The updated article is checked at its public address.
This workflow applies to the Cargo Shark blog. Newsletter content is managed separately. A website where staff need to publish changes immediately requires a different agreed workflow and suitable permissions.
How can you tell whether a change is published?
After saving, look at the entry status and check what it means in your system. If publication is a separate step, agree who carries it out and how the editor receives confirmation. A button label alone does not tell you whether visitors can already see the change.
Content saved in the Cargo Shark CMS waits for agency publication. On other websites, an authorised editor may be able to publish directly. For example, the WordPress documentation on user roles distinguishes between preparing content and having permission to publish it. Check the settings on the account your employee will use.
After publication, open the public URL in a browser window where you are not signed into the administration area. Check the exact sentence you changed, the image and the link destination. If the update is missing, tell the person responsible for publication which entry you saved and what you expected to change.
What should you prepare alongside the text?
Supply the original image file with a short description of what it shows. Choose a crop that remains understandable when the image is smaller on a phone. Agree who prepares an appropriately sized file and who checks the alt text on the published page. The description should match the image and its purpose in the article.
Link from words that describe the destination, then open the link to check it. Involve the website maintainer before changing an address that is already public. On the Cargo Shark blog, published URLs are protected against accidental changes; an intentional change requires an agreed new address and redirect.
If the administration area has separate SEO title and description fields, write them to describe the article accurately. Check the introduction shown on the blog listing too. These fields can serve different purposes, so they do not necessarily need identical wording.
Which tasks belong to the editor and which to the agency?
The division depends on the project. In the Cargo Shark example, the client has access to blog content and images, while our team handles publication and website design. Use the following table to agree responsibilities for your own website; it is a suggested arrangement, not a standard service package.
Scroll the table sideways to see all columns.
| Task | Responsible person | How to check it |
|---|---|---|
| Accuracy of copy and business details | Someone in the business who knows the offer. | They confirm names, terms and contact details before publication. |
| Article entry | An editor with suitable access. | They reopen the saved entry and check its title, text and category. |
| Image and description | The editor supplies the material; an agreed person prepares the file. | The image is clear on a phone and its alt description matches the content. |
| Links and SEO fields | The editor, with a check by the person responsible for publication. | Links reach the intended pages; titles and descriptions represent the article. |
| Publication | A person with publishing permission or the agency. | The agreed change is visible at the public URL. |
| A new layout or feature | The team maintaining design and development. | The scope and presentation receive a separate review before publication. |
Updating an existing service description and adding a new search function are different requests. Search requires decisions about the data and development of the feature. If the administration area needs to support a particular business process, work through it as part of web application development.
What should staff try during CMS handover?
Ask the person who will maintain the content to complete an update themselves, using the prepared instructions. Use an agreed draft or test environment for the exercise, so it does not accidentally change your public offer.
- Sign in with their own account and find the content they need to edit.
- Change the text, add an image and insert a link.
- Save the entry, reopen it and check what was saved.
- Follow the agreed review and publication process, then open the public page on a computer and phone.
- Find out whom to contact after a mistake and how to request a correction or restoration of earlier content.
The instructions should also cover changes to content that is already published. Check revision recovery, approval and scheduling explicitly, because their scope differs between systems. Record who maintains the administration area and who handles access problems.
How do you define the CMS scope for your website?
If you are still choosing a platform, our guide to WordPress or a custom website covers that decision. To specify the administration area itself, describe the actual work: what changes, how often, and who approves the content.
Send us that list for an estimate, together with an example page or article you want to edit yourself. We can then propose the required fields and publishing process before development starts.