Video on Your WordPress Site, Served From Your Library
WordPress runs the public site, the campus site and a good share of departmental sites nobody in IT set up. Video on those sites has usually meant an upload into the media library, with no access rule and no idea who watched. With Nexus connected, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, pages and posts carry players and library views while the recordings stay in one library with their own access rules, retention and analytics. WordPress keeps the site.
How it connects
The connection is the JavaScript widget, as the catalog names it. An editor pastes a widget or an embed code into a page or a post: a video, audio, image or document player, a playlist or collection player, a library gallery or detail view, search, or a quiz or survey player. The page renders in WordPress; the media streams from Nexus. There is no plugin to install. The widget and the embed code are the whole connection.
Configuration lives in Nexus. Embedding is restricted to approved domains, so the widgets render on the sites you list and are refused elsewhere, and embedded URLs are signed and expire. Each embed resolves against the viewer's identity, so a recording restricted in Nexus stays restricted on a public page.
Nothing is uploaded into the WordPress media library, and WordPress users, themes and plugins stay as they are.
What you can do together
- Post a lecture, a campus announcement or a public information video in the time it takes to paste an embed, with the file staying in Nexus.
- Give a department a browsable library on its own site, through the Nexus gallery and search widgets.
- Serve public video and restricted video from one Nexus library, with the rule set there deciding who sees what on the page.
- Add a quiz or a survey beside the player, through the Nexus quiz and survey player widgets.
- See which site drew the views, through Nexus embed analytics reporting view counts and last playback per site.
A scenario
- MondayThe program coordinator uploads a public open-day recording and a course preview limited to enrolled students to Nexus, each with a retention rule.
- Monday afternoonThe web editor pastes the player widget into the open-day post and into the course page. The site's domain is on the approved list, so both render.
- TuesdayA prospective student reads the post and watches the open-day recording inside it. The same person opens the course page and sees the description but not the preview, because the embed resolves against the viewer.
- Tuesday, laterAn enrolled student opens the course page and the preview plays, followed by a short survey placed with the survey widget.
- Following monthThe coordinator opens embed analytics in Nexus and sees the open-day post's view count and last playback, and how the course pages compare, per site.
What stays where
WordPress keeps the site
Pages, posts, themes, plugins and users stay in WordPress. The media library is not used for video.
Nexus keeps the video
Recordings, access rules, retention and analytics live in the library, and pages read from it through a widget.
Nothing is replaced
There is no plugin to install. The standard JavaScript widgets and embed codes are the whole connection.
Processing runs where you choose
Nexus is offered as shared SaaS, a dedicated instance, in your own cloud or on your own servers.
Products and solutions
Next step
See it on your own WordPress instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/wordpress