normalize (--fix) all markdown files according to linter configuration

Author: rpietzsch

CONTRIBUTING.md

@@ -31,9 +31,9 @@ We suggest to use a specialized markdown editor such as [obsidian](https://obsid
 
 The following tools you need locally to get started:
 
--   [poetry](https://python-poetry.org/)
--   [task](https://taskfile.dev/)
--   git, markdown editor
+- [poetry](https://python-poetry.org/)
+- [task](https://taskfile.dev/)
+- git, markdown editor
 
 On a few OS distributions (e.g. Arch Linux) the tool/binary is named `go-task`.
 
@@ -71,26 +71,26 @@ Have a look at the [mkdocs-material documentation](https://squidfunk.github.io/m
 <details>
   <summary>Extend section</summary>
 
--   always create a directory + `index.md`, e.g. `my-topic/index.md` ([Example](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/automate/cmemc-command-line-interface))
--   add new pages to the `.pages` file to add them in the right order and with correct title to the menu ([Example](https://github.com/eccenca/documentation.eccenca.com/blob/main/docs/automate/cmemc-command-line-interface/.pages))
--   put images side by side to the `index.md` ([Example](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/release-notes/corporate-memory-22-1))
--   do not use images for icons esp. icons from the application
-    -   use eccenca icons, e.g. [:eccenca-application-queries:](https://github.com/eccenca/documentation.eccenca.com/blob/main/overrides/.icons/eccenca/application-queries.svg) -> [list](https://github.com/eccenca/documentation.eccenca.com/tree/main/overrides/.icons/eccenca)
-    -   use theme icons where no eccenca icon is available -> [list](https://squidfunk.github.io/mkdocs-material/reference/icons-emojis/#search)
--   name image files properly (not just `Screenshot.xxx.png`, [Example](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/release-notes/corporate-memory-22-1))
--   used advanced features where suitable
-    -   [Admonitions](https://squidfunk.github.io/mkdocs-material/reference/admonitions/#usage) (esp. use notes and warnings where needed) -> see Admonition section for more details
-    -   [Code Blocks](https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#usage) (e.g. enable highlightning and add a title)
-    -   [Content Tabs](https://squidfunk.github.io/mkdocs-material/reference/content-tabs/#usage) (to structure complex pages)
--   code blocks:
-    -   do not use line numbers except you refer to it in the text
-    -   use correct syntax highlightning (often used: `shell-session`, `bash`, `sparql`, `turtle`, `json`) -> [list of syntax IDs](https://pygments.org/docs/lexers/)
-    -   do not confuse `shell-session` with `bash` (the first is a terminal output, the latter a script syntax)
-    -   when using `shell-session`, use `$` as the prompt
--   Links:
-    -   do not use absolute links for internal documents, e.g. `https://documentation.eccenca.com/latest/...`
-    -   do not use base-relative links, e.g. `/automate/...`
-    -   use relative links to `index.md` files
+- always create a directory + `index.md`, e.g. `my-topic/index.md` ([Example](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/automate/cmemc-command-line-interface))
+- add new pages to the `.pages` file to add them in the right order and with correct title to the menu ([Example](https://github.com/eccenca/documentation.eccenca.com/blob/main/docs/automate/cmemc-command-line-interface/.pages))
+- put images side by side to the `index.md` ([Example](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/release-notes/corporate-memory-22-1))
+- do not use images for icons esp. icons from the application
+    - use eccenca icons, e.g. [:eccenca-application-queries:](https://github.com/eccenca/documentation.eccenca.com/blob/main/overrides/.icons/eccenca/application-queries.svg) -> [list](https://github.com/eccenca/documentation.eccenca.com/tree/main/overrides/.icons/eccenca)
+    - use theme icons where no eccenca icon is available -> [list](https://squidfunk.github.io/mkdocs-material/reference/icons-emojis/#search)
+- name image files properly (not just `Screenshot.xxx.png`, [Example](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/release-notes/corporate-memory-22-1))
+- used advanced features where suitable
+    - [Admonitions](https://squidfunk.github.io/mkdocs-material/reference/admonitions/#usage) (esp. use notes and warnings where needed) -> see Admonition section for more details
+    - [Code Blocks](https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#usage) (e.g. enable highlightning and add a title)
+    - [Content Tabs](https://squidfunk.github.io/mkdocs-material/reference/content-tabs/#usage) (to structure complex pages)
+- code blocks:
+    - do not use line numbers except you refer to it in the text
+    - use correct syntax highlightning (often used: `shell-session`, `bash`, `sparql`, `turtle`, `json`) -> [list of syntax IDs](https://pygments.org/docs/lexers/)
+    - do not confuse `shell-session` with `bash` (the first is a terminal output, the latter a script syntax)
+    - when using `shell-session`, use `$` as the prompt
+- Links:
+    - do not use absolute links for internal documents, e.g. `https://documentation.eccenca.com/latest/...`
+    - do not use base-relative links, e.g. `/automate/...`
+    - use relative links to `index.md` files
 
 </details>
 
@@ -104,13 +104,13 @@ On this page is search function for icons available as well.
 <details>
   <summary>Extend section</summary>
 
-|Admonition Name|Used For |Example|
-|---------------|---------|-------|
-|Info |Information in documentation provides details about a topic or process that the reader needs to know. It is usually essential and relevant to the main subject of the document.|Statement annotations provide a way to express knowledge about statements. This group is dedicated to properties that configure the Statement Annotation feature|
-|Note |A note provides additional details that may or may not be directly related to the main topic. It could be an explanation, clarification, or an aside that the writer thinks would be helpful for the reader to know.|The graph selection drop-down might or might not be visible depending the existence of an (optional) EasyNav Module configuration. In case no specific module configuration exists or non has not has been set for the current workspace the graph selection will be shown. A EasyNav Module configuration pre-configures a graph. Thus, the dropdown will not be shown if such has been configured for the current workspace.|
-|Abstract|An abstract is a brief summary that provides an overview of the main points or contents of a document. It typically appears at the beginning of a document and is intended to give the reader an idea of what to expect from the document.|This tutorial explores the benefits of using cloud computing in enterprise organizations. It discusses the advantages of cloud computing over traditional on-premises infrastructure, and provides guidance for migrating to the cloud.|
-|Warning|It is used to convey the seriousness of the risk and the importance of taking necessary precautions to avoid harm.|If the remote file resource is used in more than one dataset, the other datasets are also affected by this command.|
-|Tip|A tip is a type of admonition in documentation that provides a helpful suggestion or best practice related to the content of the document. It is typically used to guide the reader towards a more efficient or effective way of using a product or service, or to provide additional insights or recommendations.|We have the suggestion option as well; click on the +icon and select the suggestion mapping.|
+| Admonition Name | Used For | Example |
+| ----  ----------- | -------- | ------- |
+| Info | Information in documentation provides details about a topic or process that the reader needs to know. It is usually essential and relevant to the main subject of the document. | Statement annotations provide a way to express knowledge about statements. This group is dedicated to properties that configure the Statement Annotation feature |
+| Note | A note provides additional details that may or may not be directly related to the main topic. It could be an explanation, clarification, or an aside that the writer thinks would be helpful for the reader to know. | The graph selection drop-down might or might not be visible depending the existence of an (optional) EasyNav Module configuration. In case no specific module configuration exists or non has not has been set for the current workspace the graph selection will be shown. A EasyNav Module configuration pre-configures a graph. Thus, the dropdown will not be shown if such has been configured for the current workspace. |
+| Abstract | An abstract is a brief summary that provides an overview of the main points or contents of a document. It typically appears at the beginning of a document and is intended to give the reader an idea of what to expect from the document. | This tutorial explores the benefits of using cloud computing in enterprise organizations. It discusses the advantages of cloud computing over traditional on-premises infrastructure, and provides guidance for migrating to the cloud. |
+| Warning | It is used to convey the seriousness of the risk and the importance of taking necessary precautions to avoid harm. | If the remote file resource is used in more than one dataset, the other datasets are also affected by this command. |
+| Tip | A tip is a type of admonition in documentation that provides a helpful suggestion or best practice related to the content of the document. It is typically used to guide the reader towards a more efficient or effective way of using a product or service, or to provide additional insights or recommendations. | We have the suggestion option as well; click on the +icon and select the suggestion mapping. |
 |Success|Success admonitions are a type of documentation element used to highlight successful outcomes or positive results associated with a particular task, process, or feature|Graph is created successfully.|
 |Bug|A bug admonition include a description of the bug or issue, as well as steps that the user can take to avoid or work around the problem. It may also include information about when the bug will be fixed or patched, if applicable.|Users may experience issues with the file saving feature when running this software on Windows 10. To avoid data loss or corruption, be sure to save your work frequently and consider using an external backup device. Our development team is working to resolve this issue in the next software update.|
 |Example|The example admonition is typically used in instructional or educational documents to clarify complex concepts or demonstrate how to perform a specific task.|To create a new email account, click on the "Sign Up" button on the homepage and enter your name, email address, and desired password. Be sure to choose a strong password with a mix of uppercase and lowercase letters, numbers, and special characters. Once you have entered your information, click "Create Account" to complete the process.|
@@ -123,27 +123,27 @@ On this page is search function for icons available as well.
 <details>
   <summary>Extend section</summary>
 
--   do not use a cluttered desktop
--   do not show other esp. personal project artifacts then relevant for the tutorial / feature to show
--   select cropping area carefully (omit backgrounds, lines on the edges, etc.)
--   use the same or a similar area for similar screens
--   all relevant elements should be clearly visible and not be truncated
--   irrelevant elements / details should be omitted completely and not be half visible
--   crop scrollbars (they can make edges look unclean, especially if a scrollbar is directly on an edge)
--   keep an equal distance of all visible elements to the edges of the screenshot
+- do not use a cluttered desktop
+- do not show other esp. personal project artifacts then relevant for the tutorial / feature to show
+- select cropping area carefully (omit backgrounds, lines on the edges, etc.)
+- use the same or a similar area for similar screens
+- all relevant elements should be clearly visible and not be truncated
+- irrelevant elements / details should be omitted completely and not be half visible
+- crop scrollbars (they can make edges look unclean, especially if a scrollbar is directly on an edge)
+- keep an equal distance of all visible elements to the edges of the screenshot
 
 </details>
 
 ## Generated Content
 
 <details>
   <summary>The following files are generated from other sources and should not be changed:</summary>
-    
--   cmemc Command Reference: [docs/automate/cmemc-command-line-interface/command-reference](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/automate/cmemc-command-line-interface/command-reference)
+
+- cmemc Command Reference: [docs/automate/cmemc-command-line-interface/command-reference](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/automate/cmemc-command-line-interface/command-reference)
     - to update, start `task update:cmemc`
--   Coporate Memory Application Icons: [overrides/.icons/eccenca](https://github.com/eccenca/documentation.eccenca.com/tree/main/overrides/.icons/eccenca)
+- Coporate Memory Application Icons: [overrides/.icons/eccenca](https://github.com/eccenca/documentation.eccenca.com/tree/main/overrides/.icons/eccenca)
     - to update, start `task update:icons`
--   Shapes and Datatypes: [docs/explore-and-author/graph-exploration/building-a-customized-user-interface/node-shapes|property-shapes|datatype-reference](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/explore-and-author/graph-exploration/building-a-customized-user-interface/node-shapes)
+- Shapes and Datatypes: [docs/explore-and-author/graph-exploration/building-a-customized-user-interface/node-shapes|property-shapes|datatype-reference](https://github.com/eccenca/documentation.eccenca.com/tree/main/docs/explore-and-author/graph-exploration/building-a-customized-user-interface/node-shapes)
     - to update, start `task update:shape-reference`
 
 Where applicable, we added the following disclaimer: `<!-- This file was generated - DO NOT CHANGE IT MANUALLY -->`

README.md

@@ -4,10 +4,10 @@
 
 Shared repository of the eccenca Corporate Memory documentation.
 
-| Branch       | Deployment |
-| :---         | :--- |
-| `main`       | [https://dev.documentation.eccenca.com](https://dev.documentation.eccenca.com) |
-| `published`  | [https://documentation.eccenca.com](https://documentation.eccenca.com) |
+| Branch | Deployment |
+| :----- | :--------- |
+| `main` | [https://dev.documentation.eccenca.com](https://dev.documentation.eccenca.com) |
+| `published` | [https://documentation.eccenca.com](https://documentation.eccenca.com) |
 
 If you consider to contribute to this project, please have a look on [CONTRIBUTING.md](https://github.com/eccenca/documentation.eccenca.com/blob/main/CONTRIBUTING.md)
 
@@ -27,4 +27,3 @@ This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 Inter
 [mkdocs-shield]: https://img.shields.io/badge/Made%20with-mkdocs-brightgreen
 [mkdocs]: https://www.mkdocs.org/
 [markdown-shield]: https://img.shields.io/badge/Made%20with-Markdown-1f425f.svg
-

docs/automate/cmemc-command-line-interface/command-reference/admin/acl/index.md

@@ -13,22 +13,16 @@ List, create, delete and modify and review access conditions.
 
 With this command group, you can manage and inspect access conditions in eccenca Corporate Memory. Access conditions are identified by a URL. They grant access to knowledge graphs or actions to user or groups.
 
-
 ## admin acl list
 
 List access conditions.
 
 ```shell-session title="Usage"
-$ cmemc admin acl list [OPTIONS]
+cmemc admin acl list [OPTIONS]
 ```
 
-
-
-
 This command retrieves and lists all access conditions, which are manageable by the current account.
 
-
-
 ??? info "Options"
     ```text
 
@@ -42,18 +36,12 @@ This command retrieves and lists all access conditions, which are manageable by
 Inspect an access condition.
 
 ```shell-session title="Usage"
-$ cmemc admin acl inspect [OPTIONS] ACCESS_CONDITION_ID
+cmemc admin acl inspect [OPTIONS] ACCESS_CONDITION_ID
 ```
 
-
-
-
 !!! note
     access conditions can be listed by using the `acl list` command.
 
-
-
-
 ??? info "Options"
     ```text
 
@@ -65,12 +53,9 @@ $ cmemc admin acl inspect [OPTIONS] ACCESS_CONDITION_ID
 Create an access condition.
 
 ```shell-session title="Usage"
-$ cmemc admin acl create [OPTIONS]
+cmemc admin acl create [OPTIONS]
 ```
 
-
-
-
 With this command, new access conditions can be created.
 
 An access condition captures information about WHO gets access to WHAT. In order to specify WHO gets access, use the ``--user`` and / or ``--group`` options. In order to specify WHAT an account get access to, use the ``--read-graph``, ``--write-graph`` and ``--action`` options.`
@@ -82,14 +67,10 @@ A special case are dynamic access conditions, based on a SPARQL query: Here you
 !!! note
     Queries for dynamic access conditions are copied into the ACL, so changing the query in the query catalog does not change it in the access condition.
 
-
 ```shell-session title="Example"
-$ cmemc admin acl create --group local-users --write-graph https://example.org/
+cmemc admin acl create --group local-users --write-graph https://example.org/
 ```
 
-
-
-
 ??? info "Options"
     ```text
 
@@ -132,16 +113,11 @@ $ cmemc admin acl create --group local-users --write-graph https://example.org/
 Update an access condition.
 
 ```shell-session title="Usage"
-$ cmemc admin acl update [OPTIONS] ACCESS_CONDITION_ID
+cmemc admin acl update [OPTIONS] ACCESS_CONDITION_ID
 ```
 
-
-
-
 Given an access condition URL, you can change specific options to new values.
 
-
-
 ??? info "Options"
     ```text
 
@@ -180,20 +156,14 @@ Given an access condition URL, you can change specific options to new values.
 Delete access conditions.
 
 ```shell-session title="Usage"
-$ cmemc admin acl delete [OPTIONS] [ACCESS_CONDITION_IDS]...
+cmemc admin acl delete [OPTIONS] [ACCESS_CONDITION_IDS]...
 ```
 
-
-
-
 This command deletes existing access conditions from the account.
 
 !!! note
     Access conditions can be listed by using the `cmemc admin acs list` command.
 
-
-
-
 ??? info "Options"
     ```text
 
@@ -206,22 +176,16 @@ This command deletes existing access conditions from the account.
 Review grants for a given account.
 
 ```shell-session title="Usage"
-$ cmemc admin acl review [OPTIONS] USER
+cmemc admin acl review [OPTIONS] USER
 ```
 
-
-
-
 This command has two working modes: (1) You can review the access conditions of an actual account, (2) You can review the access conditions of an imaginary account with a set of freely added groups (what-if-scenario).
 
 The output of the command is a list of grants the account has based on your input and all access conditions loaded in the store. In addition to that, some metadata of the account is shown.
 
-
-
 ??? info "Options"
     ```text
 
     --raw         Outputs raw JSON.
     --group TEXT  Add groups to the review request (what-if-scenario).
     ```
-