developer-manual

We use agile tools and techniques to:

• self-organise and plan
• communicate (within the team and with the rest of the organisation)
• continuously improve the way we work

We follow a loose gathering of agile processes:

• standups
• retrospectives
• show and tells

We can change any aspect of these lightweight processes through retrospectives.

Contributing code

We use GitHub to collaborate when writing code. We follow GitHub Flow, while expanding on:

• Branches
• Commits
• Issues
• Pull requests
• Team management
• Repositories

Deploying code

for Donate and Cookie Banner:

• Netlify for static sites
• Heroku for sites with a backend code requirement

Ask a member of the team if you need access to these services.

To keep deployments consistent we follow:

• Heroku setup guide

When we need a unique URL for our project we follow:

• Short URL setup guide

for Website:

• Github, Bitbucket: wiki

Tools and methodologies

Within the digital team we use the following:

• tools
• methodologies
• dependabot setup instructions
• dependabot PR review instructions
• wifi-location-changer setup instructions

Removing access

When someone leaves the team, we remove their access to the tools we use.

If you are not sure how to do any of the things in this manual, please feel free to ask for help. You can change any aspect of this manual through a pull request.