Background
My organization's backend and frontend teams are starting to use Architecture Decisions Records (ADRs) as part of our decision and documentation process. We were inspired by Lullabot's Andrew Berry's blog post Improving Team Efficiency with Architecture Decision Records. Andrew cited Michael Nygard's article, Documenting Architecture Decisions, as the source of inspiration. Andrew notes that one key goal for ADRs is to provide valuable documentation via the below quote from Micheal's article.
My best anecdotal proof of the immediate value of ADRs is while reviewing Lullabot's public ADRs, I discovered their Use Type Tray to improve editorial UX ADR. The Type Tray module is an excellent solution for improving UI/UX for adding new content. The Schema.org Blueprints module now provides a simple Type Tray integration sub-module that automatically generates the content type groupings and icon assignments. The proof here is that if we, as a team and community members, document and share our thought processes and decisions, others can learn and improve upon them.
Recently, a tech lead on my team expressed a reasonable concern that they wanted to ensure all team members understand the architecture decisions behind the Schema.org Blueprints module, sub-modules, and its demo. Currently, only the Read More