Community projects

Read how other projects connect Fullbleed to their own applications. The links below point to public source inspected on November 1, 2026, including each project's dependency declaration and rendering code.

These projects are maintained by their respective authors. Source integration does not establish production deployment, an endorsement, or compatibility with the latest Fullbleed release. Follow each project's own setup, license, and support information; these integrations are not part of Fullbleed's release tests.

PDF generation in Betty Blocks

Betty Blocks' native WebAssembly components include a Generate PDF action. It applies variables to a Liquid template, renders the resulting HTML inside the component, and stores the PDF in a model's file property.

The integration prepares linked stylesheets, images, and fonts before calling Fullbleed. Resource fetching belongs to that application layer; the rendering engine itself does not fetch those URLs.

• Action documentation
• HTML preparation and PDF rendering
• Fullbleed dependency

Binary-analysis reports in RBAT

RBAT is a binary-analysis tool with a PDF report exporter. Its report module puts analysis results into an Askama HTML template and passes the HTML and report CSS to Fullbleed. It also preserves an HTML fallback when PDF rendering fails.

• Report exporter
• CLI dependencies

Dataset documentation in Davis

Davis uses Fullbleed for English and Japanese schema-document PDFs. Its document crate registers bundled Inter and Japanese fonts, shares an engine through OnceLock, and writes PDF files only when their bytes change. The source includes a repeated-output test.

• Schema-document generator
• Workspace dependency declaration

Ruby bindings

mitsuru/fullbleed-ruby wraps the Rust engine as a Ruby native extension using Magnus. Its rendering methods call Fullbleed to produce PDF bytes or write a PDF file.

This is an independent binding, separate from the packages maintained in the Fullbleed organization. Its RubyGems installation instructions have an open clarification request. Check that issue for installation status before following the wrapper's README.

• Ruby API documentation
• Native rendering bridge
• Engine dependency

Build your integration

Start with a tested Rust example, web-framework starter, or n8n invoice workflow. Keep template processing, resource retrieval, and application storage in your application; provide the engine with explicit HTML, CSS, and assets.

To share a public integration or correct a listing, use Fullbleed Discussions. Include its repository and the document workflow it supports.