Dev docs: improve documenting features behind flags
Problem to solve
Improve the current guidelines of Feature flags development documentation - (Slack thread
Proposal
- Collapsed version note: (
🅰 ) display the version note while it says "disabled"? WIP: !1005 or (🅱 ) add a note saying it's disabled to an alert box instead? - For enabling features per project: proposal: omit unless it can be enabled per project and mention which GL.com project has the feature enabled.
👍 or👎 ? - Terminology: enabled/disabled vs "turned on"/"turned off". Let's keep the former to match the expression we use internally and to match the code (
enabled
/disabled
).👍 or👎 ? - Change "version history" (
🅰 ) to "feature availability" (🅱 ) ? No strong preferences from my side. WDYT? (gitlab-docs!1005 (closed))
Who can address the issue
Style committee
Other links/references
Edited by Marcia Ramos