Build audio guides, tours and resource pages

Open this page type in your workspace. Choose the scan domain, complete the fields above and attach the appropriate workspace files. Save a draft before publication.

Save the draft and check its preview before publishing. After publication, open the public link as a visitor and verify the displayed information and available actions.

Audio guide: Start with an MP3 or PCM WAV recording that you own or may publish. Give each track a meaningful title, provide a transcript for people who cannot listen, and decide whether the viewing page should show a download button. Keep a local original before uploading.

Visitors open a mobile audio page and press Play themselves. Each track has its own controls and optional transcript. A selected start and end restrict the playback window; they do not create a new shortened audio file. The full original remains the source, so playback settings are not a method of protecting unpublished audio.

Save the revised playlist as a draft, preview it, then publish. Visitors continue using the same code. Replacing a recording requires selecting the new file and publishing the page again; uploading a file alone does not change the published experience.

Up to 20 tracks per page. MP3 or PCM WAV, 20 MB per file. Uses the ordinary published-page allowance on Pro and above.

Tour guide: List the places a visitor should encounter and place them in walking order. Prepare a clear description, an optional photograph and an optional audio explanation for each stop. Use a map link that points to the actual stop rather than a general venue homepage.

The scan opens a stop index. A visitor chooses a numbered stop, reads its explanation, listens to its optional recording and can open the map or move to the next stop. The page does not collect a visitor location, mark a stop as visited or require a tracking permission.

Change a temporary closure, a stop photo or a narration in the draft. Publish after checking the whole route and its external map links. Existing printed signs continue to open the route; a changed stop order should be checked against the physical signage.

Up to 30 ordered stops per page. Optional image and audio attachments use the normal 20 MB file limit. Pro and above; one published-page allowance.

Resource library: Group the files and links your audience repeatedly needs. Use categories such as Installation, Care and Warranty, and choose descriptive resource titles. Remove confidential files before publishing: the resulting library is available to anyone with its link.

Visitors browse a mobile resource list, select a category or search the titles and descriptions. A file opens through the platform file address; a related link opens your chosen website. Search and category selection run locally in the page and do not send the search words to another search service.

When a manual changes, upload the replacement, select it in the relevant row and publish. Keep the title and description specific enough to identify the current version. Review external links periodically, because another website can change independently of your library.

Up to 60 resources per page and 20 MB per uploaded file. Pro and above; one published-page allowance. Public libraries are not a private document portal.

Portfolio: Choose completed work you have permission to show. Prepare a title, a description of the problem and your contribution, and an optional representative image for each project. Remove client names or sensitive details that are not intended for public viewing.

The code opens a responsive project grid. Visitors read each project description and may open its related project website. On a narrow phone the grid becomes one column, keeping the image and explanation together rather than reducing the content to tiny cards.

Keep previous work accurate and avoid presenting a draft project as completed. Check image permission and visitor access before publishing. Revisit the order when the audience changes, such as switching from recruitment to an exhibition.

Up to 30 project entries per page. PNG/JPEG images use the existing 20 MB file limit. Pro and above; one published-page allowance.

Teaching materials: Break the material into lessons with an explicit learning goal. Write the instructions students need, then attach the relevant file or link. Choose category names that match the course sequence and ensure students can open external resources without a staff account.

Students scan the code, browse numbered lessons and filter or search the materials. Each lesson keeps its written instructions next to its file and related URL. Reading this public page does not by itself create an attendance or completion record.

Update a lesson’s instructions and select a new file in the draft, then publish. The classroom handout keeps its scan address. When linking a training workflow, test the learner role and actual record submission independently of the public material page.

Up to 60 lessons per page; 20 MB per file. Pro and above, using one published-page allowance. Recorded training consumes the separate workflow quotas.