Project Inventory: HackforLA Website

[Olivia-Chiong]

Overview

We need to make an inventory for this project so we understand what assistance this project needs and what examples of effective processes or practices this team might have.

Action Items

• [ ] Check the project for the items on the check list below
• [ ] Mark off the items when you find it and include the links where available
• [ ] Provide comments on what you find in the issue and also highlight when they have a great example so we can use it for the organization

Project Inventory

• [x] Readme
• [x] Wiki
• [ ] [Google Drive]()
• [x] GitHub Repository
  • [x] Project Board
  • [x] Issue Templates
• [x] Slack Channel
• [ ] 1Password
• [ ] Project Email
  • [ ] projectname@hackforla.org
  • [ ] projectname@gmail.com (You will need this for setting up some applications like MIro that use rate limiting. Do not send emails using this address)
• [x] Figma
• [ ] [Miro]()
• [ ] [Team Roster]()
• [x] Product One Sheet
• [ ] [Competitive Analysis]()
• [ ] [Presentation Deck]()
• [ ] [Recruitment Form]()
• [x] User Persona/Journeys
• [ ] [OKRs and WBS]()
• [ ] [Storypoints]()
• [ ] [Meeting Minutes Template]()
• [ ] [Communication Style Guide (including documents, spreadsheets and forms)]()
• [ ] [User Research Guide/Template]()
• [ ] [Wireframes Template]()

Resources/Instructions

REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

[ExperimentsInHonesty]

@pkfynn is this complete?

[pkfynn]

@ExperimentsInHonesty I requested information from the hfla website team on 1/31/21 and I still haven't received any responses on it.

https://hackforla.slack.com/archives/C4UM52W93/p1612105029053200

[ExperimentsInHonesty]

Hi @pkfynn Sadly the slack does not go back that far and I just missed checking what happened. But the project page is updated, so you can reach out to the PMs directly in the channel by at messaging them in the public message https://www.hackforla.org/projects/website

[ExperimentsInHonesty]

@pkfynn Also, some of this info can be found on the wiki. For instance, I went to https://github.com/hackforla/website/wiki/ clicked on Joining the team and there was a the roster.

This task is not a "get it done as fast as possible" this task is a journey for you to explore the project and if this stuff is visible in their wiki or readme, or on their project board get exposure to where they put it, etc. This way you learn how projects communicate, and if you find some way that makes sense to you, you can replicate it on your own project. If it makes no sense to you, then you do it differently on your project and see if that is better.

Don't get me wrong though, I also want you to get it done because we need the data. It's just that is only part of the goal here.