Thanks for your kind words.

Would you be able to expand on what you mean by “report generation libraries”?

For example, I am building (in Common Lisp, but it’s trivial and can be done in any software) a tool to read content from a database and auto generate the HTML markup for producing pdf reports. This allows me to reuse content across reports and also leverage the full power of databases (text search in particular). As another example, I have many monthly financial metrics - I will store these in a database then use my lisp markup tool to generate the necessary HTML to produce the pdf report (via paged.js).

In addition, one can use headless chrome to automate the full workflow so that the reports are generated directly from your program and not via File > Print in your browser.

Was that what you were thinking of?

You can also add charts via charts.js.

The beauty of paged.js is that you can leverage many of the features of browsers and JavaScript libraries in your report generation.

I wasn’t able to get syntax highlighting for code blocks to work however, need to dig into that a bit more.

> Was that what you were thinking of?

Yes! This is great. Thanks for the pointers. I'll look into that.

I've built a python library called ZipReport to manage and generate PDF reports from HTML using paged.js - https://github.com/zipreport

The actual PDF generation component is an electron application, so it may fit your "frontend technology" requirement.

I started generating PDF before pagedjs and use my own electron based solution. Search for schild.report on github to see how it works. Basically reports are created via svelte templates and then printed via the electron print api. Works extremely well.

Yup. I use pagedown all the time.

https://pagedown.rbind.io/

In case you missed it, pagedown implements pagedjs afaik