Source: https://docs.pageloop.ai/guides/working-in-the-knowledge-base

# Working in the Knowledge Base

# Working in the Knowledge Base

Use **Knowledge Base** to find an article, organize your navigation, and edit a page directly. Your edits stay unpublished until you complete the publishing flow.

> [!NOTE]
>
> The tree actions, Markdown editor, previews, and publishing controls below apply to a repo-backed Pageloop docs site. Connected help centers can have different editing controls. You need an editable site and permission to make changes; a change set marked **This change set is read-only here** does not offer tree editing. Generated API pages have restricted actions rather than the full page menu.

## Open the tree from Home

1. From **Home**, select **Knowledge Base** in the sidebar. You do not need to open an Inbox item first.
2. Check the workspace selector above the tree. **Main** shows the main workspace; select a change set when you want to work in that change set instead.
3. Expand a folder with its chevron, then select a page to open it in the editor.

### Add a page, folder, or tab

1. Click the plus button labeled **Add page or folder** above the tree.
2. Select **New page**, **New folder**, or **New tab**.
3. Enter a name in the inline creation row and press **Enter**. Press **Escape** to abandon the creation. Clicking away also commits the name, including an unchanged default name.

**New page** creates a page you can edit. **New folder** groups navigation entries. Both start at the root of the first tab. **New tab** adds a separate navigation block at the end of the tree.

To create inside a particular folder, hover over the folder and click its plus button, labeled **Add to** followed by the folder name. Choose **Add page** or **Add folder**. A tab heading also has a plus menu for adding content to that tab.

![New page, New folder, and New tab in the Knowledge Base creation menu](/images/uploads/screenshot-e072aea1.png)

### Give a folder a landing page

A landing page lets readers open an overview from the folder's name while using the chevron to expand its children.

1. Add content to the folder first. **Add landing page** is disabled for an empty folder.
2. Open the folder's three-dot **Folder actions** menu.
3. Select **Add landing page**.
4. Select the folder name to edit its landing page. Use the chevron separately to expand or collapse the folder.

**Remove landing page** returns the landing page to the folder as its first child; it does not delete the page. This action requires another child in the folder and is unavailable for a folder whose pages are generated automatically.

### Search for a page

Click the magnifying-glass button labeled **Search the knowledge base**, enter your query, and select a result to open the page. Use search when you know the subject but not the page's location in the tree.

## Change a page's settings or location

Hover over a page and open its three-dot **Page actions** menu.

| Action         | What to do                                                                                                                                                                                                            |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rename**     | Enter the page title and confirm with **Rename**. To change the public address instead, use **Edit slug…**.                                                                                                           |
| **Add icon…**  | Choose an icon for the navigation entry. If an icon is already set, the menu says **Change icon…**.                                                                                                                   |
| **Edit slug…** | Set the page's full public path, as described below.                                                                                                                                                                  |
| **Redirects…** | Manage old addresses that send visitors to this page.                                                                                                                                                                 |
| **Add cover**  | Choose an image in **Select cover image**. Use **Files** to upload an image, or **URL** to enter an HTTPS image address and click **Use image**. A page with a cover offers **Remove cover** instead.                 |
| **Move to…**   | Choose a destination folder or tab. For a destination with children, open its submenu and choose **Move here** to use the parent itself. This changes navigation placement; use **Edit slug…** for an address change. |
| **Copy link**  | Copy the page's live address. This action is available only after the page has a published address; an unpublished slug edit does not change the copied live link yet.                                                |
| **Delete**     | Review the confirmation before deleting. A published page is removed from the live site on the next publish, not when you first select Delete.                                                                        |

![Page actions for a published Knowledge Base page](/images/uploads/screenshot-a4919535.png)

### Change a slug without losing old links

A slug is the page's address on the live site, not its title or its position in the tree.

1. Open **Page actions → Edit slug…**.
2. In **Address**, enter the whole path, such as `guides/writing-docs`, not just `writing-docs` if you want the page to remain under `/guides/`.
3. Check **Will be served at** to verify the normalized path.
4. Click **Save**, then publish the change when ready.

The address changes on the live site after the next publish. The old address redirects automatically. Update links you control to use the intended address after publication, and check existing links as part of your review. If the page is open in another browser tab, reload that tab before editing it.

If the page has an explicit slug, **Use file path** removes that override and returns the address to the file-derived path.

Use **Redirects…** when you need additional old addresses to lead to this page—for example, a retired article address or a previously shared URL beyond the old slug handled automatically.

1. Open **Page actions → Redirects…** on the destination page.
2. Enter an old path in **New redirect from**. The destination is fixed to the page whose menu you opened.
3. Choose **Permanent (308)** for a lasting move or switch to **Temporary (302)** for a temporary route.
4. Click **Add redirect**. To revise an existing rule, edit its source or permanence and click **Save**.
5. Click **Done** and include **Site settings** in your next publish.

