(httpd-site) branch asf-site updated: Automatic Site Publish by Buildbot
[email protected] Mon, 22 Jun 2026 17:09:35 +0000
| Newsgroups | gmane.comp.apache.cvs |
|---|---|
| Message-ID | <178214817501.1862378.13599043697585144619@gitbox3-he-fi.apache.org> |
This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/httpd-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 95bf823 Automatic Site Publish by Buildbot
95bf823 is described below
commit 95bf823c584d768d24a0d7b596930e93dc47fa33
Author: buildbot <[email protected]>
AuthorDate: Mon Jun 22 17:09:31 2026 +0000
Automatic Site Publish by Buildbot
---
output/docs-project/docsformat.html | 59 ++----------------------------------
output/docs-project/style-guide.html | 2 +-
2 files changed, 4 insertions(+), 57 deletions(-)
diff --git a/output/docs-project/docsformat.html b/output/docs-project/docsformat.html
index 470ec45..317788d 100644
--- a/output/docs-project/docsformat.html
+++ b/output/docs-project/docsformat.html
@@ -94,63 +94,10 @@ documentation and how to transform it into HTML for review.</p>
<p>The documentation is written in a custom XML format with its own DTD.
The DTD is in the
<a href="https://httpd.apache.org/docs/current/style/">style directory</a> of the
-manual. For detailed markup conventions, see the
+manual.</p>
+<p>For markup conventions, element usage, prose style rules, and
+typographic guidelines, see the
<a href="style-guide.html">Documentation Style Guide</a>.</p>
-<h3 id="common-markup-elements">Common Markup Elements<a class="headerlink" href="#common-markup-elements" title="Permalink">¶</a></h3>
-<table class="table">
-<thead>
-<tr>
-<th>Element</th>
-<th>Purpose</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td><code><example> ... </example></code></td>
-<td>Wraps a code example block</td>
-</tr>
-<tr>
-<td><code><highlight language="config"> ... </highlight></code></td>
-<td>Configuration example with syntax highlighting</td>
-</tr>
-<tr>
-<td><code><highlight language="perl"> ... </highlight></code></td>
-<td>Perl code with highlighting</td>
-</tr>
-<tr>
-<td><code><highlight language="lua"> ... </highlight></code></td>
-<td>Lua code with highlighting</td>
-</tr>
-<tr>
-<td><code><highlight language="C"> ... </highlight></code></td>
-<td>C code with highlighting</td>
-</tr>
-<tr>
-<td><code><directive module="...">Name</directive></code></td>
-<td>Cross-reference to a directive</td>
-</tr>
-<tr>
-<td><code><module>mod_name</module></code></td>
-<td>Cross-reference to a module</td>
-</tr>
-<tr>
-<td><code><program>name</program></code></td>
-<td>Cross-reference to an httpd program</td>
-</tr>
-<tr>
-<td><code><var>placeholder</var></code></td>
-<td>User-supplied value</td>
-</tr>
-<tr>
-<td><code><note> ... </note></code></td>
-<td>Informational callout</td>
-</tr>
-<tr>
-<td><code><note type="warning"> ... </note></code></td>
-<td>Warning callout</td>
-</tr></tbody></table>
-<p>The full format is best learned by reading existing documentation files.
-Start with a simple page and the patterns will become clear quickly.</p>
<h2 id="viewing-your-changes">Viewing Your Changes<a class="headerlink" href="#viewing-your-changes" title="Permalink">¶</a></h2>
<p>Modern browsers can render the XML files directly by applying the
referenced XSLT stylesheet. Simply open the <code>.xml</code> file in your browser
diff --git a/output/docs-project/style-guide.html b/output/docs-project/style-guide.html
index 2fa2706..908aa1d 100644
--- a/output/docs-project/style-guide.html
+++ b/output/docs-project/style-guide.html
@@ -330,7 +330,7 @@ Listen 8000
</highlight>
</example>
</code></pre>
-<p>Valid language values: <code>config</code> (most common), <code>lua</code>, <code>c</code>, <code>perl</code>, <code>sh</code>, <code>html</code>.</p>
+<p>Valid language values: <code>config</code> (most common), <code>sh</code>, <code>python</code>, <code>lua</code>, <code>c</code>, <code>perl</code>, <code>html</code>.</p>
<p>Do <strong>not</strong> use bare <code><example></code> with <code><br /></code> for line breaks. This is a
legacy pattern. Convert to <code><highlight></code> when editing such files.</p>
<p>If an example needs a title, use <code><example><title></code>:</p>