Florilegium
kevinraymond/florilegiumReviewed by AI
What it does
florilegium is a package for LuaLaTeX documents. It draws Delft-blue flower margins where every petal, leaf and stem is computed while the page is being typeset, so each page gets its own garden and the same page always comes out the same. The margin can react to the text: a decorated first letter, a flower beside a heading or wherever you ask, and a garden that ages from spring to autumn across the document. One colour setting changes the whole palette. There is also a pure PostScript version for Ghostscript or a printer.
How easy it is to install
C · install 1 or 2 tools · Web
- Windows D
- macOS D
- Linux D
- Web C
The easiest route is the browser: the README says you can paste florilegium.sty, the six .lua files and one .tex file into an Overleaf project and set the compiler to LuaLaTeX. On your own computer you need a LaTeX distribution with LuaLaTeX plus make and a terminal (or build the provided Docker image), and the animations and gallery images additionally need ffmpeg, Python with Pillow, pdftoppm or Ghostscript.
Numbers on GitHub
- Stars
- 1,158on Oct 31, 2026
- Downloads
- 111all releases
- Growth
- +1,158stars in 1 day
Stars over time
History starts on Oct 31, 2026.
Facts
- Runs on
- Windows, macOS, Linux, Web
- You need to install
- Other tools, FFmpeg
- To build from source
- FFmpeg
- Disk space
- not determined
- Accounts or keys
- None
- Cost
- Free · Free and open source under MIT.
- License
- MIT (Permissive)
- Last update
- Oct 31, 2026
Risk signals (2)
- Infobrand new project
GitHub facts: created 2026-10-30, with both releases (v1.0 and v1.1) tagged that same day. There is no track record yet of it working across TeX distributions.
AI review
- Infoauthored layout tuned for one page size
README.md table: the authored composition "adapts to" "nothing (tuned for A4, 68 mm margin)", while only the grown one adapts to the page layout. On other paper sizes the hand-placed version may not fit.
AI review
Evidence is shown in its original language.
What Radar could not check
- Whether it compiles without changes in your own TeX distribution and version.
- The real time and memory per page on your machine, beyond the author's "about a second a page".
- How it behaves with page sizes, margins and document classes other than the ones it was tuned for.
- Whether a given printer handles the PostScript version, which the README says falls back to opaque colours.