Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs for using feature flags in govuk-frontend #46

Merged
merged 1 commit into from
Jan 4, 2024
Merged

Conversation

owenatgov
Copy link
Contributor

@owenatgov owenatgov commented Dec 5, 2023

What it says on the tin. Fixes #47

Copy link

netlify bot commented Dec 5, 2023

Deploy Preview for govuk-design-system-team-docs ready!

Name Link
🔨 Latest commit df1d2d0
🔍 Latest deploy log https://app.netlify.com/sites/govuk-design-system-team-docs/deploys/6596cd6fd78e4a0008b99faa
😎 Deploy Preview https://deploy-preview-46--govuk-design-system-team-docs.netlify.app/development/feature-flags
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

### The thing is a breaking change
Feature flags should only be used for things considered breaking changes. This is something where users will potentially need to change their service, or assess if their service needs changing, in order to continue staying up to date with govuk-frontend. In this case, a feature flag would be a way for a user to stay up to date whilst also opting out of the feature for a period of time. We don’t need to do this for minor releases or new features such as a new component because a user can opt out by simply not using the new feature.

### The thing might be a long term project for users
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a fan of using 'the thing' in the subheads, but can't think if a different option at present

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"The feature"? "The change"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'feature' risks getting confused with specific 'new features'. 'change' might work. Or perhaps 'action'?
or I'm probably overthinking it and it doesn't really matter.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall I give action a go?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's give it whirl and see what others think

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried replacing everything with action and it didn't feel right in a few places so I've used a mix of "action" and "change" depending on the context. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like a good plan

@owenatgov owenatgov force-pushed the feature-flags branch 2 times, most recently from e52c145 to 744547f Compare January 2, 2024 17:01
@owenatgov owenatgov force-pushed the feature-flags branch 3 times, most recently from 7a8f3aa to 7bacd40 Compare January 2, 2024 17:16
@owenatgov owenatgov force-pushed the feature-flags branch 4 times, most recently from d0f4ef2 to 85e9ef6 Compare January 4, 2024 15:11
Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Update source/development/feature-flags.html.md

Co-Authored-By: CAAshworth <[email protected]>
@owenatgov owenatgov merged commit 809ad67 into main Jan 4, 2024
4 checks passed
@owenatgov owenatgov deleted the feature-flags branch January 4, 2024 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create internal documentation on how to use feature flags
2 participants