The Civic Tech Structure project seeks to improve existing structures and create new ones that make it easier to share replicable processes and practices so that the civic tech community can iterate on each other’s work, improving outcomes for the whole ecosystem.
| External Projects | With Partners |
|---|---|
 |
Civic Tech Structure’s first external project is to help extend Code for America’s Brigade Organizer’s Playbook (BOP), building on the existing product and improving its value as a communal, high-value resource for sharing best practices in topic areas such as fundraising, recruiting members, running remote brigades, project management, setting and achieving DEI goals, etc. Critical to the project’s success will be canvassing the BOP end-user - the Brigade Organizers - to understand their pains, wants, and needs, and identifying effective processes and practices (including the state of shareability they are in). This process will be made possible by an intensive UX Research phase with the BOP end users via exploratory, structured interviews. Each of the 80+ Code for America Brigades is an experiment which generates valuable learnings and new effective processes and practices. Read about the BOP Extension Project |
| Internal Projects | Implementation across all Hack for LA projects | In Use? | Status |
|---|---|---|---|
 |
To secure the passwords and make it easy to add/remove people from projects | in use | needs guide |
| Project One Sheets | To create alignment on project between the org and volunteers, while providing outside stakeholders a overview of projects. | in use | needs guide |
| Resume Content Building Tool | To help volunteers to turn their experience into bullet items on their resume | in use | ✅ includes instruction |
| WIKI template | Draft WIKI with to help projects build their onboarding documentation quickly | in use | ready to clone |
| Communication (style) Guide for Document Creation (WIP) | Document Template Creation Guide for setting up a consistent look and feel across all documents (internal and external) for your project | rolling out | needs guide |
| Google Form design (WIP) | Guide to making great headers for your google forms | ideating | needs guidlines |
| User Stories and Personas Templates (WIP) | Guide to User Stories and Persona creation | in use | needs guide |
| Privacy Policy Template (WIP) | Template for open source software projects | rolling out | needs guide |
| Figma Template (WIP) | Template for figma files on a project | ideating | needs examples |
| Adding a GitHub sponsors button to your repository | Summary of GitHub sponsors with CfA and without | ideating | ✅ includes instruction & waiting for CfA to setup |
| Competitive or Compartive Analysis Template | Template for doing analysis between your project and similar or overlapping efforts | in use | ✅ includes instruction |
| Github: How Hack for LA uses Kanban | Draft Guide in a Google Doc for how to use GitHub project boards to increase team accountablity and effectiveness | in use | ✅ includes instruction |
| Github: Kanban board setup | Slide Deck for setting up Kanban boards on your new project | in use | ✅ includes instruction |
| Miro: Create an account for your project | Instructions for how to setup a Miro board for a Hack for LA project | in use | ✅ includes instruction, needs to be made into a markdown guide |
| SMS (texing) Application - Competitive Analysis and pricing template | Template for SMS messaging campaign plan | in developement | Needs to be built out with more instructions |
| GitHub: How to work on GitHub Issues | Draft guide for working on Issues (Assigning & Unassigning/Changing Status/Reporting Progress/Stopping) | In use | ✅ Ready for peer review |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent