Open AndreaLaGrotteria opened 1 day ago
We can also keep the old macros and translate them before passing the file to asciidoctor. This would essentially be the same as what we do with the source:
, which is just translated into an include (in contrast with common:
which imports the file directly)
If you are willing to da PR which updates every guide to this, I am happy to accept it.
In guides-core use asciidoc built-in include system instead of custom macros solution.
common
would become
external-template
external-template:micronaut-k8s-oci/k8s-microservice.adoc[arg0=users]
would becomefor guides that were using the syntax {arg0:U} to make argument uppercase, the macro would become
callout
would become
the explicit numeration is not needed since asciidoc does that automatically.
We would need to update the guide asciidoc of the included files where {arg0:U} is present to replace it with {arg0Upper} and every callout, adding <.> at the begging of the line.