پرش به مطلب اصلی

Landing pages and tiles

A landing page in Scoutello is a configurable guest web app: a localized page assembled from ordered tiles (modules). Teams publish landing pages behind short links or QR flows; guests open them in a mobile browser for the typical journey.

Each landing page is stored as structured content together with its tiles. The dashboard exposes authoring controls, and guests receive a responsive layout that loads the published modules together.

Concepts​

Guest web app (landing page)​

  • Landing page: organization-scoped experience shell with its own slug or domain options, visuals, multilingual text, tiles, presentations, analytics, and optional assistant context.
  • Guest experience: Guests open landing pages in the browser-first guest app from a link, QR code, or embed. Scoutello loads the published page and lays out tiles in a responsive grid.
  • Distribution: Typical entry is URL, QR code, or share link; teams may tie landing pages to widgets, marketing pages, or other entry points documented in /reference/routes.

Tile​

Each tile has:

  • A type that selects behavior (for example events, stops, tours, quizzes—see /reference/tile-types).
  • A size (small, medium, large, or embedded for inline modules). Size affects layout on the landing grid and whether navigation opens a fuller screen experience where relevant.
  • Optional links to backing content such as a quiz, chatroom, voting view, site plan, or gallery—depending on tile type.

Tiles can behave as:

  • Click-through cards that navigate to dedicated experiences (quiz, site plan, explore-style lists, external URLs, and similar).
  • Embedded surfaces that render inside the landing grid (embedded events, chat snippets, FAQs, newsletters, polls, and more).

Tile interactions can record engagement for analytics where that tile type supports it.

Nested landing (landingPage tile type)​

Tiles of type landing page can navigate to another published landing page inside the same guest experience. That supports multi-section navigation and sub-experiences without rebuilding the outer shell.

Single-tile embed​

Teams can share a standalone tile URL so only one module appears fullscreen. This is useful when an external site should embed a single capability (poll, newsletter signup, gallery, and similar) without the full landing grid.

Relationships to other product areas​

Tiles also connect to day plans, experiences and guest planning and My Visit. Music wishes collects requests and votes, while image and video display media directly.

Module access applies to the owning feature as well as role permissions. Not every active runtime tile is offered to every editor; the day-plan tile currently has staff-only authoring. Check each tile's guide for availability.

AreaRelation
ToursTour tiles bridge into the tour experience from the landing grid.
EventsEvent tiles surface calendars or pinned events and tie into explore-style discovery where configured.
Places / stopsStop tiles surface recommendations (“places”), often paired with site plans or tours.
Offers, contact forms, site plansDedicated tile types link into offer flows, contact submissions, or site plans.
CRM / newslettersNewsletter tiles surface subscription flows tied to CRM and mailing lists.
PermissionsDashboard authoring is organization-scoped; see /reference/permissions.

Related concepts: Browser-first guest app, Multilingual content, Dashboard landing pages.