Add PDF Export Automation to SDPi Publication

[ToddCooper]

Some organizations that want to reference and utilize the SDPi specifications prefer PDF documents, in addition to other forms such as HTML.

Request is to include export of the final HTML publication into a PDF rendering, as part of the Github automation process or the release / publication package process. Also, to include the PDF in the profiles.ihe.net/DEV publication page.

[d-gregorczyk]

Difficult... we could potentially tweak the print view of the spec and manually export a PDF as part of the publication process.

[ToddCooper]

SDPi Friday Review 2023.10.27 Not simple but will try to find a tool to automate the PDF conversion. This may require some tweaks to the HTML output.

Note: Some of the IHE ITI HTML profiles are also exported as PDF.

[JavierEspina]

I see 2 options to investigate:

1. Set the build pipeline to convert straight from ASCIIDOC to PDF (instead of ASCIIDOC->HTML->PDF)
2. Manually convert the HTML to PDF with every release using the browser's print function (I think this is what David proposed above)

If option 1 is feasible with reasonable effort it would be my preference.

On 1:
I think the asciidoctorj plugin supports building PDF instead of HTML. It may be as simple as replacing "html" with "pdf" in

Run gradle/gradle-build-action@v[2]
with:
arguments: run --args="--input-file ../../asciidoc/sdpi-supplement.adoc --output-folder ../../sdpi-supplement --github-token *** --backend html"

On 2: I tried it out and it looks pretty decent. Not sure if sufficiently similar to the HTML though. Here is the result for your assessment:
Service-oriented Device Point-of-care Interoperability (SDPi) Technical Framework.pdf

[ToddCooper]

Well ... that DEFINITELY looks pretty good!!!

[ToddCooper]

SDPi Friday 2024.02.09 - Investigate creating a Github action that is able to simulate the HTML output and print it to PDF.