I agree but aren’t there docs that might be needed by non-technical people as well. The general doc repo might contain “bureaucratic” information (what I mean is who owns the application, what is the security concept, what other apps does it communicate with and who are their owners, how does it get audited, etc.).
Of course we can set up an export to a static website from the repo, but how would a non-technical person edit it, say if the owner or audit process changes?
Comments
I agree but aren’t there docs that might be needed by non-technical people as well. The general doc repo might contain “bureaucratic” information (what I mean is who owns the application, what is the security concept, what other apps does it communicate with and who are their owners, how does it get audited, etc.).
Of course we can set up an export to a static website from the repo, but how would a non-technical person edit it, say if the owner or audit process changes?
Certain static sites can hook up into a WYSIWYG CMS backend, although I'm not sure how nice they play with version control.