# Govrn Contributor Stack

###### tags: onboarding, HR, ops

*This is the stack of what Govrn provides to our core contributors.*


### tl;dr

There tends to be an overkill when it comes too what tools to use. Our goal at Govrn is to:
1. Keep the number of tools to the lowest amount possible
2. Choose tools that enable modularity and easy export of your work (for ownership)
3. Increase collaboration by creating shared spaces

This is meant to be iterative, and will change as the team grows in size.

## The Govrn Tool Stack

Here is the Govrn tool stack and their associated purpose.

*Note: If a tool is never serving it's intended purpose, we should eliminate or replate the tool. Similarly, if we ever want to add a tool, we should check it against this list if it serves a duplicate purpose.*

Govrn Stack:
- **Discord:** Team Communication Platform
- **HackMD:** Team Documentation Tool
- **HackMD/Github:** Workplace for the team to organize artifacts
- **Figma - FigJam:** Team Brainstorming and Whiteboarding platform
- **Figma - Figma Design:** Wireframing and Design Tool
- **Linear:** Team project management tool (if a task doesn't exist in linear, it doesn't exist at all)
- **Github:** Code repository
- **Loom:** Video messages
- **Bird Eats Bug:** Record bugs for repo

Licenses Required for Each Member:
- Linear
- Github
- HackMD
- Figma
- Loom
- Bird Eats Bug

## Use Cases

*Want to do something but not sure where to do it? Here is a guide of some common workflows.*