As the SDPi standard has evolved, especially leveraging the rich metadata that is central to this profile standard, there is also an increasing degree of complexity in authoring the context, making maintenance and authoring more challenging and limiting those who can actively contribute.
Options should be explored for potentially refactoring the content so as to help reduce the inherent complexity while maintaining the technical elements of the specification.
One option is converting the current AsciiDoc-based specification to using "Typist". The rationale for this, from @d-gregorczyk is:
Typst, it is very similar to Asciidoc. What Asciidoc lacks, comes with Typst:
- fully specified
- tons of tutorials and modules
- default export to PDF and HTML, both fully customizable
- incremental builds with blazingly fast instant previews in editors such as VSCode and IntelliJ
- based on a script language that allows to specify Turing-complete functions (which means: one tools fits all, no AsciidoctorJ+Kotlin anymore)
As the SDPi standard has evolved, especially leveraging the rich metadata that is central to this profile standard, there is also an increasing degree of complexity in authoring the context, making maintenance and authoring more challenging and limiting those who can actively contribute.
Options should be explored for potentially refactoring the content so as to help reduce the inherent complexity while maintaining the technical elements of the specification.
One option is converting the current AsciiDoc-based specification to using "Typist". The rationale for this, from @d-gregorczyk is:
Typst, it is very similar to Asciidoc. What Asciidoc lacks, comes with Typst: