Convert AsciiDoc documentation to Markdown (#12389)

Convert AsciiDoc documentation to Markdown.

The former SE content is published under the top-level Modules and Guides sections. 

The configuration documentation generator now outputs Markdown instead of AsciiDoc, with simpler anchor handling for included pages. Generated configuration docs are checked in under `docs/config`, and CI regenerates them and fails if the checked-in output is out of date.

Aggregate Javadocs are generated by the dedicated `javadocs/pom.xml` module instead of `docs/pom.xml`.

Author: romain-grecourt

.github/ISSUE_TEMPLATE/1_bug.md

@@ -9,7 +9,6 @@ assignees: ''
 
 ## Environment Details
 * Helidon Version:
-* Helidon SE or Helidon MP
 * JDK version:
 * OS:
 
@@ -24,4 +23,3 @@ assignees: ''
 [//]: # "Step by step instructions to reproduce the problem"
 [//]: # "Provide sample code/application if relevant"
 
-

.github/workflows/validate.yml

@@ -163,6 +163,7 @@ jobs:
           artifact-path: |
             **/target/state-javadoc.xml
             **/target/*-javadoc.jar
+            javadocs/target/*.jar
           run: |
             mvn ${MVN_ARGS} -T8 \
               -Dorg.slf4j.simpleLogger.showThreadName=true \
@@ -191,8 +192,19 @@ jobs:
             mvn ${MVN_ARGS} \
               -Dcache.recordSuffix=docs \
               -f docs/pom.xml \
-              -Pjavadoc \
               install
+      - name: Verify generated configuration documentation
+        shell: bash
+        run: |
+          changes="$(git status --porcelain=v1 --untracked-files=all -- docs/config)"
+          if [[ -n "${changes}" ]]; then
+            echo "${changes}"
+            git diff -- docs/config
+            echo "::error::Generated configuration documentation is out of date."
+            echo "Regenerate with:"
+            echo "  mvn -f docs/pom.xml generate-sources"
+            exit 1
+          fi
   examples:
     needs: build
     timeout-minutes: 30

.gitignore

@@ -53,9 +53,6 @@ nb-configuration.xml
 .classpath
 .factorypath
 
-# Asciidoctor
-.asciidoctor/
-
 # Vim
 *.swp
 
@@ -83,7 +80,7 @@ ObjectStore/
 PutObjectStoreDirHere/
 package-lock.json
 RUNTIMEDB/
-docs/se/config/images
+docs/modules/config/images
 .helidon-oidc-secret
 .helidon-oidc-secret.*.tmp
 

.mvn/cache-config.xml

@@ -21,7 +21,7 @@
     <lifecycleConfig>
         <project path="docs/pom.xml">
             <projectFilesExcludes>
-                <exclude>src/main/asciidoc/config/*</exclude>
+                <exclude>config/*</exclude>
             </projectFilesExcludes>
         </project>
         <project glob="**/*">

CONTRIBUTING.md

@@ -14,10 +14,10 @@ When filing a bug remember that the better written the bug is, the more likely i
 to be fixed. Please include:
 
 1. Version of Helidon
-2. Whether you are writing a Helidon SE or MP application
-3. OS
-4. Version of Docker or Kubernetes or other software if it's relevant to your issue
-5. Steps to reproduce
+2. OS
+3. Version of Docker or Kubernetes or other software if it's relevant to your
+   issue
+4. Steps to reproduce
 
 ## Contributing Code
 
@@ -41,4 +41,3 @@ first.
 Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If
 you'd like more specific guidelines see the
 [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
-

DEV-GUIDELINES.md

@@ -337,7 +337,7 @@ be used by users to [bom/pom.xml](bom/pom.xml).
 
 - <a id="rule-11-6-1"></a>**Rule 11.6.1.** Avoid bundling third-party dependencies that may add unexpected libraries,
   such as the Google Login provider.
-- <a id="rule-11-6-2"></a>**Rule 11.6.2.** Put SE bundles under `bundles/` with group ID `io.helidon.bundles`.
+- <a id="rule-11-6-2"></a>**Rule 11.6.2.** Put Helidon bundles under `bundles/` with group ID `io.helidon.bundles`.
 - <a id="rule-11-6-3"></a>**Rule 11.6.3.** Keep bundle directories scoped to active Helidon bundle families.
 - <a id="rule-11-6-4"></a>**Rule 11.6.4.** Bundles are for end users, not internal use.