Skip to Content
Enderdash

Write and publish knowledge pages

Organize player guides, review public updates, and keep your server handbook current.

Before you begin

Open Knowledge base in the organization sidebar. Editing uses organization workspace access: owners and admins have elevated access, while members need the team-collaboration plan feature.

Only owners and admins can publish, unpublish, or change public knowledge-base settings. Public content is available to visitors outside the organization.

Create and save an internal page

  1. Use Create page, choosing a template if it suits the task.
  2. Enter a title and write the instructions or reference content.
  3. Watch the draft save state while editing.
  4. Choose Save changes to apply the draft to the saved page.
  5. Reopen the page and confirm the saved content.
Demo knowledge base with the page list on the left and the selected page on the right.
The demo uses sample data. A lock next to a title marks an internal page.

Autosaved drafts and saved page content are different states. Done exits editing; use Save changes when there are unapplied changes.

Publish the page

As an owner or admin:

  1. Review the content for credentials, internal addresses, and private operational information.
  2. Save outstanding changes.
  3. Open Knowledge page actions and choose Publish page.
  4. Confirm publication, then choose Open public page.
  5. Verify the public page without a dashboard session.

Saved edits stay internal until you publish an update. The review dialog previews the saved page and compares its title, Markdown, and metadata with the published snapshot. An autosave, Save changes, or revision restore does not replace public content.

Organize pages

Use Create subpage from a page's actions to create a child page. Use Move page to choose a parent and a position before a sibling, or place it at the end. Moving a page keeps its URL. A page cannot become its own parent or move below one of its descendants.

Public readers get breadcrumbs, collapsible navigation, a heading outline, child-page links, and previous/next links. Search ranks titles, aliases, and saved text and returns excerpts. It supports command names, prefixes, and small typing mistakes.

Set an audience and owner

Open Page settings to set:

  • The audience
  • Search aliases
  • The owner or team
  • The verification date and the next review date
  • The applicable servers, game mode, and season

Organization staff only pages cannot be published or returned by public search, Discord guide lookup, or the in-game guide command. An admin must change a published page to this audience. Doing so unpublishes it. Other metadata changes become public with the next publication.

For translations or season variants, give related pages the same Variant group, such as claiming. Set each page's language code and season. Publish each variant separately. The public reader links the available variants and uses the site's default language and season when choosing navigation entries. If no exact variant exists, it prefers English and an unseasoned guide.

Change the public site

Open the … menu next to the search field and select Settings. An owner or admin can set:

  • The title and description
  • The accent color and typography
  • The layout: documentation or help center
  • The homepage content, in Markdown
  • The default language and the current season
  • A Discord invite

For connection guides, copyable commands, steps, persistent Java/Bedrock tabs, reusable content, and custom interactive widgets, see Knowledge blocks and widgets.

Restore a revision

Open View revision history and choose Compare to inspect a prior version and its differences from the saved page. Choose Restore on the intended revision and confirm with Restore revision. Then verify the working page, and publish an update when it is ready.

If a concurrent change blocks saving or restoring, read the latest page again and reconcile the changes. Do not repeatedly overwrite another editor's work.

Unpublish or archive

Unpublish page removes public access while retaining the internal page and revision history. Archive page removes the page from the active knowledge base while retaining its revision history.

To recover earlier content, use revisions. To investigate a missing public page, use publication troubleshooting.

Continue

Was this page helpful?

Send a quick note if anything is missing or unclear.

Last updated on