adr-tools
log4brains
Our great sponsors
| adr-tools | log4brains | |
|---|---|---|
| 3 | 6 | |
| 4,388 | 1,059 | |
| - | - | |
| 0.0 | 0.0 | |
| about 2 months ago | 3 months ago | |
| Shell | TypeScript | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
adr-tools
-
What tools do you use to plan software features?
For architectural decisions I have used this in the past: https://github.com/npryce/adr-tools
- More persistent and less frenetic communication: alternatives to Slack
-
Documenting Software Architecture Decisions
👍 This approach is becoming more popular. It's a great way to document decisions and, for many teams, is a core part of their documentation bundle. ADRs don't take very long to put together, but they are incredibly useful to look back on, to help tell stories about how/why things changed, etc. Definitely recommended if you're not using them already, and Nat Pryce's adr-tools tool is an easy way to get started.
log4brains
-
A practical overview on Architecture Decision Records (ADR)
There is an interesting win-win tool called log4brains, that can turn your markdown into a static website. It's also integrated into MADR template. I haven’t had time to try them yet, but it's in my backlog.
-
Can't bring myself to produce code any more, any ideas to help?
I'm a solution architect in my current job, and I love it because I still get to solve technical problems and help/mentor more junior developers but I don't really write code anymore (except on minor occasions and it's mostly by choice). The tradeoff is I have to write docs and make presentations, but I learned how to do that easily enough.
- Build some good documentation habits in your team with ADRs (Architecture Decision Records) and their go-to tool: Log4brains
- Document your project by logging your decisions chronologically with ADRs (Architecture Decision Records)
- Log4brains: Document your projects by logging your decisions chronologically with ADRs (Architecture Decision Records)
- Document your projects by logging your architecture decisions chronologically with ADRs (Architecture Decision Records)
What are some alternatives?
standard-readme - A standard style for README files
vscode-front-matter - Front Matter is a CMS running straight in Visual Studio Code. Can be used with static site generators like Hugo, Jekyll, Hexo, NextJs, Gatsby, and many more...
jellyfin-docs - Documentation for Jellyfin
documentalist - :memo: A sort-of-static site generator optimized for living documentation of software projects
github-action-markdown-link-check - Check all links in markdown files if they are alive or dead. 🔗✔️
mdSilo-app - Lightweight Knowledge Base and Feed Reader.
udoxy - Guidelines and script (bash) for generic standalone code documentation
mm-docs-template - Template to use with mm-docs
docs - Rundeck documentation
prpl - Lightweight library for building fast static sites
EMBA - EMBA - The firmware security analyzer
slant - Beautiful static documentation for your API