Since the front end requires data from the back end to implement new features, there is sometimes a necissary lag where the front end may work with stubbed or fake data from the server to implement new features. Given the timelines of the project, we should be able to deploy and test out these features but we probably don't want them on the site that user actually access.
To that end, we should have a system where we can activate a 'beta' version of the site.
Acceptance Criteria:
- We should have a way to activate the 'beta' site. Some websites use a Konami Code to activate easter eggs, for example:
- We should set up a 'feature flag' framework so that our 'beta' site can be the only version of the site to show certain features
- Add the first toggled feature, which would be some visual indication that you are in 'beta' mode - such as a 'beta' header which tells you how to get back to non-beta mode
- Update the readme with directions to future developers on how to use the feature toggling that was set up.
For more research, background, and resources, read this gist.
Since the front end requires data from the back end to implement new features, there is sometimes a necissary lag where the front end may work with stubbed or fake data from the server to implement new features. Given the timelines of the project, we should be able to deploy and test out these features but we probably don't want them on the site that user actually access.
To that end, we should have a system where we can activate a 'beta' version of the site.
Acceptance Criteria:
For more research, background, and resources, read this gist.