Daily article operations guide
Read the live page after a VA article deployment
Catch layout and meaning problems that source-code checks cannot reveal on their own.
Where the work breaks
Automated checks may confirm a 200 response and correct metadata while a page still has clipped text, broken tables, or awkward headings.
A routine the team can repeat
Open the direct production URL on desktop and a narrow viewport. Read the title, date, opening, headings, links, tables, and close in order.
What to keep in the record
Capture the route, deployed commit, viewport, check time, and a screenshot when it helps explain a defect.
Who decides
The checker reports visible facts. The editor decides copy changes and the developer fixes rendering; neither silently waives the other’s gate.
Use this in the daily queue
Apply the check to one named article and keep the result with that article’s release record. A short, specific entry is more useful than a generic "done" status.
See the research library or plan a research support workflow.