A toggle is a feature that allows a user to switch between two different options or states. Toggles are often used in everyday technology such as keyboards (Caps Lock & Num Lock) and software applications, but they are also frequently found on websites and digital products to help users update their preferences or settings. Toggles are commonly deployed in the form of a button that appears to be an “on” or “off” indicator. In practice, when a button is clicked it flips the toggle to its other state and then when the button is clicked again it switches back to its original state.
The visibility toggle is a great way to hide content from certain visitors, but it is important to be aware of the limits and risks of this feature. For example, hiding content via the visibility toggle could break articles that contain dynamic content, such as a Spoiler or a mention link to another article. Additionally, this toggle may not work properly on mobile devices.
Visibility toggles can be found on most content types, including article sections created by template specific prompt fields, containers, images, maps, key/value items, prompt linked articles, quotes, and aloud boxes. However, there are some exceptions to this rule. Article titles, subheadings, credits and the article vignette cannot be hidden using this toggle. The reason for this is that these components are essential for the understanding of the article and should always be visible to viewers.
Toggle switches are a great way to allow users to update their preferences and settings. However, if they are not deployed correctly, they can be a frustrating user experience. Toggle switches should be clearly labeled, use standard visual design, and deliver immediate results. The toggle should also be placed where it is easy to find and in a position that does not disrupt the flow of the user’s journey through the site or app.
When it comes to implementing and managing toggles, there are a number of approaches that teams can use. These range from simple but less dynamic methods such as a commenting pattern or the use of a preprocessor’s #ifdef feature to more sophisticated but complex systems that act upon a variety of conditions.
Savvy teams treat their inventory of Feature Toggles as something that has a carrying cost and strive to keep it low. They also make sure to have a process in place for proactively removing toggles as they are no longer needed. This can be as simple as adding a code cleanup task to the team’s backlog or as complex as creating a time bomb that will fail an automated test if a toggle has not been removed by a set date.
Toggles can be a valuable tool for managing the impact of new features on your website or app. However, they should be used sparingly and only when the user needs to change their preferences or settings. To avoid frustration for the user and to reduce the burden on your support teams, ensure that toggles are deployed with clear and effective instructions and are accompanied by clear and meaningful feedback.
