From c7dc46faef3c3e402e6ecf78332e8d80a4939729 Mon Sep 17 00:00:00 2001
From: Wolfgang Bangerth <bangerth@colostate.edu>
Date: Thu, 12 Sep 2024 12:56:42 -0600
Subject: [PATCH] Remove a section about ways to use doxygen that we don't use.

---
 doc/developers/writing-documentation.html | 20 --------------------
 1 file changed, 20 deletions(-)

diff --git a/doc/developers/writing-documentation.html b/doc/developers/writing-documentation.html
index 83d9df1cc6..40d4777c16 100644
--- a/doc/developers/writing-documentation.html
+++ b/doc/developers/writing-documentation.html
@@ -238,26 +238,6 @@ void foobar ()
 </pre>
     </ul>
 
-    <h3>Code examples for the usage of single classes</h3>
-    <p>
-    Writing example files for classes is supported by
-    <acronym>doxygen</acronym>. These example files go into
-    <tt>deal.II/examples/doxygen</tt>. If they are short,
-    documentation should be inside and they are included into the
-    documentation with <code>@include filename</code>. Take a look how
-    the class <code>BlockMatrixArray</code> does this.
-    </p>
-
-    <p>
-    Larger example files should be documented using the
-    <acronym>doxygen</acronym> command <code>@dotinclude</code> and
-    related commands. However, if these programs do something
-    reasonable and do not only demonstrate a single topic, you should
-    consider converting them to a complete example program in the
-    <code>step-XX</code> series.
-    </p>
-
-
 
     <a name="examples"></a>
     <h2>Writing example programs for the tutorial</h2>
-- 
2.39.5