#1070 (#1071)

* #1070

Author: jackdewinter

changelog.md

@@ -8,7 +8,9 @@
   - Started movement of docs from README.md and docs directory to
     the newdocs directory with a shorter README.md.
 - [Issue 1059](https://github.com/jackdewinter/pymarkdown/issues/1059)
-  - Added updated pre-commit documentation.
+  - Complete redo of pre-commit documentation.
+- [Issue 1070](https://github.com/jackdewinter/pymarkdown/issues/1070)
+  - Complete redo of advanced configuration documentation.
 
 ### Fixed
 

newdocs/.pymarkdown.yaml

@@ -8,3 +8,7 @@ plugins:
     enabled: false
   list-anchored-indent:
     enabled: true
+
+        # "list-marker-space" : {
+        #     "enabled": false
+        # },

newdocs/clean.json

@@ -4,7 +4,7 @@
             "enabled": true,
             "code_block_line_length" : 160
         },
-        "list-marker-space" : {
+        "ul-indent" : {
             "enabled": false
         },
         "list-anchored-indent" : {

newdocs/src/advanced_configuration.md

@@ -7,3 +7,6 @@ Other things that will be added:
 
 - ensure solid documentation on each extensions
 - ensure each extension has good examples
+
+- move Pragma Extension and Front-Matter Extension from user guide into here, with
+  teaser left there

newdocs/src/advanced_extensions.md

@@ -203,7 +203,7 @@ This section relates to configuration files, as they are described in the
 document on [Advanced Configuration](./advanced_configuration.md#configuration-files).
 If you have not read that document to understand how PyMarkdown handles
 configuration files, please read that document before proceeding.  Note that
-while we can specify configuration files with [different internal formats](./advanced_configuration.md#different-types),
+while we can specify configuration files with [different internal formats](./advanced_configuration.md#configuration-file-types),
 the following configuration examples are going to specify a JSON configuration file
 named `pymarkdown.json`.
 
@@ -466,7 +466,7 @@ on these subjects.
 
 ### Command Line Arguments Vs Configuration File
 
-As part of our documentation on [Advanced Configuration](./advanced_configuration.md#command-line-arguments-vs-configuration-file),
+As part of our documentation on [Advanced Configuration](./advanced_configuration.md#command-line-vs-configuration-file),
 we delve into this topic, providing our views on why to choose configuration files
 over command line arguments.  There is no cut-and-dried answer that we can provide
 for everyone.  Your own team's context is important.

newdocs/src/advanced_pre-commit.md

@@ -590,7 +590,7 @@ In addition to enabling and disabling rules, many of the rules have extra config
 that allow you to adjust their
 default values to meet your needs.  Information on how to set that configuration
 on
-a per rule basis is covered in the document [Advanced Configuration](./advanced_configuration.md).
+a per rule basis is covered in the document [Advanced Configuration](./advanced_configuration.md#rule-plugins).
 For other information
 about rules and their capabilities, consult the [Advanced Rules Guide](./advanced_plugins.md).
 That guide covers these topics in more detail, including a list of all rules that
@@ -669,7 +669,7 @@ of configuration
 files is simple, there are a fair number of interactions to consider
 when supplying configuration.  As such, this is more fully covered in the
 [Advanced Configuration](./advanced_configuration.md)
-document.
+document, especially the section on the [configuration files](./advanced_configuration.md#configuration-files).
 
 ##### --set  (configuration)
 
@@ -678,7 +678,7 @@ to explicitly set for
 the current execution of the PyMarkdown application.  While the basic usage of configuration
 files is typically simple, there are a fair number of interactions to consider
 when supplying configuration.  As such, this is more fully covered in the
-[Advanced Configuration](./advanced_configuration.md)
+[Advanced Configuration](./advanced_configuration.md#specific-command-line-settings)
 section of this documentation.
 
 ##### --strict-config (configuration)