Content QA

Content QA that knows your guidelines.

Spellcheck catches typos. Donobu catches what breaks your guidelines: a tone that slips off-brand, a fact that is wrong, a price or version that went stale. Our engineers turn your rules into checks, AI agents run them on every page and document before it goes live, and test engineers review every finding before you see it.

Content under test
learn.brightpath.io/it-basics/lesson-3
brightpath/ IT Support BasicsLesson 3 of 5

Set up a workstation

Daniel Reyes · 6 min read

In this lesson, you set up a new workstation from scratch.

Start by installing Windows 95 from the setup disks.

It's so easy that honestly any idiot can do it.

Connect to Wi-Fi 6, which tops out at 54 Mbps.

Students should save their work every hour.

Your guidelines
FreshnessNo retired tools, versions, or prices
ToneEncouraging, never condescending
AccuracyFacts match the course sources
TerminologySay "learners", not "students"
The problem

The errors that hurt you are not typos.

A help article quotes a price you changed last year. A product page reads like it was written for a different brand. A setup guide still recommends Windows 95. None of these trip a spellchecker or a broken-link scan. A human reviewer catches them only with time to read every word against the style guide, so review becomes the launch gate, and it gets slower exactly when your publishing calendar gets busier.

What it flags

What Donobu flags, with your rules as the yardstick.

  • Freshness: a guide that still recommends Windows 95, or a price, date, version, or policy that is out of date
  • Accuracy: claims that contradict your sources, like a spec that says Wi-Fi 6 tops out at 54 Mbps
  • Tone: copy that drifts from your voice, like "any idiot can do it" on a page meant to encourage
  • Terminology: "customers" where your guide says "members", or a competitor's product name where yours belongs
  • Spelling, grammar, and brand-name errors in page text and PDFs, including scanned ones
  • Broken images, videos, and links on the page a visitor actually sees
How it works

Your guidelines, applied to every item, every time.

01

We turn your guidelines into checks.

Forward-deployed engineers in test (FDETs) read your style guide, tone and voice rules, terminology list, and source-of-truth references, and encode them as checks Donobu applies to every item.

02

Agents read the real rendered content.

Not a CMS field: the page or document your audience actually sees, including PDFs and downloads.

03

Every item gets checked against the same rules.

Tone that drifts off-brand, claims that contradict your sources, outdated tools, versions, prices, and dates, and wrong terminology. Spelling, grammar, broken media and links, and locale variants get checked too.

04

Our engineers review before you do, and you pay per item.

AI agents do the reading and the first pass. SDETs review every finding before delivery, so you get a short list of real problems, not a wall of AI opinions. Pricing is usage-based: per item checked, not a flat contract sized for your busiest month.

Proof

Proof

Coursera uses Donobu to QA content before launch, paying for outcomes rather than tester-hours.

Ownership

Findings you keep, not a report you file away.

Every content check runs the same way every other Donobu test does: local-first, on your machine or in your VPC. A rendering issue on your most-visited page can become a real Playwright test in your own repo, one you can re-run on the next launch instead of re-checking by hand. See the full case for owning your tests.

More ways teams use Donobu

Functional testing

Turn critical user journeys into a regression suite that never goes stale.

See functional testing

API testing

Test your HTTP APIs on Playwright, with every request and response in the report.

See API testing

Exploratory testing

Point an agent at your app and see what's actually broken, no script required.

See exploratory testing

Mobile app testing

Test native Android and iOS builds the same way you test the web.

See mobile app testing

Localization QA

Continuous QA across every market and locale you ship.

See localization QA
FAQ

Frequently Asked Questions

What guidelines can Donobu check against?

Whatever your editors already use: a style guide, tone and voice rules, a terminology list, banned phrases, and source-of-truth documents for facts like prices, versions, and policies. Our engineers encode them as checks, and you review the first findings with us before the checks run at scale.

How do you keep tone and accuracy checks from being noisy?

The checks measure each item against your written rules and sources, not a generic opinion of good writing. Test engineers review every finding before it reaches you and drop the ones that do not hold up.

What content can Donobu check?

Any page or document you publish: product and pricing pages, help center and docs articles, marketplace listings, course lessons, marketing pages, and PDFs. Each item is checked as the rendered page your audience sees, not as fields in a CMS.

Can Donobu check PDFs and downloadable material?

Yes. Donobu reads PDFs, including scanned ones, with OCR, and proofreads page text or PDF text for spelling, grammar, and brand-name errors.

How is content QA different from localization QA?

Localization QA checks whether your product works correctly in each locale: layout, translated strings, locale-specific logic. Content QA checks whether a content item is ready to publish against your own guidelines: tone, accuracy, freshness, terminology, and rendering. The two overlap where an item ships in more than one language.

Is this fully automated?

No. AI agents do the reading and the first pass. Our engineers encode what "ready to publish" means for your content and review every finding before it reaches you: the same FDET-authors, SDET-reviews model Donobu uses across every managed offering.

What does it cost?

Usage-based, per item checked. Cost scales with what you publish instead of a flat contract sized for your busiest launch month.
Get started

Ready to see what Donobu finds in your content before launch?

Book a demo