The menu is the most valuable strip of space on your platform and usually the hardest to edit. Vodlix makes it a list you arrange yourself, with header, footer and page navigation all built the same way.
On most platforms the navigation is the last thing anybody can change. It gets set during the build, and after that adding a link means a ticket, a release and a fortnight. That is a poor arrangement for something a viewer sees on every single screen, and it quietly stops teams from doing obvious things like promoting a new section during a campaign. Vodlix treats navigation as content. Menus are lists you build and reorder yourself, and a change is live when you save it.
Three menus, built the same way. Each carries its own items in its own order, so the footer is not an afterthought bolted onto the header.
An item can be an internal destination, an external URL, or a content list group, which means a curated row becomes a top level menu entry without a page being built for it.
Items carry the platforms they appear on, so a link that makes sense on the web can be left out of the television where a remote makes long menus painful.
Four things decide whether navigation stays useful as a platform grows, and all four are per item.
Order. Rows are dragged into sequence, so the thing you are promoting this month sits where the eye lands rather than at the end.
Type. Internal destinations, external links and content list groups all coexist, which is what lets a curated collection become a menu entry in its own right rather than something buried two clicks down.
Platform. Each item declares where it belongs. A support link that earns its place in the web footer does not have to clutter a television.
Status and audience. Items can be switched off without being deleted, and carry an authorisation setting, so a section can be prepared ahead of a launch or shown only to the people it applies to.
Navigation is where merchandising meets structure. A row you built in content lists can be promoted to the top level menu the week it matters and demoted afterwards, without a page existing for it. A seasonal section can appear in November and disappear in January with its configuration intact.
Because the same menus drive the web storefront and the apps, that decision reaches every screen at once, and because it is a configuration change rather than a deployment, the person who owns the programming can make it. That is usually the difference between a menu that reflects the business and one that reflects whatever was true on launch day.
Have questions about taking advantage of this limited-time offer? Check out the FAQ for answers.