# Project Frameworks/Guidelines/Checklists/etc
**URL:** https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43
**Category:** Projects
**Tags:** best-of-discourse
**Created:** [May 24, 2018, 11:07pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43 "2018-05-24T23:07:51Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@ninakin](https://discourse.codeforamerica.org/u/ninakin)
#### Post date: [May 24, 2018, 11:07pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/1 "2018-05-24T23:07:51Z")
For project canvass resources, check out this Discourse post: [Creating the Next Generation of Brigade Project Guidance [Brigade Congress 2019]](https://discourse.codeforamerica.org/t/creating-the-next-generation-of-brigade-project-guidance-brigade-congress-2019/623).
Based on recent Slack discussion, I put together a list of project management resources from brigade around the Network:
- Code for Atlanta
- [Connector](https://github.com/codeforatlanta/connector) - Projects management tool
- Open Austin
- [Civic Tech Canvas](https://www.open-austin.org/civic-tech-canvas/)
- [Project Idea Github Issue Template](https://github.com/open-austin/project-ideas/blob/master/ISSUE_TEMPLATE.md)
- Code for Baltimore
- [civicideahub](https://github.com/CodeForBaltimore/civicideahubV2)
- Code for Boston
- [New Project Requirements](http://www.codeforboston.org/projects/)
- Code for BTV
- [Partnership Packet](https://drive.google.com/drive/folders/1Xyp_85NOPMdUKOO52Mbikz5p5KjzjvCC)
- Code for Charlotte
- [Project Starting Process](http://codeforcharlotte.org/start/)
- [Project Criteria](http://codeforcharlotte.org/criteria/)
- [Project Canvas (based on Open Austin’s), has a few variations used for data exploration and community asset mapping](https://drive.google.com/file/d/0B_1lAkQK3oVDLWU0OXVoVUVidnc/view)
- [Project Process Doc, for sharing with new partners (they also have a couple versions of the canvas for different things and have large printed versions at Hack Nights)](https://docs.google.com/document/d/1xcCrAu7t1TqcoQ8OPDFfnaxJV5y-rAwnt9YPdjTuztI/edit)
- [Skilled Volunteer Engagement Agreement (note that they take on paid work as a non-profit)](https://docs.google.com/document/d/1_R27KRHgokJG_scCo-U6uu9kISxqLwQIOhKKKUYW8SE/edit)
- Open Cleveland
- [Project Ground Rules](https://docs.google.com/document/d/13oSUlmVNbhYNYXCnoRbJGdOp9pGnEcoeMPLvsGesKM8/edit)
- Code for Denver
- [Members Project](https://github.com/codefordenver/members) - Members portal ([Waffle board](https://waffle.io/codefordenver/members))
- [Project Champion Check-In](https://drive.google.com/file/d/1pB9rnhwiIXG5-gEY4lF6RhqCiGwVu_sV/view)
- Code for DC
- [How to Start a Project](https://codefordc.org/resources/startaproject.html)
- [Jekyll Website w/ Projects Directory](https://github.com/codefordc/codefordc.github.com) - driven by civic.json
- [Leah Bannon’s (formerly Code for DC) New Project Sketch](https://github.com/leahbannon/old-leah-website/blob/master/_posts/starting-new-project-sketch.md)
- Code for Kansas City
- [Project Process Checklist](https://docs.google.com/document/d/1mXrB8U-9mWimYV-mEaNji3PNY2ilGf2HPNUAaG5hqpU/edit)
- Hack for LA
- [Project Framework in progress](https://github.com/hackforla/governance/issues/2)
- Code for Maine
- [beehve](https://github.com/Code4Maine/beehve) - Members/projects portal (retired)
- Code for Nashville
- [Project Guidelines](https://github.com/code-for-nashville/handbook/blob/master/README.md#projects)
- OpenOakland
- [How to be an OpenOakland Project](http://www.openoakland.org/how-to-be-an-openoakland-project/)
- Code for Philly
- [Civic Hacker’s Starter Guide](https://github.com/CodeForPhilly/gettingstarted)
- [laddr](https://github.com/CodeForPhilly/laddr) - Brigade projects/member portal with multi-site hosting
- Code for Poland
- [Project Finder](https://codeforpoland.org/projects/) - A project finder with project roles and technologies taxonomies
- Code for San Francisco
- [New Member to Project Matchmaker (created by the UX Research Group)](https://github.com/designforsf/brigade-matchmaker)
- [New Member Engagement Project](https://github.com/sfbrigade/research-group/blob/master/projects/NewMemberEngagement/README.md)
- [BrigadeHub](https://github.com/brigadehub/brigadehub) - Members/projects potral (retired)
---
### Author:  [@tdooner](https://discourse.codeforamerica.org/u/tdooner)
#### Post date: [May 24, 2018, 11:47pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/2 "2018-05-24T23:47:36Z")
Here’s **OpenOakland** ’s [How to be an OpenOakland Project](http://www.openoakland.org/how-to-be-an-openoakland-project/) page.
We don’t have as clear a process as many other Brigades, so we’ll be looking to adopt some thinking on this soon!
---
### Author:  [@ninakin](https://discourse.codeforamerica.org/u/ninakin)
#### Post date: [May 24, 2018, 11:53pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/3 "2018-05-24T23:53:50Z")
Added OpenOakland 👍🏽
---
### Author:  [@chris](https://discourse.codeforamerica.org/u/chris)
#### Post date: [May 25, 2018, 12:16am UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/4 "2018-05-25T00:16:17Z")
I alphabetized the list before adding Code for Philly so that I might resist the urge to add us to the top 😃
---
### Author:  [@chris](https://discourse.codeforamerica.org/u/chris)
#### Post date: [July 11, 2018, 6:06pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/5 "2018-07-11T18:06:30Z")
In a similar vein to [`civic.json`](https://github.com/BetaNYC/civic.json), there’s [`publiccode.yml`](https://github.com/italia/publiccode.yml)
---
### Author:  [@eemshi](https://discourse.codeforamerica.org/u/eemshi)
#### Post date: [July 13, 2018, 9:26pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/6 "2018-07-13T21:26:12Z")
Hi there, Code for Denver’s Members Project is in its super early stages, so this would probably give a better idea of our guidelines/checklists: [waffle.io/codefordenver/projects](http://waffle.io/codefordenver/projects)
The first card in each column has info about each stage of the project life cycle as well as requirements.
---
### Author:  [@chris](https://discourse.codeforamerica.org/u/chris)
#### Post date: [May 17, 2019, 3:31pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/7 "2019-05-17T15:31:41Z")
@miklb pointed out this great readme template: [https://gist.github.com/miklb/1737a9c897660261bbc7674e187b0c83](https://gist.github.com/miklb/1737a9c897660261bbc7674e187b0c83)
---
### Author:  [@chris](https://discourse.codeforamerica.org/u/chris)
#### Post date: [June 7, 2019, 2:22pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/8 "2019-06-07T14:22:15Z")
Here’s a handy collection of project documentation templates:
> **[kylelobo/The-Documentation-Compendium](https://github.com/kylelobo/The-Documentation-Compendium/)**
>
> 📢 Various templates & tips on writing high-quality documentation that people want to read. - kylelobo/The-Documentation-Compendium
---
### Author:  [@chris](https://discourse.codeforamerica.org/u/chris)
#### Post date: [September 24, 2019, 4:25pm UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/9 "2019-09-24T16:25:02Z")
I’m not sure how long this has been a thing, but GitHub published and supports a bunch of “community health” standards exactly like we were talking about:
[https://help.github.com/en/articles/creating-a-default-community-health-file-for-your-organization](https://help.github.com/en/articles/creating-a-default-community-health-file-for-your-organization)
So this makes figuring out how to standardize super easy…
For non-code projects, we could just publish repos on behalf of teams as at the least a means of documenting/publishing community health files
---
### Author:  [@Mari](https://discourse.codeforamerica.org/u/Mari)
#### Post date: [July 1, 2023, 7:04am UTC](https://discourse.codeforamerica.org/t/project-frameworks-guidelines-checklists-etc/43/11 "2023-07-01T07:04:39Z")