exploring-the-testing-hyperpyramid
structurizr-site-generatr
| exploring-the-testing-hyperpyramid | structurizr-site-generatr | |
|---|---|---|
| 2 | 1 | |
| 11 | 186 | |
| - | 8.6% | |
| 5.4 | 9.4 | |
| about 2 months ago | 4 days ago | |
| Kotlin | Kotlin | |
| - | 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.
exploring-the-testing-hyperpyramid
-
Architecture diagrams enable better conversations
Http4k, a http library for Kotlin, has an, in my opinion, great way of generating documentation for you [0]. They explain it in more detail in their talk [1] and also have an example repository [2], if you favor to look at code.
[0] https://www.http4k.org/blog/http4k_v5/#tracerbullet_a_brand_...
[1] https://www.youtube.com/watch?v=CrslqbMbaD8
[2] https://github.com/http4k/exploring-the-testing-hyperpyramid
-
http4k at KotlinConf '23: Exploring the Testing Hyperpyramid. aka: Auto-generation of visual documentation from tests
There is also a companion GitHub repo where you can find all of the code.
structurizr-site-generatr
-
Architecture diagrams enable better conversations
Recently been doing the same amongst our various teams since we have a mish-mash of Lucidchart, Miro, and other collaborative design tools.
One thing I was experimenting with (read: struggling with!) was a way to keep per-service (per-repo) architecture workspaces which are also synchronized on-commit to a central workspace and used !include to bind them together. The moving parts are not difficult - but writing your DSLs in a way that can handle this can be. This idea would let individual projects be self-sufficient and generate their own README doc diagrams as part of their own build process; but also have a central site which shows all the services as well as inter-service connectivity.
Did you ever consider https://github.com/avisi-cloud/structurizr-site-generatr to bring together your ADRs in with your architecture, or do you keep them separate?
What are some alternatives?
architecture-decision
arc42.org-site - (jekyll-based) website for arc42.org - the template for communicating software architectures.
java - Structurizr for Java
Diagon - Interactive ASCII art diagram generators. :star2:
d2 - D2 is a modern diagram scripting language that turns text to diagrams.
c4-notation - Technical resources for using the C4 model for visualizing software architecture.
architecture_decision_record - Architecture decision record (ADR) examples for software planning, IT leadership, and template documentation
asciiflow - ASCIIFlow