Publishing a generated article
The last step is the same as for anything you write by hand.
By HeyThula · Updated
Once a generated draft reads the way you want, publishing it is exactly like publishing any other article.
Choose a collection
A generated draft needs a home. Put it where a reader would look — a walkthrough of your signup belongs in Getting started, not in a collection of its own for generated content.
Once published, nothing distinguishes it from an article you typed. Readers shouldn't be able to tell, and there's no reason they should.
Preview first
Preview matters more here than usual, because generated guides carry several screenshots and this is where you see them at reading size — too small to make out, or too tall so the text disappears between them.
Set live
Publishing does three things at once:
Puts the article on your public help centre
Makes it searchable, there and in the widget
Gives it to the AI as something it can answer from
That third one is the reason this is worth doing. A recorded walkthrough becomes an answer the AI can give a customer at 2am, not just a page someone might find.
Its address is fixed now
The article gets a permanent address at first publish, based on its title. Renaming it later won't change that, so shared links keep working. See Drafts and publishing.
Keeping it current
Screenshots age. When the flow they show changes, re-record the guide rather than replacing images individually — a fresh recording takes minutes and keeps every picture consistent.
A stale screenshot costs more trust than a missing one, because a reader who follows a picture that no longer matches concludes the whole help centre is out of date.
Where it fits
Recorded guides are good at procedures — the click-by-click flows that are tedious to write and easy to get wrong from memory.
They're not a substitute for the articles that explain why, or the ones covering things with no interface to record. Use them for the how, and write the rest.