EuroPDF

@europdf.eu

Create PDFs from HTML securely and at scale. Powered by the industry-leading PrinceXML engine, 100% hosted and operated in the EU. https://www.europdf.eu

Revision 684: Ecosystem Performance (@e18e.dev) workingdraft.de/684/ mit @thealexlichter.com und Ulrich-Matthias „Ulima“ Schäfer. Diese Revision wird gesponsert von @europdf.eu ✨ , eurem SaaS zur Erzeugung hochwertiger, barrierefreier PDFs mit Hilfe modernem HTML/CSS/JS – und mit Sitz in der EU 🇪🇺

Revision 684: Ecosystem Performance (e18e) | Working Draft

Diese Revision plaudern wir mit Alexander Lichter (LinkedIn / Mastodon) und Ulrich-Matthias „Ulima“ Schäfer (LinkedIn) über Ecosystem Performance, kurz „e18e“: Warum es sich lohnt, das JavaScript-Ökos...

workingdraft.de

Just launched: Document request timelines! Now you can see the complete lifecycle of your PDFs: Processing steps, callback results, and confirmation of when document data has been permanently removed (“incinerated”) from our servers.

Screenshot of the new timeline feature, showing a sequence of timestamped events for a PDF document, including “requested,” “created,” “callback request failed with status 500”, and “incinerated”.

Quick heads up: It’ll soon be possible to include a ZIP file in your API request containing all the required assets! This feature is already in beta, and we plan to release it in about 4 weeks.

When you discover that your logo also makes nice Xmas decorations (still playing around with sizes and colours). 🎄⭐️🌟

Photo of a handful of 3d printed stars from the EuroPDF logo, in different sizes, two colour prints, mostly yellow on blue, some black on white.

We’re mainly here to answer questions, but here’s a brief pitch nonetheless: Need to create a lot of PDFs? Like invoices or status reports? Sure, you can use a low-level library like FPDF or Prawn, or run a headless browser and “print as PDF“. Or just save yourself the hassle and use europdf.eu 😎