Thank the authors for their wonderful job at first! I really appreciate this extension and like it quite a lot. I am using it heavily to write docs. At the same time, I found the available documentation is a bit limited.

While I am trying to define my own style.css, I found that the documentation in this page only give s

At the top of your C4 PlantUML .puml file

What need to be done, to understand Getting Started section? I have no idea, what is your C4 PlantUML .puml file)

I could create it and fill it with example code, but the next question is: how to transpile .puml file to .svg file?

When using an inter-document cross reference, such as this:
<<SOME_ADOC.adoc#, Some Adoc>>
The link in the preview as well as browser does not point to the .adoc file, but changes the link to point to a .html file. This file is of course not present because the html has not been generated yet, when everything is still in adoc format.
For previewing inter-document links (to .adoc files), the g

Currently, the README.md file lists all tables with their full table comment.

I'm putting a lot of info in some of my table descriptions, including SQL code blocks. These render rather badly in the comment column of the central Tables table, which treats markdown just a little different.

Perhaps the Tables table should only use the first paragraph of each table description.

E.g.

Currently we are using unittest (from the stdlib) but the integration is far from perfect. Maybe https://docs.pytest.org/en/latest/ will be a better choice.

I think there is a bug with highlighting. Error E363 happens when 35 or more dashes ('-') are in continuation. I use those in comments when I want to delimit sections of the document.

I don't know enough about syntax files, but I guess it should be an easy fix for someone who understands them.

Expected Behavior

Each class should have it's own unit test

Actual Behavior

Not every class has it's own unit test

Steps to Reproduce the Problem

1. Look at the sources in src/main/java
2. Look for the same source file in src/test/java with Test appended to its name

Specifications

• n/a

Repositories typically have a top-level README file that explains what the project is about and how to get started using it. I think it would be helpful to re-use that file when generating the documentation using c4builder:

/README.md       # for website generation, use this as the start page (and assume it has a link to e.g. `doc/all-in-one.md`); for pdf, use this as the intro section