From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:devbook-guide commit in: appendices/contributing/devbook-guide/
Date: Sun, 23 Sep 2018 14:54:27 +0000 (UTC) [thread overview]
Message-ID: <1537711668.9f5781ca8f2a0cfeb59194c375704d34a06e451a.ulm@gentoo> (raw)
commit: 9f5781ca8f2a0cfeb59194c375704d34a06e451a
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 23 14:07:48 2018 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Sep 23 14:07:48 2018 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=9f5781ca
appendices/contributing/devbook-guide: Move everything into a chapter.
Demote previous chapters to sections, and sections to subsections.
appendices/contributing/devbook-guide/text.xml | 72 +++++++++++++-------------
1 file changed, 37 insertions(+), 35 deletions(-)
diff --git a/appendices/contributing/devbook-guide/text.xml b/appendices/contributing/devbook-guide/text.xml
index 48fb0ae..23d496a 100644
--- a/appendices/contributing/devbook-guide/text.xml
+++ b/appendices/contributing/devbook-guide/text.xml
@@ -1,6 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<guide self="appendices/contributing/devbook-guide/">
+<chapter>
<title>Gentoo GuideXML Guide</title>
<abstract>
@@ -10,9 +11,9 @@ documentation, and this document itself was created using GuideXML. This guide
assumes a basic working knowledge of XML and HTML.
</abstract>
-<chapter>
-<title>GuideXML basics</title>
<section>
+<title>GuideXML basics</title>
+<subsection>
<title>GuideXML design goals</title>
<body>
@@ -30,12 +31,12 @@ documents.
</p>
</body>
+</subsection>
</section>
-</chapter>
-<chapter>
-<title>GuideXML</title>
<section>
+<title>GuideXML</title>
+<subsection>
<title>Basic structure</title>
<body>
@@ -125,8 +126,8 @@ license. This is still accepted/allowed.
</p>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Chapters and sections</title>
<body>
@@ -176,8 +177,8 @@ contain at least one <c><body></c> element.
</note>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>An example <body></title>
<body>
@@ -245,8 +246,8 @@ This is important.
</impo>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>The <body> tags</title>
<body>
@@ -273,8 +274,8 @@ exactly, making it well-suited for code excerpts. You must name the
</pre>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>
<c>, <b>, and <e>
</title>
@@ -308,8 +309,8 @@ prose more <e>punch</e>!
</p>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Code samples and colour-coding</title>
<body>
@@ -319,8 +320,8 @@ Fill this section with the information about the use of
</todo>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title><uri></title>
<body>
@@ -349,8 +350,8 @@ link="http://www.w3.org/QA/Tips/noClickHere">W3C</uri>.
</p>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Figures</title>
<body>
@@ -365,8 +366,8 @@ for adding images without captions, borders, etc.
</p>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Tables</title>
<body>
@@ -422,8 +423,8 @@ right-aligned, left-aligned or centered with the <c>align</c> attribute.
</table>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Lists</title>
<body>
@@ -436,8 +437,8 @@ that you must close all tags including list items unlike in HTML.
</p>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Intra-document references</title>
<body>
@@ -454,12 +455,12 @@ to <uri link="#doc_chap2_pre2">code listing 2 in chapter 2</uri>, type
</p>
</body>
+</subsection>
</section>
-</chapter>
-<chapter id="codingstyle">
-<title>Coding Style</title>
<section>
+<title>Coding Style</title>
+<subsection>
<title>Introduction</title>
<body>
@@ -476,8 +477,8 @@ Both sections are described next.
</p>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>Internal Coding Style</title>
<body>
@@ -560,8 +561,8 @@ Correct: <pre caption="Attributes">
</pre>
</body>
-</section>
-<section>
+</subsection>
+<subsection>
<title>External Coding Style</title>
<body>
@@ -595,12 +596,12 @@ Forums</uri> is preferred over <uri>http://forums.gentoo.org</uri>.
</p>
</body>
+</subsection>
</section>
-</chapter>
-<chapter>
-<title>Resources</title>
<section>
+<title>Resources</title>
+<subsection>
<title>Start writing</title>
<body>
@@ -617,6 +618,7 @@ to tackle. Have fun!
</p>
</body>
+</subsection>
</section>
</chapter>
</guide>
next reply other threads:[~2018-09-23 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 14:54 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-23 14:54 [gentoo-commits] proj/devmanual:devbook-guide commit in: appendices/contributing/devbook-guide/ Ulrich Müller
2018-09-23 14:54 Ulrich Müller
2017-07-29 20:55 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1537711668.9f5781ca8f2a0cfeb59194c375704d34a06e451a.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox