Antylogic
DemoApp login

399 operational guides

Docs sections
DocsDocumentation
Device

Open a public Docs article

Lets you check that a public help route opens the right article from the landing, without signing in, and shows content, steps, validations, result and published media from the Docs bundle.

In this article

Use this guide to check a public Docs publication before sharing it with support, content or external users.

The flow starts from `/docs/access/en-auth-native-login?lang=en`, loads the public index, resolves the article detail and shows whatever is available in `backend/docs-content/articles.json`.

Before you start

  • The landing must be available at `APP_WEB_URL`.
  • The landing must point to the public backend through `VITE_PUBLIC_API_BASE_URL` or use the `http://localhost:8081` fallback.
  • The backend must have `DOCS_CONTENT_PATH` pointing to a valid `articles.json` or use `./docs-content`.
  • The bundle must contain the English article with section `access` and slug `en-auth-native-login`.
  • To review published media, `DOCS_ASSETS_PATH` must contain the asset referenced by `media.src`.

Instructions

  1. 1.

    Open the public article route

    Open `APP_WEB_URL/docs/access/en-auth-native-login?lang=en`. The public Docs screen must load without asking for a user, password, organisation or location. If you enter from `/manual/...` or `/wiki/...`, the view is the same and internal links go back to `/docs/...`.

  2. 2.

    Confirm language, device and theme

    Check that the article is shown in English and that the `Device` selector reflects the variant in use. If the device is changed, the screen requests the index and detail again with `locale`, `platform` and `theme`, but it does not change the browser route.

  3. 3.

    Review the published content

    Verify that the title, summary, `Reports and feedback` notice, main media if published, prerequisites, steps, validations, result, related links and table of contents appear. The detail must only load after finding in the index a `DocsArticleSummary` with `section_slug=access` and `slug=en-auth-native-login`.

  4. 4.

    Check the public contract

    For a technical publication review, open `GET /api/public/docs/access/en-auth-native-login?locale=en&platform=mobile&theme=light` and confirm that the response includes `version`, `locale`, `platform`, `theme`, `section` and `article`.

  5. 5.

    Verify the published media

    If the article returns `media.src`, check that it is served from `/api/public/docs/assets/...`. For this case, the expected variant is `/api/public/docs/assets/iphone/light/en/auth-native-login/auth-native-login-validation-clip.mp4`.

  6. 6.

    Handle unavailable states

    If the index does not contain the article, the detail fails or the asset does not exist under `DOCS_ASSETS_PATH`, record the problem as a bundle, configuration or media publication gap. The public UI must not present partial data as valid.

Validations and limits

  • The action is public: any visitor can read the article if it is in the bundle.
  • The canonical article route is `/docs/{sectionSlug}/{articleSlug}` even though the `/manual` and `/wiki` aliases exist.
  • `locale` is limited to `es` or `en`; the landing falls back to English if its language is not among the generated locales.
  • `platform` is normalised to `mobile`, `tablet` or `web`; `theme` only distinguishes `dark` and treats everything else as `light`.
  • The public endpoint only allows `GET` and `HEAD`; other methods return `405 metodo no permitido`.
  • Public assets are cleaned and only served if the path stays inside `DOCS_ASSETS_PATH`.
  • The verified bundle declares `version=2026-06-18`; if later changes are expected, they must be regenerated in `backend/docs-content/articles.json`.

Expected result

The operator confirms that the public Docs article opens from the landing, uses the right public contract and shows only content and media published from the bundle.

Related articles