aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGöktürk Yüksek <gokturk@gentoo.org>2017-04-17 18:07:56 -0400
committerGöktürk Yüksek <gokturk@gentoo.org>2017-04-17 18:07:56 -0400
commit4cbf0bacaee312eb0b240205d5566a6660833814 (patch)
tree196df0f6c73c549f8e6534758e91c75fa3938ee9
parentappendices/contributing/devbook-guide: chapter doesn't support id attribute (diff)
downloaddevmanual-4cbf0bacaee312eb0b240205d5566a6660833814.tar.gz
devmanual-4cbf0bacaee312eb0b240205d5566a6660833814.tar.bz2
devmanual-4cbf0bacaee312eb0b240205d5566a6660833814.zip
appendices/contributing/devbook-guide: remove the section on FAQ
We do not have FAQ in devmanual and it doesn't render <faqindex/>.
-rw-r--r--appendices/contributing/devbook-guide/text.xml24
1 files changed, 0 insertions, 24 deletions
diff --git a/appendices/contributing/devbook-guide/text.xml b/appendices/contributing/devbook-guide/text.xml
index 2ad0ad7..ce4749e 100644
--- a/appendices/contributing/devbook-guide/text.xml
+++ b/appendices/contributing/devbook-guide/text.xml
@@ -485,30 +485,6 @@ to <uri link="#doc_chap2_pre2">code listing 2 in chapter 2</uri>, type
</body>
</section>
-<section>
-<title>FAQs</title>
-<body>
-
-<p>
-FAQ documents need to start with a list of questions with links to their
-answers. Creating such a list is both time-consuming and error-prone. The list
-can be created automatically if you use a <c>faqindex</c> element as the first
-chapter of your document. This element has the same structure as a
-<c>chapter</c> to allow some introductory text. The structure of the document
-is expected to be split into chapters (at least one chapter) containing
-sections, each section containing one question specified in its <c>title</c>
-element with the answer in its <c>body</c>. The FAQ index will appear as one
-section per chapter and one link per question.
-</p>
-
-<p>
-A quick look at a <uri link="/doc/en/faq.xml">FAQ</uri> and <uri
-link="/doc/en/faq.xml?passthru=1">its source</uri> should make the above
-obvious.
-</p>
-
-</body>
-</section>
</chapter>
<chapter id="codingstyle">