This step I find critical, because this is where you really have to start thinking about all of the features of your product, from both big to small features. It's useful to think of these ahead of time, so you can take stock of what you need to program in, and from there, how you can structure your code better.

We want to front load all of our design decisions here, before we start programming. We don't want to be making design decisions while programming because it is slower to iterate and test out ideas, and therefore more expensive. Using tools like Sketch make it easy for you to iterate on different design ideas.

My final Sketch document:

Sketch Cloud

https://www.youtube.com/watch?v=WaBj42cOURA

Key features to start off with

1. Allow users to arrange their Github issues (and PRs maybe) in "views"
2. Create issues
3. Edit + manage issues like on Github
4. Create dashboards using these views
5. Connect with Github

Pages

1. 1 Dashboard View

Things to consider doing later

• Match the font of Github
• Match the design on Github
• Match the color scheme on Github
• What issues will be in the "sample" views if we create them?

Another idea is that we shouldn't copy Github's design. I think it'll cause too much clash, with a different app but the same theme as Github.

We should have our own branding and style. But of course we can still copy and be inspired by many of the design elements and layout of Github, which is done very well.

• [x] Create views, edit the name, delete views

should have split this into 2 steps