You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that architecture (related) documents SHOULD have a single point of entry for any reader, be properly readable/understandable, and be easily maintainable.
Since there is already a git repo TechArch, I suggest to use this repo for
maintaining all of its documentation (versioned if need be);
develop the TechArch specific terminology (as per the guidance of CTWG);
have github actions turn the documentation into a nicely rendered static website;
(which is basically a setup that is similar to e.g. that of the eSSIF-Lab framework).
My guess is that setting it up would require a bit of effort (and a person that knows how to do that), but maintaining a once-installed structure should be doable (I do that for eSSIF-Lab).
The benefits I see are that
it achieves the requirements of the first sentence in this post;
it can start using the tools/CTWG toolbox as they become available;
it will make the Architecture have a professional look and feel (don't underestimate the effects of that).
The text was updated successfully, but these errors were encountered:
It seems to me that architecture (related) documents SHOULD have a single point of entry for any reader, be properly readable/understandable, and be easily maintainable.
Since there is already a git repo TechArch, I suggest to use this repo for
(which is basically a setup that is similar to e.g. that of the eSSIF-Lab framework).
My guess is that setting it up would require a bit of effort (and a person that knows how to do that), but maintaining a once-installed structure should be doable (I do that for eSSIF-Lab).
The benefits I see are that
The text was updated successfully, but these errors were encountered: