Home

Welcome!

This wiki is established to give us a space to put publicly available information related to our front-end work. The reason for a separate area is that information here should be limited to topics that don't necessarily make sense to be anywhere else.

Front-end process flow

The business process model shows the overall workflow, from the creation (or ingestion) of a feature to its approval and acceptance.

View larger image

Git(Hub) repository setup

The front-end Git workflow follows the Gitflow Workflow.

1. Create the repository and establish a master branch (optional) and a develop branch (default and required). Note: These branches can be named something else; however, if different names are used, they should be identified in the CONTRIBUTING.md instructions.
2. Go to "settings" -> "Branches"
3. Mark the develop branch as the default branch for the repository.
4. Add both develop and master branches to the list of "protected branches". Checking the following:
5. Protect this branch
6. Require status checks to pass before merging: Include administrators, and Require branches to be up to date before merging
7. Restrict who can push to this branch: add the usernames of collaborators with "write" access who you would like to be able to merge pull requests
8. If the repository is private, collaborators should be added to allow them to see the repository; collaborators with the ability to merge pull requests should be given "write" access and everyone else should have "read" access.
9. If the repository is public, collaborators are not needed; however, could be helpful.
10. Contributors should create a fork of the repository to begin suggesting changes. For details see CONTRIBUTING.md

Tools

• Wire frames are to be completed using Balsamiq as clickable prototypes.