Add the module type attribute; Issue #18

See also redhat-documentation/modular-docs#151

Author: msuchane

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

@@ -5,6 +5,14 @@ Base the file name and the ID on the module title. For example:
 * Title: = My concept module A
 ////
 
+////
+Indicate the module type in one of the following
+ways:
+Add the prefix con- or con_ to the file name.
+Add the following attribute before the module ID:
+////
+:_module-type: CONCEPT
+
 ////
 The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
 

data/generated/minimal-concept.adoc

@@ -1,3 +1,5 @@
+:_module-type: CONCEPT
+
 [id="minimal-concept_{context}"]
 = Minimal concept
 

data/generated/minimal-procedure.adoc

@@ -1,3 +1,5 @@
+:_module-type: PROCEDURE
+
 [id="minimal-procedure_{context}"]
 = Minimal procedure
 

data/generated/minimal-reference.adoc

@@ -1,3 +1,5 @@
+:_module-type: REFERENCE
+
 [id="minimal-reference_{context}"]
 = Minimal reference
 

data/generated/proc_testing-a-procedure.adoc

@@ -9,6 +9,14 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 ////
 
+////
+Indicate the module type in one of the following
+ways:
+Add the prefix proc- or proc_ to the file name.
+Add the following attribute before the module ID:
+////
+:_module-type: PROCEDURE
+
 [id="proc_testing-a-procedure_{context}"]
 = Testing a procedure
 ////

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

@@ -9,6 +9,14 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 ////
 
+////
+Indicate the module type in one of the following
+ways:
+Add the prefix ref- or ref_ to the file name.
+Add the following attribute before the module ID:
+////
+:_module-type: REFERENCE
+
 [id="ref_the-lines-in-a-reference-module_{context}"]
 = The lines in a reference module
 ////

data/templates/concept.adoc

@@ -5,6 +5,14 @@ Base the file name and the ID on the module title. For example:
 * Title: = My concept module A
 ////
 
+////
+Indicate the module type in one of the following
+ways:
+Add the prefix con- or con_ to the file name.
+Add the following attribute before the module ID:
+////
+:_module-type: CONCEPT
+
 ////
 The ID is an anchor that links to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
 

data/templates/procedure.adoc

@@ -9,6 +9,14 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 ////
 
+////
+Indicate the module type in one of the following
+ways:
+Add the prefix proc- or proc_ to the file name.
+Add the following attribute before the module ID:
+////
+:_module-type: PROCEDURE
+
 [id="{{module_id}}_{context}"]
 = {{module_title}}
 ////

data/templates/reference.adoc

@@ -9,6 +9,14 @@ The ID is an anchor that links to the module. Avoid changing it after the module
 The `context` attribute enables module reuse. Every module ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 ////
 
+////
+Indicate the module type in one of the following
+ways:
+Add the prefix ref- or ref_ to the file name.
+Add the following attribute before the module ID:
+////
+:_module-type: REFERENCE
+
 [id="{{module_id}}_{context}"]
 = {{module_title}}
 ////