How to Use Toggle in Your Content Management System

Toggle is a versatile feature in our platform that allows you to hide or show content to your viewers. This can include world images, articles, maps, key/value items and prompt linked articles among other things. However, there are some restrictions that prevent some elements from being toggled: The article title, author and credits cannot be toggled, nor can any element that is loaded via a dynamic link (such as the map or article preview).

When using Toggles in your releases it’s important to remember that they’re meant to be transitionary by nature. Toggles should generally not stick around for more than a week or two, although product-centric toggles may need to remain in place longer. With that in mind, it’s good practice to update a toggle configuration with every new release version.

Another use for Toggles is as a circuit breaker in your production application during high latency periods. By enabling or disabling non-essential features for specific users or segments of the user base, you can prevent issues from being exacerbated by too many changes at once.

A final use for Toggles is to validate features with a segment of your user base before launching them broadly. By putting new functionality behind a feature toggle, you can test how it will be received by your audience and reduce the risk that a new feature won’t take off.

Toggles can be managed in several different ways, ranging from simple commenting approaches through to more sophisticated dynamic configuration systems such as Kameleoon. However, the approach you choose should be consistent with how you manage other parts of your continuous development process.