WordPress gives publishers a flexible foundation for building websites, managing editorial content, and reaching audiences online. But delivering a complete streaming destination requires more than placing a basic video player on a page.
Media teams also need practical ways to organize and publish large video libraries, manage playlists, support live and linear programming, authenticate viewers, deliver entitled content, monetize premium programming, expose structured metadata, and maintain control over the presentation of every viewing experience.
The Zype WordPress Plugin brings these capabilities together by connecting a WordPress website to the Zype Streaming Platform. It gives publishers, administrators, and developers a practical integration layer for managing streaming operations in WordPress while keeping privileged platform credentials and API activity securely on the server.
The result is a more connected workflow for organizations that want WordPress to serve as the front end of an owned-and-operated video destination.
Once the plugin is configured with the appropriate Zype credentials, authorized WordPress administrators can access a broad set of video operations through a dedicated Zype menu.
Instead of moving between disconnected tools for everyday publishing tasks, teams can search videos and playlists, copy shortcodes, upload media, manage Channels, review consumers, work with metadata objects, configure product experiences, manage cloud encoders, and oversee live or linear events from the familiar WordPress dashboard.
The plugin uses Zype APIs to retrieve content when it is needed. Videos, consumers, playlists, and ZObject records remain managed in Zype rather than being unnecessarily duplicated as WordPress content records. WordPress stores the plugin-owned configuration needed to shape the website experience, including route settings, Channel definitions, View Template metadata, interface preferences, and related integration settings.
This separation helps publishers maintain Zype as the source of truth for their streaming catalog and audience data while using WordPress to control presentation, navigation, and editorial workflow.
Publish Complete Video Experiences With Shortcodes
Shortcodes make it easier for editors to place Zype-powered experiences into WordPress pages and posts without building a custom integration for every content type.
The current shortcode system supports experiences such as:
A video can be inserted with:
[zype_video id="VIDEO_ID"]
A playlist can be placed in a page with:
[zype_playlist id="PLAYLIST_ID"]
A horizontal carousel can be created with:
[zype_carousel id="PLAYLIST_ID"]
Editors can choose how playlist, grid, and carousel selections open. The default inline mode reveals a player-and-metadata panel beneath the selected row while keeping the surrounding collection visible:
[zype_playlist id="PLAYLIST_ID" view="inline"]
Using view="details" sends the viewer to a dedicated video-detail destination instead.
This gives editorial teams a straightforward publishing workflow while allowing developers to retain control over routing, rendering, templates, player behavior, and front-end assets.
Create Responsive Landscape and Vertical Video Layouts
The standard video shortcode can support both traditional landscape, responsive view and opt-in vertical presentation.
Landscape is default:
A vertical experience can be enabled with:
[zype_video id="VIDEO_ID" vertical="true"]
When the attribute is omitted, the regular landscape presentation remains unchanged. Vertical rendering is scoped to the shortcode instance and uses a responsive 9:16 player area rather than applying global layout changes to the site.
This is useful for short-form programming, mobile-first editorial experiences, social-style video destinations, and catalogs that combine multiple video formats.
Vertical video can also participate in the plugin’s broader rendering and Product Placement architecture rather than requiring a separate shortcode or isolated player implementation.
Centralize Viewer Journeys With System Routes
A streaming destination often includes more than video pages. It may also need login, logout, profile, device-linking, subscription, checkout, password-management, rental, pass, and purchase destinations.
The plugin now manages these consumer-facing destinations through a centralized system-route architecture.
Instead of allowing forms, menus, templates, redirects, and transactional emails to construct URLs independently, the plugin uses a canonical route registry and URL resolver. Administrators can configure public paths under the Routes settings area, while the plugin remains responsible for determining whether each destination is enabled, publicly available, authenticated, anonymous, or dependent on another feature.
This architecture supports routes such as:
Disabled routes are not registered publicly, and URL helpers return no destination when a route is unavailable. This helps prevent broken links, empty form actions, placeholder URLs, and navigation entries that lead to disabled services.
Child routes inherit the availability of their parent. Checkout, for example, remains connected to the Subscribe route rather than operating as an unrelated destination.
The routing system also supports a public, read-only API for compatible WordPress themes. A theme can store a durable system-route identifier and resolve the current URL at render time instead of saving a hardcoded path. If an administrator later changes /profile/ to /my-account/, compatible navigation can continue pointing to the correct destination without rebuilding the menu manually.
The public API intentionally exposes only safe, navigable route information. Internal handlers, submit endpoints, tokenized password-reset URLs, template IDs, raw path fragments, and secrets remain private.
Publish Friendly Video Details URLs
The plugin also supports Dynamic Video Details routes for publishers that want dedicated public destinations based on a video’s Zype friendly_title.
Administrators can configure one or more base paths, such as:
videos
watch
library/video
A video with the friendly_title value featured-documentary could then resolve to:
https://example.com/videos/featured-documentary/
No physical WordPress page or post is created for each video. The plugin resolves the final path segment against the Zype catalog and creates a request-scoped virtual page when exactly one active video matches.
Each configured base route can use the native Video Details renderer or a compatible enabled user View Template. An empty template assignment intentionally means native rendering; it is not treated as a missing configuration.
Ambiguous, missing, invalid, or failed video lookups return the WordPress theme’s normal 404 experience rather than displaying an empty player or partial page.
Different publishers have different presentation requirements. A documentary destination may emphasize long descriptions, credits, and related metadata. A mobile entertainment brand may favor compact interfaces, vertical players, and fast content discovery. A commerce-oriented experience may need product information alongside playback.
The plugin’s enhanced View Template system gives authorized administrators and developers a structured way to customize those experiences without making the public site dependent on a custom file.
The central principle is native-first rendering:
Shortcode or system route
→ determine the rendering context
→ resolve an explicit compatible user template
→ otherwise use the native PHP renderer
→ return to native output if custom rendering fails
Registered service templates act as trusted starting points that can be copied into a custom template and edited. They are not silently executed as public defaults. User-created templates have their own durable metadata, type, context, enabled state, identity, and file mapping.
Template contexts help prevent a layout intended for one experience from being applied incorrectly to another. Current contexts cover experiences such as:
Template selection can occur through supported global defaults, route assignments, page assignments, or shortcode attributes, depending on the rendering context.
When a selected template is missing, disabled, incompatible, invalid, or fails while rendering, partial output is discarded and the plugin falls back to the native presentation. Administrators may receive a sanitized diagnostic explaining why the fallback occurred, while public viewers do not see internal identifiers, stack traces, credentials, or filesystem paths.
Direct file browsing and the older Native View registry model are no longer part of the current template-management experience.
The View Template system also supports an HTML and macro layer for approved rendering contexts.
Rather than requiring template authors to work directly with inconsistent API response structures, the plugin can provide normalized, display-safe data through macros.
Depending on the context, templates can use values such as:
{product.title}
{zobject.title}
{teams.title}
{@url:teams.website_url}
The macro system supports conditional sections, collection iteration, escaped text, safe URLs, selected attributes, and narrowly scoped trusted components.
For example, a ZObject collection template can iterate over records using a qualified namespace: