Antylogic
DemoApp login

399 operational guides

Docs sections
DocsPublic Docs
Device

Resolve a Legacy Public Article Link

Use this guide when an old public help link contains only one article id, such as /manual/en-access-users-create-location-internal. The public Docs screen loads the English Docs index, replaces the old path with /docs/access/en-access-users-create-location-internal, and displays the article without requiring sign-in.

In this article

Old public help links under /docs, /manual, and /wiki still open the public Docs screen. When the link only contains one article id, the screen resolves it against the loaded index before showing the article.

In the GB example, /manual/en-access-users-create-location-internal becomes /docs/access/en-access-users-create-location-internal and shows Create an Internal Location User for Harbor Soho.

Before you start

  • The public Antylogic landing site is reachable and can display the Docs screen.
  • PUBLIC_API_BASE_URL points to an API host that serves /api/public/docs.
  • The English Docs bundle includes en-access-users-create-location-internal.
  • No authenticated user, organisation membership, location membership, role, or demo session is required.
  • For the GB English context, the public Docs locale resolves to en.

Instructions

  1. 1.

    Open the old public link

    Open /manual/en-access-users-create-location-internal, or the equivalent one-segment path under /docs or /wiki. The page stays public and read-only.

  2. 2.

    Let the Docs index load

    The screen requests GET /api/public/docs with locale=en plus the selected platform and theme. Legacy resolution only runs after that index returns successfully.

  3. 3.

    Confirm the canonical path

    When the loaded summary matches the trimmed and slugified id, the browser replaces the old path with /docs/access/en-access-users-create-location-internal. The /manual or /wiki prefix is not preserved.

  4. 4.

    Read the article

    The normal article detail request loads GET /api/public/docs/access/en-access-users-create-location-internal with the same locale, platform, and theme parameters, then renders Create an Internal Location User.

  5. 5.

    Handle unresolved links

    If the id is missing from the current locale index, the URL is not replaced and no article detail is requested. Share a published canonical Docs link when the old id cannot be found.

Validations and limits

  • The legacy route must match /docs/:articleId, /manual/:articleId, or /wiki/:articleId.
  • The incoming id is trimmed and normalized with the frontend slug rules before matching.
  • A legacy id resolves only when a loaded article summary has the same slug or the same id after normalization.
  • The replacement target always uses /docs/{sectionSlug}/{articleSlug} and uses browser history replace.
  • If the index request or detail request fails, the Docs screen shows the generic load error.
  • Two-segment /manual/:sectionSlug/:articleSlug and /wiki/:sectionSlug/:articleSlug routes render in place and are not canonicalized only because of their prefix.

Expected result

The visitor lands on the current public article without authentication, and the browser history contains the canonical /docs/access/en-access-users-create-location-internal route instead of the old one-segment link.

Related articles