Write and publish articles

Articles are the pages of your portal's docs. Anyone on your team can write, publish and change them in Docs.

Write an article

1. Open Docs in the sidebar.

2. Select Add content → New article. To start it in a collection, select the + beside that collection (or tab) in the tree on the left, then New article.

3. Give it a title of 3 to 120 characters, such as "Invite your team".

4. Write the text under it. Type / on an empty line for headings, lists, tables, steps, code and more: see Format an article.

5. To put it in a collection or hide its updated date, select Settings in the top bar. Its other settings, such as who can read it, appear there once it's saved: see Article settings.

6. Select Save draft.

A draft is only seen by your team. Its address comes from its title and follows it while it's a draft.

Publish it

Select Publish in the top bar, then Publish again in the dialog. The article goes into your portal's docs, for the readers its Who can read setting allows, and search engines can find it unless you block them in its settings.

On the Free plan, a project can have up to 50 published articles. Past that, publishing is refused with "Your plan publishes up to 50 articles. Unpublish some, or upgrade to Pro." Saving drafts always works. Pro and Business have no limit: see Plans.

Change a published article

Edit the title or text and select Save. Your changes don't go live straight away. An Unpublished changes card appears above the article: readers see the published version until you publish them.

• Review changes compares them with the published version. Paragraphs taken out are struck through and new ones are highlighted. You can publish from there too.

• Publish changes makes them live.

• Discard changes takes the article back to the published version. What you discarded stays in its history, so you can restore it.

A change of collection in Settings waits for Publish changes in the same way. The article's other settings apply as soon as you save them.

Once changes go live, readers see "Updated" and the date under the title. You can turn this off for one article in its settings, or for every article in Content actions.

If a teammate saves the article while you're editing it, the editor says so and keeps your text. Save, and your changes are combined with theirs. If you both changed the same part, the newest version shows beside your text so you can copy what you need, then save again.

Autopilot's suggested edits also wait in Unpublished changes. See Review Autopilot's updates.

Unpublish an article

Select Unpublish in the top bar. The article leaves your portal at once and becomes a draft again. If it had unpublished changes, they become the draft's text.

Go back to an earlier version

Open More actions (⋯) in the top bar and choose History.

History lists every save that changed the article, newest first, with who saved it. Pick one to see what changed since then, and select Restore this version to bring it back. On a published article, the restored text arrives as unpublished changes for you to publish. The version you replaced stays in the history.

How many versions you can see depends on your plan:

When a plan keeps fewer, the older versions are hidden, not deleted. They show again, and can be restored, once your plan keeps them.

Delete an article

Open More actions (⋯) and choose Delete, then confirm. A published article leaves your docs and links to it stop working.

Deleted articles wait in Recently deleted, at the bottom of the Docs page (the tree links to it). Select Restore within 30 days to bring one back as a draft.

Check it against your code

If your project is connected to GitHub, More actions → Verify checks a published article against your code. See Check articles against your code.