Creating and Editing Documents

Creating and Editing Documents

Documents in AB Projects are Markdown pages with full version history. Creating and editing happens in a side panel with a live preview, and every change is recorded so the team always knows what changed and why.

Creating a page

• In the project's Documents area, start a new page. Give it a title, an optional parent path (defaults to / — set something like onboarding to nest it), and optional tags.
• Write the body in Markdown. The editor shows a live preview next to the source so you can see the rendered result as you type.
• Save to publish the page into the tree. It becomes version 1.

Editing a page

• Open a page and choose Edit (from the page's actions menu). The same panel opens with the current Markdown.
• An edit note is required when you edit. Before saving a change you must enter a short note describing what changed — if you leave it blank, AB Projects asks you to add one "so your team knows what changed." (New pages don't need a note; edits do.)
• Saving creates a new version rather than overwriting — the previous version is preserved.

Version history and restore

• Every page tracks a version number and the latest editor and time.
• Open History from the page's actions menu to see past versions, each with its edit note — so the "why" of every change is on the record.
• You can restore an earlier version from the history list. Restoring brings that content back as the current page (and is itself recorded as a new version).

Deleting a page

• Delete is available from the page's actions menu, deliberately placed apart from Edit/History so it isn't clicked by accident.
• Deleting removes the page from the tree. Treat it as a careful action — prefer editing or restoring over deleting when you just need to change content.

Tips

• Use the parent path to build a clear structure (e.g. engineering/runbooks) instead of a flat list of pages.
• Write meaningful edit notes — they're what History shows and what teammates rely on to understand a change without diffing.
• Use the live preview to check formatting (headings, code blocks, links) before saving.
• If an edit went wrong, restore the previous version from History rather than rewriting from memory.

With Markdown, live preview, mandatory edit notes, and full history with restore, Documents stay easy to write and safe to change.