Think of a way to organize GitHub project boards
- Dominant language
- No language data
- Stars
- 12
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
So what I mean by this is that **organizations, repositories & teams** can have kanban project boards. We can get really disorganized if we don't have a TOC of some sorts. I think this repo would be a good place to keep a TOC document linking to all project boards. For now we rely on sending these links when talking about them over discord. We can easily loose track of which repo to look in for specific boards.
*This would also be a good fit for the branding guidelines I think*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in the GDQuest/meta repository and review its existing guidelines, including the branding-guidelines context mentioned in the issue. Inventory the organization, repository, and team GitHub project boards, then create a TOC document here linking to them. Done means the relevant boards can be located from the document without relying on Discord.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100