Skip to content

Commit c9bb0e4

Browse files
committed
No longer require the abstract tag
1 parent a4485e8 commit c9bb0e4

13 files changed

+4
-22
lines changed

data/generated/assembly_testing-that-an-assembly-forms-properly.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,6 @@ If the assembly covers a task, start the title with a verb in the gerund form, s
4040
The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
4141
////
4242

43-
[role="_abstract"]
4443
This paragraph is the assembly introduction. It explains what the user will accomplish by working through the modules in the assembly and sets the context for the user story the assembly is based on.
4544

4645
== Prerequisites

data/generated/con_a-title-that-tests-a-concept.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@ The `context` attribute enables module reuse. Every module ID includes {context}
2525
In the title of concept modules, include nouns or noun phrases that are used in the body text. This helps readers and search engines find the information quickly. Do not start the title of concept modules with a verb. See also _Wording of headings_ in _The IBM Style Guide_.
2626
////
2727

28-
[role="_abstract"]
2928
Write a short introductory paragraph that provides an overview of the module.
3029

3130
The contents of a concept module give the user descriptions and explanations needed to understand and use a product.

data/generated/minimal-assembly.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ endif::[]
1212

1313
:context: minimal-assembly
1414

15-
[role="_abstract"]
16-
1715
== Prerequisites
1816

1917
[role="_additional-resources"]

data/generated/minimal-concept.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@
33
[id="minimal-concept_{context}"]
44
= Minimal concept
55

6-
[role="_abstract"]
7-
86
[role="_additional-resources"]
97
.Additional resources
108

data/generated/minimal-procedure.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@
33
[id="minimal-procedure_{context}"]
44
= Minimal procedure
55

6-
[role="_abstract"]
7-
86
.Prerequisites
97

108
.Procedure

data/generated/minimal-reference.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@
33
[id="minimal-reference_{context}"]
44
= Minimal reference
55

6-
[role="_abstract"]
7-
86
[role="_additional-resources"]
97
.Additional resources
108

data/generated/proc_testing-a-procedure.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@ Add the following attribute before the module ID:
2323
Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.
2424
////
2525

26-
[role="_abstract"]
2726
Write a short introductory paragraph that provides an overview of the module.
2827

2928
Procedure modules should include the steps that users perform and address user motivation.

data/generated/ref_the-lines-in-a-reference-module.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,6 @@ Add the following attribute before the module ID:
2323
In the title of a reference module, include nouns that are used in the body text. For example, "Keyboard shortcuts for ___" or "Command options for ___." This helps readers and search engines find the information quickly.
2424
////
2525

26-
[role="_abstract"]
2726
Write a short introductory paragraph that provides an overview of the module.
2827

2928
A reference module provides data that users might want to look up, but do not need to remember. It has a very strict structure, often in the form of a list or a table.

data/templates/assembly.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,6 @@ If the assembly covers a task, start the title with a verb in the gerund form, s
4040
The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID so you can include it multiple times in the same guide.
4141
////
4242
43-
[role="_abstract"]
4443
{% if examples -%}
4544
This paragraph is the assembly introduction. It explains what the user will accomplish by working through the modules in the assembly and sets the context for the user story the assembly is based on.
4645
{%- endif %}

data/templates/concept.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@ The `context` attribute enables module reuse. Every module ID includes {context}
2525
In the title of concept modules, include nouns or noun phrases that are used in the body text. This helps readers and search engines find the information quickly. Do not start the title of concept modules with a verb. See also _Wording of headings_ in _The IBM Style Guide_.
2626
////
2727

28-
[role="_abstract"]
2928
{% if examples -%}
3029
Write a short introductory paragraph that provides an overview of the module.
3130

0 commit comments

Comments
 (0)