The content pipeline defines how digital signage content moves from initial concept to final display on screen. A well-designed pipeline automates repetitive steps, enforces quality standards, and reduces time-to-screen from days to minutes. SpinetiX enables three pipeline models: manual (designer-driven), semi-automated (template + data), and fully automated (API-driven with zero human touch for routine content).
Pipeline Stages
Stage 1: Content Creation
Content originates from two sources: creative design and business data. Creative content (brand videos, campaign graphics, layouts) is designed in Elementi. Business data (prices, schedules, KPIs) feeds into templates from spreadsheets, APIs, and databases. The best pipelines separate design from data — designers create templates, operations teams manage data.
Stage 2: Review and Approval
For creative content, implement a review step. The designer creates or modifies content, a reviewer previews it (Elementi preview or staging player), and an approver authorizes publication. For data-driven content, the template is approved once — subsequent data updates flow through without per-update review.
Stage 3: Publishing
Approved content is published to target players. With Elementi: click Publish, select targets. With Arya: upload to cloud, assign to groups. With automated pipelines: script triggers WebDAV upload or API call. The publishing step defines where, when, and how content reaches players.
Stage 4: Delivery and Caching
Content transfers from source to player via the delivery architecture (push or pull). Players cache content locally. Delta sync ensures only changed files transfer, minimizing bandwidth and time.
Stage 5: Rendering and Display
The player renders content locally in real time — executing schedules, fetching live data, animating transitions, and compositing multi-zone layouts. The output drives the connected display via HDMI. Data-driven content refreshes at configured intervals without re-publishing.
Pipeline Models
| Model | Automation Level | Human Involvement | Best For |
|---|---|---|---|
| Manual | None | Design → Preview → Publish | Brand campaigns, creative content |
| Semi-Automated | Data feeds auto-update | Template design, occasional review | Menu boards, dashboards |
| Fully Automated | API-driven end-to-end | Initial template only | Exchange rates, transit, queues |
| CI/CD Pipeline | Git + build + deploy | Code review | Developer-managed signage |
Key Parameters
| Parameter | Value | Why It Matters |
|---|---|---|
| Time-to-screen | Seconds (automated) to hours (manual) | Business agility |
| Update frequency | Real-time to weekly | Matches content freshness requirements |
| Quality control | Template-level approval | Brand consistency at scale |
| Rollback | Git versioning, previous publish | Recover from bad updates |
| Monitoring | Delivery confirmation + display status | Verify pipeline completion |
Common Mistakes
- Manual updates for dynamic data. If prices change daily, don't have a designer update the screen manually each morning. Use data-driven templates — update the spreadsheet, screens update automatically.
- No staging or preview. Publishing content directly to production without preview is risky. Use a staging player or Elementi's preview to verify before going live.
- One-size-fits-all pipeline. Brand campaign videos need creative review. Exchange rate updates don't. Design different pipeline paths for different content types — don't force creative review on automated data feeds.
- No rollback capability. When a bad update goes live, you need to restore the previous version quickly. Keep previous project versions (Git, backup copies) and know how to re-publish them instantly.