Config Doc: use HTML tables to be able to output markdown inside cells

[Athou]

This fixes this comment by @gsmet

Sample output of allConfig.qute.md for CommaFeed: https://gist.github.com/Athou/18d9ab535a4d7bebd74d916c4b023407

I think io.quarkus.maven.config.doc.generator.MarkdownFormatter#escapeCellContent may need to be updated to escape HTML to avoid breaking the table cells, but I'm not sure what's the best way to do that.

[gsmet]

Looks good. I wonder if you should avoid centering Configuration property and the section name?

Maybe you could use something similar to what I did for Asciidoc and add a number of unbreakable spaces in front of the sections depending on the level? For your simple example, it would just be left aligned but if it goes deeper, they would be indented a bit?

As for escaping HTML, the Javadoc will potentially come as HTML so you can't really do that.

[gsmet]

I added a few suggestions and a question.

[github-actions]

🎊 PR Preview 155093d has been successfully built and deployed to https://quarkus-pr-main-43225-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[Athou]

I wonder if you should avoid centering Configuration property and the section name?

Maybe you could use something similar to what I did for Asciidoc and add a number of unbreakable spaces in front of the sections depending on the level? For your simple example, it would just be left aligned but if it goes deeper, they would be indented a bit?

Done! I updated the gist with the new output (I have nested configuration items, see Database cleanup settings that is a child of Database settings)

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 63b38d0.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

You can consult the Develocity build scans.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 63b38d0.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[gsmet]

Looks really good. Let's drop the new line replacement and it's good to go!

[gsmet]

Nice update, thanks!