Skip to content

Commit 8abdb37

Browse files
authored
Merge pull request #31127 from michelle-purcell/doc-contributor-guide-enhancements
Enhancements to instructions for contributing to the Quarkus docs
2 parents afcb8c8 + 3dadb29 commit 8abdb37

File tree

2 files changed

+31
-8
lines changed

2 files changed

+31
-8
lines changed

docs/src/main/asciidoc/doc-contribute-docs-howto.adoc

+14-2
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,18 @@ include::_attributes.adoc[] <3>
5454
<2> For information about how to create a good title for each content type, see xref:{doc-guides}/doc-reference.adoc#titles-and-headings[Titles and headings] on the "Quarkus style and content guidelines" page.
5555
<3> The `_attributes.adoc` include is required to ensure that attributes get resolved, the table of contents is generated, and content renders in the website portal.
5656
<4> Set at least one category to ensure that the content is findable on the link:https://quarkus.io/guides/[Quarkus documentation home page]. For a list of Quarkus categories, see xref:{doc-guides}/doc-reference.adoc#document-attributes-and-variables[Document attributes and variables] on the "Quarkus style and content guidelines" page.
57+
+
58+
[IMPORTANT]
59+
====
60+
Ensure there are no line breaks in the header section until after `:categories:` line.
61+
====
62+
+
63+
. Add an abstract to describe the purpose of the guide.
64+
[IMPORTANT]
65+
====
66+
The first sentence of the abstract must explain the value and some benefit of the content in less than 27 words because this automatically displays on the link:https://quarkus.io/guides/[Quarkus guides homepage].
67+
There must also be a line break before and after the abstract.
68+
====
5769

5870
For more information about the minimum header requirements, see xref:{doc-guides}/doc-reference.adoc#document-structure[Document structure] on the "Quarkus style and content guidelines" page.
5971

@@ -75,8 +87,8 @@ newUrl: /guides/<new_asciidoc_filename> // <2>
7587
---
7688
+
7789
Where:
78-
<1> Is the name of the original AsciiDoc source file that you are retiring.
79-
<2> Is the name of the AsciiDoc source file that you want to redirect to.
90+
<1> Is the name of the original AsciiDoc source file that you are retiring, without the `.adoc` file extension.
91+
<2> Is the name of the AsciiDoc source file that you want to redirect to, without the `.adoc` file extension.
8092

8193
.Example
8294

docs/src/main/asciidoc/doc-reference.adoc

+17-6
Original file line numberDiff line numberDiff line change
@@ -149,29 +149,40 @@ Minimally, each document should define and id and a title, and include common at
149149
<3> Include common document attributes.
150150
<4> Specify the relevant <<Categories>> (comma separated).
151151

152-
==== Other common document attributes:
152+
[[doc-header-optional]]
153+
==== Other common document header attributes
153154

154155
`:extension-status: preview`:: Use this attribute to flag special types of content. Valid values: `experimental`, `preview`, `stable` (not usually used), and `deprecated`.
155156
`:summary: <text>`:: Use the summary to provide a concise (26 words or less) description of the document.
156-
This attribute will be used in tiles or other descriptions on the website. If not present, the contents of the <<Abstracts (preamble),preamble>> will be used instead.
157+
The value of this attribute is used in tiles or other descriptions on the website and is not required in newer diataxis-styled docs, as outlined in <<abstracts-preamble>>.
158+
If not present, the first sentence of the abstract is automatically used to generate the tile summary.
157159

158-
NOTE: Take care with whitespace when working with document-scoped attributes. The document header ends with the first blank line.
160+
IMPORTANT: Take care with whitespace when working with document-scoped attributes. The document header ends with the first blank line.
159161

162+
[[abstracts-preamble]]
160163
=== Abstracts (preamble)
161164

162-
Add a short description that helps your audience to quickly find and understand the purpose and intent of the page.
165+
The first paragraph in the main body is treated as the abstract, also referred to as the preamble.
166+
Add a short description that helps your audience quickly find and understand the purpose and intent of the page.
167+
The first sentence of the abstract provides a summary and gets automatically added to the tile on the link:https://quarkus.io/guides/[Quarkus guides homepage].
163168

164169
Try to write the abstract by using the following guidelines:
165170

166171
* *User oriented:* Contains terms and keywords that are familiar to users.
167-
* *Concise:* Avoids self-referential expressions and filler words, for example, "This document..", "This tutorial..", or "The following.."
172+
* *Concise:* Avoids self-referential expressions and filler words, for example:
173+
** "This document.."
174+
** "This tutorial..."
175+
** "The following..."
168176
* *Brief:* Is no more than three sentences long.
169177

170178
[IMPORTANT]
171179
====
172-
The first sentence of the abstract must explain the value and some benefit of the content in less than 27 words because this automatically displays on the link:https://quarkus.io/guides/[Quarkus guides homepage].
180+
Ensure that the first sentence explains the value and some benefits of the content in 26 words or less.
173181
====
174182

183+
If the first sentence is too long or can not be simplified to fit on the website tile, you can define a ``:summary:`` attribute in the document header attributes to serve that purpose.
184+
For more information, see <<doc-header-optional>>.
185+
175186
=== Semantic line breaks
176187

177188
:semantic-line-breaks: footnote:smbl[Rhodes, B. Semantic Linefeeds. https://rhodesmill.org/brandon/2012/one-sentence-per-line/]

0 commit comments

Comments
 (0)