Third-party CMS integration enables SpinetiX players to work with any content management platform — not just Elementi and Arya. SpinetiX's open architecture accepts content via WebDAV file publishing, meaning any CMS that can push files to a network endpoint can drive SpinetiX players. This flexibility is important for enterprises with existing CMS investments or multi-vendor signage environments.
Integration Architecture
WebDAV Content Publishing
SpinetiX players expose a WebDAV endpoint. Any system that can PUT files via WebDAV can publish content to the player. Third-party CMS platforms generate HTML5 content files, upload them to the player's WebDAV folder, and the player renders them. Standard HTTP PUT semantics — no proprietary protocol.
HTML5 Content Format
SpinetiX players render HTML5, SVG, CSS, JavaScript, images, and video. Third-party CMS platforms that output standard web content are compatible. The content should be self-contained (all assets bundled) and designed for the target resolution (1920×1080 typical).
Hybrid Workflows
Mix native SpinetiX content (from Elementi) with third-party CMS content on the same player. A multi-zone layout places Elementi-designed header and footer with third-party CMS content in the main zone. This leverages SpinetiX's design capabilities where needed while integrating with existing CMS workflows.
CMS Integration Approaches
| Approach | CMS Responsibility | Player Responsibility | Best For |
|---|---|---|---|
| Full CMS control | Generate + schedule + push | Render only | Enterprise-wide CMS deployment |
| CMS content + local schedule | Generate + push | Schedule + render | Mixed vendor environment |
| Hybrid Elementi + CMS | Push zone content | Layout + schedule + render | Design-rich with CMS data |
| Data feed only | Provide API/JSON | Template + schedule + render | CMS as data source only |
Key Parameters
| Parameter | Value | Why It Matters |
|---|---|---|
| Publishing protocol | WebDAV (HTTP PUT/DELETE) | Universal, no proprietary SDK |
| Content format | HTML5, SVG, CSS, JS, Media | Standard web technologies |
| Max project size | Player storage capacity (GB) | Local cache for offline playback |
| Scheduling | Player-side or CMS-side | Flexible workflow control |
| Authentication | Basic auth on WebDAV | Secure content publishing |
Common Mistakes
- Server-dependent CMS content. Some CMS platforms generate content that requires a live connection to the CMS server for rendering. SpinetiX plays content locally — ensure content is self-contained with all assets bundled, not streaming from a server.
- Ignoring resolution matching. CMS content designed for a 1920×1080 screen deployed to a portrait 1080×1920 display looks wrong. Communicate the exact display resolution and orientation to the CMS publishing pipeline.
- No content validation. A CMS publishing malformed HTML or oversized files can crash the display. Implement content validation before publishing — check file sizes, HTML validity, and required assets.
- Forgetting offline capability. SpinetiX's strength is offline playback. If third-party CMS content makes runtime API calls that fail when offline, the screen breaks. Design content to work with cached data and graceful degradation.