From 2c95ca68777e39d55d72ef704442d0c1a77c40ee Mon Sep 17 00:00:00 2001 From: Rolfe Dlugy-Hegwer Date: Wed, 31 Jan 2024 13:51:01 -0500 Subject: [PATCH] Re-remove [role="_abstract"] #221 --- .../files/TEMPLATE_ASSEMBLY_a-collection-of-modules.adoc | 1 - .../files/TEMPLATE_CONCEPT_concept-explanation.adoc | 1 - .../files/TEMPLATE_PROCEDURE_doing-one-procedure.adoc | 1 - .../files/TEMPLATE_REFERENCE_reference-material.adoc | 1 - 4 files changed, 4 deletions(-) diff --git a/modular-docs-manual/files/TEMPLATE_ASSEMBLY_a-collection-of-modules.adoc b/modular-docs-manual/files/TEMPLATE_ASSEMBLY_a-collection-of-modules.adoc index aa2cc22..32614fb 100644 --- a/modular-docs-manual/files/TEMPLATE_ASSEMBLY_a-collection-of-modules.adoc +++ b/modular-docs-manual/files/TEMPLATE_ASSEMBLY_a-collection-of-modules.adoc @@ -39,7 +39,6 @@ If the assembly covers a task, start the title with a verb in the gerund form, s 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. //// -[role="_abstract"] 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. == Prerequisites diff --git a/modular-docs-manual/files/TEMPLATE_CONCEPT_concept-explanation.adoc b/modular-docs-manual/files/TEMPLATE_CONCEPT_concept-explanation.adoc index 6fdaabf..0f31142 100644 --- a/modular-docs-manual/files/TEMPLATE_CONCEPT_concept-explanation.adoc +++ b/modular-docs-manual/files/TEMPLATE_CONCEPT_concept-explanation.adoc @@ -30,7 +30,6 @@ In the title of concept modules, include nouns or noun phrases that are used in Be sure to include a line break between the title and the module introduction. //// -[role="_abstract"] Write a short introductory paragraph that provides an overview of the module. The contents of a concept module give the user descriptions and explanations needed to understand and use a product. diff --git a/modular-docs-manual/files/TEMPLATE_PROCEDURE_doing-one-procedure.adoc b/modular-docs-manual/files/TEMPLATE_PROCEDURE_doing-one-procedure.adoc index 81026c4..1685717 100644 --- a/modular-docs-manual/files/TEMPLATE_PROCEDURE_doing-one-procedure.adoc +++ b/modular-docs-manual/files/TEMPLATE_PROCEDURE_doing-one-procedure.adoc @@ -20,7 +20,6 @@ The ID is an anchor that links to the module. Avoid changing it after the module Start the title of a procedure module with a gerund, such as Creating, Installing, or Deploying. //// -[role="_abstract"] Write a short introductory paragraph that provides an overview of the module. The introduction should include what the module will help the user do and why it will be beneficial to the user. Include key words that relate to the module to maximize search engine optimization. .Prerequisites diff --git a/modular-docs-manual/files/TEMPLATE_REFERENCE_reference-material.adoc b/modular-docs-manual/files/TEMPLATE_REFERENCE_reference-material.adoc index 462fe28..526ef8b 100644 --- a/modular-docs-manual/files/TEMPLATE_REFERENCE_reference-material.adoc +++ b/modular-docs-manual/files/TEMPLATE_REFERENCE_reference-material.adoc @@ -30,7 +30,6 @@ In the title of a reference module, include nouns that are used in the body text Be sure to include a line break between the title and the module introduction. //// -[role="_abstract"] Write a short introductory paragraph that provides an overview of the module. 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.