Issues-109-111-115 updated filenames

Author: emmurphy1

modular-docs-manual/content/topics/module_anchor-and-file-names-concept.adoc

@@ -1,14 +1,49 @@
-[id="anchor-and-file-names"]
-= Anchor Names and File Names
+[id="module_anchor-and-file-names-concept"]
+= File Names and Anchors
 
-To optimize modular documentation, follow these guidelines for naming module anchors and files:
+To optimize modular documentation, follow these guidelines for naming files and creating anchors:
 
-Anchor names:: Provide an anchor in the format `+++[id="anchor-name_{context}"]+++` for every module so that it can be identified by Asciidoctor when reused or cross-referenced. `+++{context}+++` is a variable whose value you define in the assembly. Give the anchor the same or similar name as the module heading. Separate the words in the anchor with hyphens and use an underscore to separate the `+++{context}+++` part:
-+
+.File names
+Assembly and module file names should accurately and closely reflect the title of the assembly or module. File names should have the format `prefix-filename.adoc` or `prefix_filename.adoc` where `prefix` is one of the following module prefixes:
+
+* `con`: Concept module prefix
+* `proc`: Procedure module prefix
+* `ref`: Reference module prefix
+* `assembly`: Assembly module prefix
+
+.Examples
+* `con-guided-decision-tables.adoc`  (Concept module)
+* `proc-creating-guided-decision-tables.adoc`  (Procedure module for creating)
+* `proc-editing-guided-decision-tables.adoc`  (Procedure module for editing)
+* `ref-guided-decision-table-examples.adoc`  (Reference module with examples)
+* `ref-guided-decision-table-columns.adoc`  (Reference module with column types)
+* `assembly-designing-guided-decision-tables.adoc`  (Assembly of guided decision table modules)
+
+
+[NOTE]
+====
+Do not include special characters in file names. Ensure that all members of your team use the same file naming conventions.
+====
+
+These file naming guidelines are optional but highly recommended. However, if your team does not include the module prefixes in file names followed by either a hyphen (-) or an underscore (_), you must include one of the following variables in each concept, procedure, and reference module:
+
+NOTE: This is a Pantheon 2 requirement.
+
+[source]
+----
+:system-module-type: CONCEPT
+:system-module-type: PROCEDURE
+:system-module-type: REFERENCE
+----
+
+
+
+.Anchors
+At the top of every module, provide an anchor in the format `+++[id="filename_{context}"]+++` where `filename` is the exact name of the file, without the file extension (`.adoc`). Module anchors are necessary so that the module can be identified by Asciidoctor when reused or cross-referenced. The `{context}` variable is intentionally not defined in the module anchor ID. You define a context value in each assembly, in the format `:context: my-context-value`. This enables the context variable in each module to be populated according to the relevant assembly.
 --
 [source]
 ----
-[id="anchor-name_{context}"]
+[id="filename_{context}"]
 = Module Heading
 
 The first sentence of the topic.
@@ -17,7 +52,8 @@ The first sentence of the topic.
 .Example 1. Concept Module
 [source]
 ----
-[id="guided-decision-tables_{context}"]
+[id="con-guided-decision-tables_{context}"]
+
 = Guided Decision Tables
 
 The guided decision tables feature works similarly to ...
@@ -26,7 +62,7 @@ The guided decision tables feature works similarly to ...
 .Example 2. Procedure Module
 [source]
 ----
-[id="creating-guided-decision-tables_{context}"]
+[id="pro-creating-guided-decision-tables_{context}"]
 = Creating Guided Decision Tables
 
 You can use guided decision tables to ...
@@ -38,26 +74,8 @@ You can use guided decision tables to ...
 The format defined here is recommended because it is the most stable and versatile of anchor formats, and supports variables that enable topics to be reused and cross-referenced properly. For details, see xref:reusing-modules[]. Other anchor formats include `+++[[anchor-name]]+++` and `+++[#anchor-name]+++`, but these formats either do not support variables for content reuse or do not support certain character types, such as periods. These limitations cause errors at build time.
 ====
 
-NOTE: The underscore is recommended as the separator for `+++{context}+++`, because this facilitates tooling to distinguish the context part from the base anchor ID.
-
-For more information about Asciidoc anchors, see the link:http://asciidoctor.org/docs/user-manual/#anchordef[Asciidoctor User Manual].
 --
 
-File names:: Give the module file the same name as the anchor used in it (which is the same as or similar to the module heading). Assembly and module file names should accurately and closely reflect the title of the assembly or module.
-+
-[NOTE]
-====
-Ensure that all members of your team use the same file naming conventions.
-====
-+
-.Examples
-* `guided-decision-tables.adoc`  (Concept module)
-* `creating-guided-decision-tables.adoc`  (Procedure module for creating)
-* `editing-guided-decision-tables.adoc`  (Procedure module for editing)
-* `guided-decision-table-examples.adoc`  (Reference module with examples)
-* `guided-decision-table-columns.adoc`  (Reference module with column types)
-* `designing-guided-decision-tables.adoc`  (Assembly of guided decision table modules)
-
 .Additional Resources
 
-* The link:http://asciidoctor.org/docs/user-manual/#anchordef[Asciidoctor User Manual]
+* link:https://asciidoctor.org/docs/user-manual/[Asciidoctor User Manual]

modular-docs-manual/content/topics/using_text_snippets_or_text_fragments.adoc

@@ -1,18 +1,8 @@
-// Module included in the following assemblies:
-//
-// <List assemblies here, each on a new line>
 
-// Base the file name and the ID on the module title. For example:
-// * file name: my-concept-module-a.adoc
-// * ID: [id="my-concept-module-a_{context}"]
-// * Title: = My concept module A
+[id='using_text_snippets_or_text_fragments']
 
-// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
-[id="using_text_snippets_or_text_fragments_{context}"]
-// The `context` attribute enables module reuse. Every module's ID includes a variable that sets the context, such as {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
 = Text Snippets or Text Fragments (Pseudo-modules)
-//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_.
+
 
 [NOTE]
 The following standard is recommended when the documentation is being maintained without a Content Management System (CMS) capable of managing complex interrelations between modules.
@@ -23,8 +13,3 @@ Snippet (fragment) file use should be limited to:
 
 * Standardized admonitions (such as 'Technology preview' and 'Beta' text).
 * Where there is an existing standard between the upstream and downstream communities.
-
-
-//.Additional resources
-
-//* A bulleted list of links to other material closely related to the contents of the concept module.