Frequently Asked Questions

Yes. Tick Enable www when you configure the domain and add the record for the www address as well. Verification then checks both addresses.

Yes, with one rule. A CNAME record works with Cloudflare. An A record must be set to DNS only (grey cloud); an A record behind the Cloudflare proxy (orange cloud) fails verification, so switch to a CNAME if you need the proxy.

It keeps working alongside your custom domain. If you later want a different domain, use Change Domain on the same screen; your current domain keeps serving viewers until the new one is verified.

No. Vodlix recommends first checking whether a requirement is a platform setting or an existing integration, since both cost far less than custom code and are often already available.

Custom code must be maintained forever, survive every platform upgrade and be understood by whoever inherits it, whereas a Vodlix setting costs nothing after it is switched on.

Yes. Vodlix builds custom and tailor made features when a requirement is genuinely bespoke. The approach is simply to reach for custom work last, once configuration and integration are ruled out.

A feature delivered as configuration is the cheapest, because it is already built, tested and maintained by Vodlix and costs nothing after it is enabled.

Keep the custom surface small. The less bespoke logic your platform carries, the less there is to break when the underlying platform is upgraded, and the cheaper it is to run.

Ask whether it describes how something needs to work or how it used to work in a system you are replacing. A surprising share of bespoke requests are habits carried over rather than genuine constraints, and that is worth twenty minutes before it is worth a proposal.

That is the question worth settling before anything is built, along with what happens to it when the platform upgrades. It is the difference between custom work that pays for itself and custom work somebody later regrets.

With the configuration you already have. Branding, pricing, languages, territories, quality and screen limits are all settings, and a meaningful number of requirements that arrive described as development turn out to be one of those that nobody had found yet.

Yes. Vodlix lets you preview and customise a new template separately from your live site, which stays untouched until you choose to activate the new one.

Yes. Vodlix custom templates are reversible. If a new look does not perform, you can switch back to the previous template within minutes, so redesign carries no lasting risk.

No. The template your viewers currently see stays exactly in place while you work on an alternative in preview. Nothing changes for viewers until you activate the new template.

Yes. Vodlix lets you adjust colours, layouts and content placement fully in preview, see the template exactly as viewers would, and only then decide whether to activate it.

Reversibility removes the risk that makes redesigns get deferred for years. With Vodlix custom templates, refreshing the look becomes an ordinary decision rather than a quarterly project.

A template is the structure and layout. Themes and colours are the brand values applied within it. You would change a template rarely and colours whenever your branding moves, which is why they are separate screens.

Templates govern the web front end, while the apps have their own presentation with the branding shared between them. What travels across all of them is the brand layer rather than the layout, since a television and a browser cannot use the same structure anyway.

Rarely, but the point is that you can. Services that find changing painful never change, which is how a front end quietly ages for three years and then needs an expensive rebuild all at once.

No. Vodlix custom themes are built with a visual editor that lets you adjust colours, typography, imagery and layout on a responsive template without writing any code.