Blog / Framer & site building /

A content QA process for Framer CMS entries

The editor says the CMS entry is complete. Title, image, body, all there. Then you open the Framer page: the image crops out the one detail that mattered, and the main button opens the wrong resource.

Content QA has to follow an entry from its fields to the page people actually see. Filling the required fields is a start. It doesn’t prove the content is accurate, clear or pointing at the right place.

I build the review around what the collection is for: a short checklist for normal entries, and extra attention for the odd ones. Editors get a repeatable method without turning every publish into a ceremony.

Define what a complete entry means

List the information the collection needs to do its job. An article, a resource listing and a service entry need different fields and checks. Don’t borrow a generic checklist without adapting it to the model.

Separate required information from optional presentation. A missing download link should block publishing; a missing decorative image may not. Editors need to know which gaps hurt usefulness and which only affect looks.

Keep the rule with the collection instructions. Explain what each field controls, where its source comes from and who can confirm a factual question. Field names alone rarely communicate all of that context.

Review accuracy before polishing

Check important claims, dates, names, conditions and references against approved sources. If the entry describes a product or service, verify its scope with the responsible owner. A well-written sentence can still be wrong for the particular item.

Use a clear unresolved state when information is missing. Assign the question and hold the claim instead of filling it with plausible text. An empty field is easier to spot than a confident invention.

Keep source references in the working record where the team can maintain them. The published page may not need to expose every internal document, but the next editor should be able to understand how the information was verified.

Check the relationships between fields

Read the title, summary, body, image and action together. They should describe the same thing and make compatible promises. A summary copied from an older version can contradict the revised body.

Inspect related-content fields and manually entered URLs. Confirm the destination is current, relevant and intended to be public. A technically valid address can still lead to the wrong resource or an access-restricted document.

I pay attention to optional fields that change the template. Remove a caption or secondary action and you may get odd spacing or an empty element. Check what the project actually renders instead of assuming blank fields vanish neatly.

Preview realistic content extremes

Try long titles, long summaries, missing optional images and entries with several references. A template can look great with its sample content and struggle with what editors really type.

Use mobile and desktop views and check increased text size where appropriate. Look for clipped labels, awkward wrapping and images whose focal point disappears. These are content-model and presentation questions as much as writing questions.

Confirm the heading sequence and link labels remain meaningful. A repeated “read more” card may need enough surrounding context to make its destination understandable. Avoid using appearance as the only guide to the page’s structure.

Follow the entry’s main task

If the page offers a download, open it and confirm the file and version. If it sends an enquiry, follow the form route using approved test details. If it points to related content, inspect whether the suggested entry actually continues the topic.

Check the published page or approved preview, not just the CMS editor. Shared templates, navigation and component settings can change behaviour outside the entry’s fields. Review what the visitor receives. I’ve learned to trust the rendered page over the editor view.

Record failures in a reproducible way. Identify the entry, affected field or control, expected result and observed behaviour. A precise note helps the editor or designer correct the source instead of patching one visible symptom.

Separate approval from publication

Define who confirms content and who publishes it. These may be the same person, but the responsibility should be clear. A factual approval does not necessarily mean a shared template is ready for release.

Confirm the reviewed version has not changed in a way that requires another check. If a late edit alters a claim or destination, return that part to the relevant reviewer. Do not let approval become a blanket permission for subsequent changes.

After publication, open the public page and complete the important checks again. Confirm the route, visible content and primary action. Keep outstanding issues with owners rather than assuming publication closes them.

Use recurring defects to improve the model or instructions. If editors repeatedly enter the wrong kind of URL, the field explanation may be unclear. Fixing that source can make the next entry easier to publish correctly.

Let the checklist follow the collection’s real defects. If reviewers keep finding the same image problem, fix the image guidance or the template instead of adding a warning everyone ignores. If sources keep going missing, make the source request part of drafting. QA should cut preventable errors upstream, not just find them at the deadline.

Pick one CMS entry and follow its main action from the rendered page. What would a field-completion checklist alone have missed?