View Public Article Media

In this article

Before you start

• Open the landing Docs area through /docs, /manual, or /wiki. No sign-in, organisation membership, location membership, role, or demo session is required for this public surface.
• For the English GB article, open the route with ?lang=en. Direct API calls should use locale=en, not en-GB.
• PUBLIC_API_BASE_URL must reach a backend serving /api/public/docs; local landing defaults use http://localhost:8081.
• backend/docs-content/articles.json and the docs asset root must be available so resolved media can be served from /api/public/docs/assets/{path}.
• Use /docs/attendance/en-attendance-view-board?lang=en to show a resolved image, a resolved video, and planned placeholders. Use /docs/access/en-access-users-create-location-internal?lang=en to show pending planned media only.

Instructions

1. 1.

   Open the public article

   Open /docs/attendance/en-attendance-view-board?lang=en from the landing site. The article title View the Clock in/out Board, the Docs breadcrumb, and the Device selector should be visible without a login or membership prompt.

2. 2.

   Set the device context

   Use the Device selector when the capture needs a specific variant. The public article request uses locale=en, the selected platform such as mobile, tablet, or web, and the current light or dark theme.

3. 3.

   Check the primary media

   After Reports and feedback, confirm that the first published media item with a resolved source appears before In this article. In the English attendance article, the primary figure is Clock in/out entry point from Harbor Soho home.

4. 4.

   Review the remaining captures

   Scroll to Flow screenshots and videos. Additional media stays in this section, including the video Open and scan the Clock in/out board, while planned unresolved items show Pending generation.

5. 5.

   Interpret placeholder and asset states

   Pending generation means the media metadata has no resolved src. It is not an upload, edit, publish, or generation workflow. If a resolved asset later returns 404, the page relies on normal browser image or video failure behaviour.

6. 6.

   Verify a direct asset when needed

   For capture QA, open /api/public/docs/assets/iphone/light/en/attendance-view-board/attendance-view-board-open-and-scan.mp4. A valid video asset opens with browser controls; invalid, traversal, or missing paths are rejected by the public asset route.

Validations and limits

• The public Docs media surface is read-only and does not generate, upload, edit, delete, or publish media assets.
• The landing request sends locale=en for English, platform or device as mobile, tablet, or web, and theme as light or dark.
• The first media item that is both published and resolved becomes the primary figure; if no item qualifies, no primary figure is shown above the overview.
• Resolved videos render with browser-native controls and do not autoplay. Resolved images render inline with lazy loading and object-contain sizing.
• A trimmed empty src is treated as unresolved and renders Pending generation instead of requesting an asset.
• Asset URLs are limited to the configured docs asset root. Empty paths, dot paths, traversal attempts, and missing files return 400 or 404.
• The focused backend test TestHandleDocsIndexArticleAndAsset verifies the public index, article detail media URL rewriting, and asset serving path.

Expected result

A public reader can inspect article media directly from the landing Docs article. Published images and videos render when their sources resolve, planned media remains clearly marked as pending, and the page never exposes a public editing or generation workflow.