At one of previous gigs we had weekly newsletters organized and edited by our VP. Besides org-wide news it typically featured 1-2 freshly written in-depth artic

At one of previous gigs we had weekly newsletters organized and edited by our VP. Besides org-wide news it typically featured 1-2 freshly written in-depth articles about some piece of our system or project by engineers who worked on it. An archive of these posts served nicely as a repository of knowledge: if you needed to know how some component worked, often there was an article there by experts involved, even if somewhat dated, giving you enough background and pointers to get started. The background stories were especially interesting e.g. giving you some historical context why something exists and was designed this way, which is often missing from other forms of technical documentation.