Maintain and share knowledge pages
Review reader feedback, move content with Markdown archives, and connect in-game and Discord lookup.
Use this guide after your first pages are published. It covers the upkeep of a knowledge base and the places where players can find it. To write and publish a page, see write and publish knowledge pages.
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.
Review feedback and overdue guides
Open the … menu and select Maintenance. It lists pages whose review date has passed, along with their owners. It also shows public article feedback, outdated-content reports, correction suggestions, and requested guides from unsuccessful searches. Open the affected page, make and review changes, then mark the report reviewed. Suggestions never edit an article automatically.
Use Check article links in Page settings to find paths that do not match an active page. This checks article paths. It does not fetch external websites or validate section anchors.
Import and export Markdown
Open the … menu and select Import / export to download saved pages as a ZIP, including hierarchy, metadata, and uploaded images. Working autosaves and widget code are not included. External images remain linked; the exporter lists images it could not include.
For an import, choose a ZIP of Markdown files and inspect the page list. Enderdash archives preserve hierarchy through enderdash.json. Other Markdown archives can use folders and index.md pages. A plain archive can supply a front-matter title; otherwise the first main heading or filename supplies it. Executable MDX is not imported.
Choose Import N unpublished pages, where N is the number of pages in the archive, to create new pages. Existing pages remain intact, conflicting slugs get a suffix, and recognized relative article links are rewritten. Local images are uploaded through the usual signed image-upload flow. Review each imported page before publication.
| Limit | Value |
|---|---|
| Pages in one archive | 50 |
| Expanded archive content | 30 MB |
| Markdown in one archive | 10 MB |
| Markdown in one page | 1 MB |
| Uploaded images in one export | 50 |
| Image data in one export | 20 MB |
For a larger import, split the content into several ZIP files.
Connect player help
For Bukkit/Paper servers, set knowledgeBaseOrganization in the agent's config.yml to the organization's slug and reload the agent. Players can use /enderdash guide to open the handbook or /enderdash guide claiming to receive up to three matching public links. Lookup uses the public knowledge API and never sends the agent key. On a failed or throttled lookup, players receive a browser search link.
You can share a search link such as https://kb.enderdash.com/@your-server?q=claiming in Discord. For the Discord /guide command, see Discord guide lookup.
The dashboard's Server handbook suggests saved organization guides for the current workflow. Public status pages link to connection guides when the organization's knowledge base is enabled.
Continue
Use knowledge blocks and widgets for guide components. To serve the knowledge base from your own hostname, see Connect a custom domain.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on