18F/development-guide resource
A set of guidelines and best practices for an awesome software engineering team observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4009
- days_rel: n/a
- days_push: 897
- n_releases_24m: 0
Adoption not part of the score
1469 stars · 166 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A published guide of software engineering best practices and guidelines maintained by the 18F/TTS Engineering Practices Guild, written in Markdown and built as a static site with Jekyll. It serves as a living knowledge base covering team practices, tools, and common patterns for software development teams.
Use cases
- find best practices for running a software engineering team
- learn how a professional engineering guild documents its standards
- reference guidelines for code review and development workflows
- set up engineering conventions for a new team
- study an example of a Jekyll-published internal engineering guide
- onboard new developers with shared team practices
When to choose
- you want actionable, opinionated engineering guidance from an experienced government digital services team
- you need a template or inspiration for your own team's engineering handbook
- you are looking for a curated knowledge base of software development practices
When to avoid
- you need executable tooling or a library rather than written guidance
- you need up-to-date content, since this guide has moved to the consolidated 18F guides repository
- your context differs significantly from US government software delivery
Facets
learning-resource · maturity maintenance
documentation developer-tools developer-tools documentation tutorials cross-platform engineering-practices best-practices jekyll government team-guidelines software-craftsmanship web-server
1 source
- readme: https://github.com/18F/development-guide · fetched 2026-08-28 · 6b5eb361bf15
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| 18F/development-guide | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="18F/development-guide")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem