Antylogic
DemoApp login

399 operational guides

Docs sections
DocsDocumentation
Device

Select Docs Device Variant

Switch a public Docs article between Mobile, Tablet, and Web so the page reloads the public index and selected article with the chosen platform, then shows the closest available media variant.

In this article

Use this guide when a public reader, support operator, or capture producer needs to review the same Docs article in a Mobile, Tablet, or Web context.

The Device selector is temporary page state. It changes the platform sent to the public Docs API and affects media resolution, but it does not save a preference or change product data.

Before you start

  • A public Docs route is available at /docs, /manual, /wiki, or an article route under one of those prefixes.
  • The public docs service can load the generated docs bundle, and the landing page can reach PUBLIC_API_BASE_URL.
  • The current landing theme resolves to light or dark; the Device selector does not choose the theme.
  • For a visible English media-variant example, use /docs/calendars/en-calendars-view-general because it has published calendar media variants.
  • No Harbor Demo Group login, organisation role, location membership, or demo session is required for this public action.

Instructions

  1. 1.

    Open a public article

    Open /docs/calendars/en-calendars-view-general, or open /docs, /manual, or /wiki and let the page select the first available article. The public page should load without asking for an account.

  2. 2.

    Check the current device

    Find the Device segmented selector in the article header. It offers only Mobile, Tablet, and Web. The starting value is detected from the viewport: mobile below 768px, tablet for coarse pointer or up to 1180px, otherwise web.

  3. 3.

    Select a variant

    Click Mobile, Tablet, or Web. The page refetches the public index and then the selected article using the same locale and theme with the new platform. If the user changes device quickly, the previous request is cancelled and the latest choice wins.

  4. 4.

    Review refreshed media

    After loading finishes, review the article content and media. Media first tries the selected platform and theme, then falls back to another available asset variant. If no source exists, the pending media placeholder remains.

  5. 5.

    Keep the boundary clear

    Treat Device as a public documentation viewing control. It is not the TPV terminal platform, does not edit documentation, does not submit search, and is not stored in the URL, browser storage, account, or backend state.

Validations and limits

  • The public selector renders exactly three values: Mobile, Tablet, and Web.
  • Docs requests include locale, platform, and theme; q is only sent by API callers or search flows when provided.
  • The public Docs route does not require authentication for this action.
  • The backend normalises locale to es or en, platform/device to mobile, tablet, or web, and theme to light or dark.
  • Invalid or omitted platform values normalise to web for direct API callers.
  • The index response echoes platform, but article_count and section membership are not platform-specific.
  • Article detail resolves by section slug and article slug, or by legacy article id when only one path segment is provided.
  • Media resolution may return src, resolved_platform, resolved_theme, available_platforms, and available_themes; missing media renders the pending placeholder.
  • Current content freshness should be checked when captures depend on media: backend/docs-content/articles.json was generated on 2026-06-18 while the update context is dated 2026-06-24.

Expected result

The reader remains on the public article, the selected device button is highlighted, and the article reloads through /api/public/docs with the selected platform so media can resolve to the closest available device and theme variant.

Related articles