Files
pulse-signage/docs/user
lzstealth 0a03cdd0b7
Publish Docker Image / build-and-push-existing-registry (./build/Dockerfile, web, pulse-signage-web) (push) Successful in 2m6s
Publish Docker Image / build-and-push-existing-registry (./build/Dockerfile.player, player, pulse-signage-player) (push) Successful in 33s
Release v2.12.0
2026-09-11 17:22:31 +01:00
..
2026-09-11 17:22:31 +01:00
2026-09-11 17:22:31 +01:00
2026-09-11 17:22:31 +01:00
2026-09-11 17:22:31 +01:00
2026-09-11 17:22:31 +01:00
2026-09-11 17:22:31 +01:00
2026-09-11 17:22:31 +01:00

User Guides

These guides explain how to use Pulse Signage to create content, publish it to screens, monitor players, and operate displays.

How Pulse Signage Fits Together

The main content objects have a simple relationship:

  • A template defines the structure and appearance of a slide.
  • A slide is a piece of finished content built from that structure.
  • A playlist arranges slides into a sequence.
  • A screen is the display destination for a playlist.
  • A player runs the screen and reports its connected clients.

You can reuse a template across many slides, reuse a slide across many playlists, and change a playlist without rebuilding the slides inside it. This separation lets you update one part of a signage setup without recreating everything around it.

Typical Publishing Workflow

For a new piece of signage, work through the application in this order:

  1. Decide the screen size or aspect ratio and create a matching canvas size if one does not already exist.
  2. Choose an existing slide template, or create one when the design needs a new structure.
  3. Build a slide, add its content, and preview it at the intended size.
  4. Add the slide to a playlist and place it in the correct order.
  5. Assign the playlist to a screen.
  6. Check connected clients to confirm the player is online and displaying the expected content.
  7. Use an announcement or data source when the information needs to change independently of the playlist.

The web application is the main place where content and screen assignments are managed. Once a change is saved, the relevant players receive the updated state.

For deployment and service setup, see the Compose guide.