change log

422 used to have both wiki cleanup and rewrite tasks. I have moved rewrite tasks here.
8/15 i read the wiki audit from last year. it's still not clear to me why the standards are what they are. this also makes sense as to why there were certain pages such as job descriptions present on our wiki. ticking a box does not make the wiki better though - because the job description page was so poorly written i had to remove it. because it was honestly better that it not be there at all. even though it's supposedly "important".

Topics that need to be written about

[x] the purpose of documentation is to tell a story. Not only should we write about how to navigate Github, we also need to address why documentation is important generally, and how this is far from the only time we will have to do it in the tech industry.
- [x] Specifically for Github, we need to write about how to work with its challenges, that it's challenging because it was meant for software engineers. right now the new page is up, but it needs even more info added.
- [ ] and addressing misconceptions about "user stories"
- [x] if our alumni transition to using Jira... why should their time at HfLA teach them inaccurate things, or even bad habits? initiatives, epics, stories, and subtasks are all "issues." a serious overhaul of how we use Github is necessary before putting together any training or workshops - no use training people to use garbage first, before identifying the garbage.
- [x] protocol on milestone creation - milestones are for anything that has an end. milestones can have descriptions, due dates, and can be closed. milestones should be the new epic. issues should avoid too many dependencies to avoid Kanban clutter and cognitive load (epics, stories and subtasks are all the same card? makes no sense.)
- [x] protocol on label creation - should be avoided as much as possible due to distraction in the Kanban view. similar labels should have the same color, and their names should start the same so that alphabetically they are grouped together.
- [x] protocol on Kanban columns - Github can only automate one to-do column per board
[ ] Drive cleanup history. It used to be split by design and research teams, now its structure is based on projects and history, because looking at both teams together is necessary for someone to piece together the full story.
- [ ] how to keep the drive clean in the future, and how to reference drive. reduce folders and clicking. long, descriptive names. ALL CAPS, endash, lower case. issue numbers referenced inside. When sharing, don't link folders, link the file itself, because folders can get moved around. For videos, click "share" and add that link
[ ] job descriptions for designers and researchers. Need for UX/UI role responsibilities was referenced in #136 but "overview" pages have all been merged under the background info page to reduce wiki clutter. The current list of lead responsibilities needs to be drastically shortened. There is a job description in the Drive - how does it compare to the wiki version?
[ ] how to write in markdown - it's more cognitive load for people to write in Markdown if they're not familiar with it. this is also why I decided that template protocol should be copying templates into comments with the main issue having people's account handles - minimizing markdown usage is important for streamlining the Github experience
- [ ] account settings can change font to same-width letters to make markdown writing easier

hackforla / design-systems

Wiki rewrite #406

change log

422 used to have both wiki cleanup and rewrite tasks. I have moved rewrite tasks here.

Topics that need to be written about