ARCHITECTURE.md
If you maintain an open-source project in the range of 10k-200k lines of code, I strongly encourage you to add an ARCHITECTURE document next to README and CONTRIBUTING. Before going into the details of why and how, I want to emphasize that this is not another docs are good, write more docs advice. I am pretty sloppy about documentation, and, e.g., I often use just simplify as a commit message. Nonetheless, I feel strongly about the issue, even to the point of pestering you :-)
If you maintain an open-source project in the range of 10k-200k lines of code, I strongly encourage you to add an ARCHITECTURE document next to README and CONTRIBUTING . Before going into the details of why and how, I want to emphasize that this is not another “docs are good, write more docs” advice. I am pretty sloppy about documentation, and, e.g., I often use just “simplify” as a commit message. Nonetheless, I feel strongly about the issue, even to the point of pestering you :-) I have experience with both contributing to and maintaining open-source projects. One of the lessons I’ve learned
Explore this link on the map →related reading
- Making Softwaremakingsoftware.com
- The Architecture of Open Source Applicationsaosabook.org
- How to Contribute to Open Source | Open Source Guidesopensource.guide
- Using CLAUDE.MD files: Customizing Claude Code for your codebase | Claudeclaude.com
- Using CLAUDE.MD files: Customizing Claude Code for your codebase | Claudeclaude.com
- Cognitive load is what mattersminds.md
- The Architecture of Open Source Applicationsaosabook.org
- Contributing to Complex Projects – Mitchell Hashimotomitchellh.com
- Big Ball of Mudlaputan.org
- Big Ball of Mudlaputan.org
- Visualizing a Codebasegithubnext.com
- Best practices for Claude Code - Claude Code Docsanthropic.com