Document reviewer guidelines for reference architectures
Open
- Dominant language
- Go
- Stars
- 104
- Forks
- 14
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 3
Description
Expected sections in the actual ref architecture.
* Projects and Usage
* TLDR; Synopsis
* Use Cases as Sub-items
* Architecture
* Mandatory diagram with high quality image and specific format accepted
* Potentially
* What works well
* What needs improvement, Challenges, Risks
* Key Takeaways, Lessons Learned
* Optionally a more detailed journey with info on intermediate steps and things that got dropped on the way
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.