From 57abdd89d91b27c393f2aeb82e2ca69d5654a977 Mon Sep 17 00:00:00 2001
From: Simon Michael <simon@joyful.com>
Date: Fri, 26 Sep 2025 14:06:07 -1000
Subject: [PATCH] ;doc:DOCS: updates, add doc-update diagram

---
 doc/DOCS.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/doc/DOCS.md b/doc/DOCS.md
index a783ec4a1..215930964 100644
--- a/doc/DOCS.md
+++ b/doc/DOCS.md
@@ -1,11 +1,14 @@
-# Docs
+# DOCS
 
 <div class=pagetoc>
 
 <!-- toc -->
 </div>
 
-## hledger's documentation structure
+An overview of hledger's documentation structure and process, for developers and maintainers.
+(For user documentation, see [Docs](docs.md).)
+
+## Documentation structure
 
 <div style="margin:1em 2em; font-style:italic;">
 "There is a secret that needs to be understood in order to write good
@@ -227,6 +230,12 @@ In the release branch, once the corresponding github release is created, after u
 1. Cherry pick the latest release notes (`doc/relnotes.md`) from the release branch to master.
 2. Push to the master branch on github. The website's "Release notes" page will update automatically.
 
+### Diagrams
+
+(approximate)
+[![doc update diagrams](doc-update.png)](doc-update.png)
+
+
 
 ## 201901 docs reorg (#920, WIP)