A toggle is a pin that’s passed through the eye of a chain, loop or other fastener to bind it temporarily. In computers and other devices, toggles allow users to switch between two functions. For example, the key that turns on your Caps Lock and Num Lock is a toggle. When you press it once, the function is turned on and when you press it again it’s switched off.

A Feature Toggle is the term used to describe a configuration option in software that controls the availability of a feature. Unlike the dynamic nature of Product Toggles, Feature Toggles are intended to be static. The toggling decision for a Feature Toggle will be baked into a specific release version and changing it requires rolling out a new version with a different toggle configuration.

Savvy teams view the Feature Toggle inventory in their codebase as inventory that comes with a carrying cost and seek to keep it low. To that end, some teams have rules in place for adding a task to remove a Feature Toggle to the backlog as soon as it’s introduced and still others set “expiration dates” on their Feature Toggles that will trigger a test failure (or even refuse to run the application) if that feature flag isn’t removed by its scheduled date.

The Content Toggle element allows you to create collapsible and expandable sections of text within an article. It works by transforming standard ordered (ol>) and unordered (ul>) lists created in the article editor into toggles. As with all Article elements the Content Toggle element also has a set of advanced options to enable you to control its positioning, Responsiveness, Animation & Delay.