# Docs — a documentation hub at /docs

> The official Docs plugin — a modern documentation site with section menus, contents, search, copy buttons, Markdown and llms.txt for AI, JSON bundle import, drag-to-reorder and multiple languages

Source: https://anasaki.live/docs/en/store/plugin-docs

The **Docs** plugin (`docs`) builds a documentation hub at `/docs` that looks like a modern docs site, uses your theme's colours and fonts, and sits inside your site's header and footer — the docs you are reading are made with it.

![](/uploads/2026/11/plugin-docs-article-846460574.png)

A Docs article — menu on the left, contents on the right

## The pages you get

| URL | Page |
| --- | --- |
| `/docs` | Home: search box, product cards and &#34;Quick start&#34; |
| `/docs/` | Articles grouped by section |
| `/docs//` | An article: left menu, breadcrumb, &#34;On this page&#34; contents, previous/next |
| `/docs//.md` | The article as Markdown (the &#34;Copy Markdown&#34; button) |
| `/docs/llms.txt` | Contents for AI per llmstxt.org (`llms-full.txt` = every article in one file) |

Search with **Ctrl K** or `/` on any page. On phones the menu is a drawer, and `/docs` and every article are in the sitemap of the [SEO](/docs/en/store/plugin-seo) plugin.

## Writing an article

1. Left menu **Docs** → **Add new** — the editor is the same as for posts
2. Enter the title, content and **excerpt** (shown under the title and used as the meta description)
3. Set the **product** (its id from the settings), the **section** (e.g. &#34;Getting started&#34;) and the **order**
4. Publish — only published articles are shown

In the content, H2/H3 headings become the contents automatically, code blocks get a copy button, and you can use the `dx-note` / `dx-tip` / `dx-warn` boxes, `dx-cards` link cards and `dx-tabs` code tabs.

## The Docs admin page

![](/uploads/2026/11/plugin-docs-admin-818911083.png)

The Docs admin page — drag to reorder articles and sections

- **Drag ⠿** to reorder articles or sections and to move articles between sections, ✎ to rename a section, then press **Save order**
- **Import a JSON docs bundle** — articles with an existing slug are updated, not duplicated (handy for writing docs in Git and importing them)
- The **Settings** tab (administrators): the home page heading and intro, products (add/remove/reorder), the &#34;Edit this page&#34; link and redirects from old links

A minimal bundle:

```json
{ &#34;products&#34;: [ { &#34;id&#34;: &#34;guide&#34;, &#34;name&#34;: { &#34;th&#34;: &#34;คู่มือ&#34;, &#34;en&#34;: &#34;Guide&#34; }, &#34;icon&#34;: &#34;📘&#34; } ],
  &#34;docs&#34;: [ { &#34;slug&#34;: &#34;install&#34;, &#34;title&#34;: &#34;Install&#34;, &#34;excerpt&#34;: &#34;…&#34;, &#34;product&#34;: &#34;guide&#34;,
              &#34;section&#34;: &#34;Getting started&#34;, &#34;order&#34;: 1, &#34;content&#34;: &#34;<p>…</p>&#34; } ],
  &#34;legacyRedirects&#34;: [ { &#34;from&#34;: &#34;/blog/getting-started&#34;, &#34;to&#34;: &#34;/docs/guide/install&#34; } ] }
```

### Multiple languages (1.2.0)

Articles in another language live at `/docs//…`, e.g. a Thai site has English docs at `/docs/en`. Set the article's **Language** to `en` and its **Link slug** to the slug of the original article (the post's own slug must still be unique, e.g. `install-en`).

- Every page has a 🌐 link to the other language: translated articles lead to the translation, untranslated ones to that language's product page
- Search, `llms.txt`, Markdown and the sitemap are per language, and pages tell Google about `hreflang`
- In a JSON bundle, add `&#34;lang&#34;: &#34;en&#34;, &#34;base&#34;: &#34;install&#34;` to the translated article

The plugin ships with no articles — once installed it is an empty hub with one product (&#34;Docs&#34;, id `general`) until you write or import some.

> [!NOTE]
> The Plugin Store's **Developers** page pulls its list of developer guides from `/docs/search.json` of the docs site the Store administrator set — add or edit articles in Docs and that page follows within 10 minutes.
