Pages and navigation
Builds on The editor.
The page tree on the left of the editor is the guide's sidebar: its groups and pages in the order readers see them.
Add a page
#Choose + (New page) at the top of the tree.
Title
#Type the page's Title.
Group
#Pick its Group in the sidebar, or New group… and type a Group name. A new page goes after the page you have open when it's in the same group, else at the end of the group.
Address
#The Address fills in from the group and title, like
/guides/slack-notifications. Change it if you like.Create it
#Choose Create page. It starts as a draft: readers see it after the next publish.
Move, reorder and delete
#Each page in the tree has a menu (…) with Move up, Move down, Move to another group, and Delete page. The new order is saved straight away and reaches readers at the next publish.
Deleting a page asks first. If it's on the published guide, it disappears at the next publish and old links to it stop working, so add a redirect if people link to it. You can't delete the home page, or a page someone else is editing.
Page settings
#The panel on the right of the editor (Page settings on smaller screens) has:
- Address: where the page lives in the guide.
- Show in the sidebar: turn it off to hide the page.
- Icon: shown beside the page in the sidebar, or No icon.
- History: the page's last saves, and See all versions. See History and versions.
Page addresses
#An address starts with / and has up to 6 parts, like /guides/connect-postgres. Each part uses lowercase letters, numbers and hyphens. The editor tells you what's wrong as you type:
- it can't end with
/or contain// - it can be at most 200 characters
- two pages can't have the same address
- it can't start with a part the guide uses itself:
docs-assets,mcp,md,og,changelog,public,api-reference,api-reference-jsonorvideo-scenes, andvideo-scenescan't be any other part either
When you name a page in a group whose name can't start an address (a group called "API reference", say), the suggested address leaves the group out: /payments, not /api-reference/payments.
The home page is always /. Its address can't change, it can't be hidden, and it can't be deleted.
When you change the address of a page that's on the published guide, Markdrop Guides adds a redirect from the old address to the new one in Redirects, so links people saved keep working after the next publish. Change it again and that redirect follows the page: there's never a chain. Redirects that pointed at the old address are moved to the new one too. A page that was never published gets no redirect, since nobody has a link to it.
Hidden pages
#Turn off Show in the sidebar to hide a page. It moves to Hidden pages at the bottom of the tree. A hidden page is still published and opens at its address: it's only left out of the sidebar. Use it for pages you link to from elsewhere, or for old pages you keep for existing links. Turn it back on to put the page at the end of the last group.
Redirects
#Moved or renamed a page? Send its old address to the new one in the guide's Settings › Redirects, so links people saved keep working. Admins edit redirects.
Add a row
#Choose Add a redirect.
Fill it in
#Type the Old address, like
/guides/postgres, and where it Goes to: a page of the guide (/guides/connect-postgres, optionally with a#section) or anyhttps://address.Save
#Choose Save (it says how many). Redirects go live at the next publish.
A row is refused when it would break something: an old address that's still a page of the guide, the home page, one of the guide's own addresses like /llms.txt, a page that doesn't exist, a redirect to itself, the same old address twice, or a chain (an address that redirects again). Readers get a permanent redirect, and only when no page or file of the site is at that address.
Pages imported from GitBook keep their old addresses working without rows here, alongside the ones you add. See Import from GitBook.