Redirect rules are site-wide and go live with the next publish. Review any validation warning rather than assuming a saved rule points where you intended.

### Rename, move, or delete a folder

Open **Folder actions** to **Rename** a folder, **Add icon…** or **Change icon…**, manage its landing page, or choose **Move to…**. A folder cannot move into itself or one of its descendants.

**Delete** is disabled while the folder holds content. Move or delete the content first. Deleting an eligible folder also removes its empty subfolders. Tab actions similarly offer **Rename**, icon selection, and **Delete**; a tab must be empty before you can delete it.

You can also drag pages and folders in the tree to rearrange navigation. Check the drop indicator before releasing the item.

## Edit a page

Select the page in the tree. In **Visual**, edit the title, description, and body directly. Use **Markdown source** when you need to work with the page's MDX source. Edits autosave as a draft; saving is not publishing. Check the save status before leaving, previewing, or publishing, and resolve any save error first.

### Insert a block

1. Place the cursor in the body where you want the block.
2. Type `/` to open **Insert Block**. Continue typing a block name to narrow the list.
3. Click a block, or use the arrow keys and **Enter**. Press **Escape** to dismiss the menu.
4. Replace the inserted block's starter content with your own content.

The menu includes text and headings, lists, quotes, code blocks, tables, images, diagrams, callouts, cards, steps, tabs, and accordions. For example, type `/Note` for a callout or `/Card group` for a grid of cards. A slash stays literal inside code rather than opening the menu.

### Review the page diff

Click **Show differences** in the page toolbar to compare the draft with the published page. Review body edits and **Page details**, which includes changed metadata such as the title, description, or slug.

Where a revert control is available, use it to restore that block or field to its published value. Reverting changes the draft; it does not publish the result. A never-published page has no published version to restore. Close the differences view to continue editing.

### Preview before publishing

The preview control beside **Publish** builds a temporary site so you can inspect unpublished changes without publishing them.

- In a change set, click **Generate preview**, wait for the preview to become ready, then use **Open preview**. The ready preview opens in a separate tab.
- On Main with unpublished edits, **Preview your unpublished changes** opens **Preview these changes**. Review the **Branch name** and the selected pages, navigation, and site settings. Continuing moves the selected drafts into a change set for preview; this is not just a different view of Main.
- On Main without previewable changes, the control asks you to select or create a branch instead.
- After a preview is ready, **Preview options** offers **Rebuild** and **Close preview**. Rebuild after further edits to inspect the updated result.

## Resolve a draft that has fallen behind Main

If the underlying page changes after your draft was taken, a drift banner warns you that the draft is based on an older version. The banner keeps your draft rather than silently replacing it.

For a changed page, the banner offers:

- **Bring in the GitHub changes** — bring upstream edits into your draft. If the edits overlap, review the conflict chooser and choose the content to keep before applying the result.
- **Take the GitHub version** — drop your draft and use the upstream version. Read the confirmation carefully; dropping the draft cannot be undone.

A moved page can also show its updated path. If the page was deleted upstream, the banner offers **Revert delete** to restore it as a new page for publication, or **Sync delete** to drop your draft and leave it deleted. If another page has appeared at your new draft's address, **Keep mine at another address** lets you preserve your draft at a different path.

Resolve the banner and re-read the resulting draft before publishing. If publishing warns that an upstream change would be replaced, return to the affected page rather than choosing **Publish anyway** without reviewing what would be overwritten.

## Publish the reviewed changes

1. Check that the editor has saved your latest edit, then open **Publish**.
2. On **Main**, review the items under **Pages**, **Navigation**, and **Site settings**. Select the items you intend to publish; the popover is not limited to the page you have open.
3. Enable **Open a pull request instead** when you want repository review. This option is required for a protected branch.
4. Check the selected item count, then use **Publish** followed by the item count to submit the selection.
5. If a pull request opens, review and merge it in the repository. Otherwise, wait for the site's sync to complete. Submission alone does not mean the live site has updated.

![Publish popover on Main with navigation and site settings selected](/images/uploads/screenshot-18ab17b3.png)

In an editable change set, the popover names the **Branch** and lists what the push carries rather than offering Main's per-item selection. **Push to branch** sends the changes for repository review. **Push & merge**, or **Merge** when there is nothing left to push, includes a separate merge confirmation. The published site updates after the merge syncs back.

For a review-backed change set, the popover can instead offer **Publish accepted review**. Only recorded accepted changes are included; pending and rejected changes stay out of the proposal.

## Related

- [The Pageloop sidebar](/guides/pageloop-sidebar)
