What's New in Peter Richards' Liferay Fragments Repository: 2026 LTS, a Visual Gallery, and Drop-and-Go Deploys

This is LR Tools’ rewrite of an update by Peter Richards on Liferay.dev, following up on his earlier post about scaling Liferay fragments with AI and automation. This one covers what’s changed in his open-source Liferay Fragments repository since then — the short version: it’s moved from a personal lab of experiments toward something meant to be dropped into a real project.

From personal collection to something production-ready

The repository started as a place to collect fragments the author had built for his own projects. The update covers four changes aimed specifically at making it usable by other teams, not just browsable:

Verified against 2026 LTS. Every fragment in the repo has been checked against the current LTS release, rather than assuming whatever version they were originally built for still behaves the same way.

A built-in visual gallery. Instead of reading through fragment names and code to guess what something looks like, there’s now a gallery for browsing components visually before importing anything — useful for quickly finding the right fragment for a demo or a proof of concept without trial-and-error importing.

Version-specific packaged releases. Fragments are now packaged per DXP version, so teams on an older supported release aren’t stuck adapting fragments built and tested against the newest one.

A drop-and-go zip deployment workflow. Fragments can now be deployed via a straightforward zip-based process rather than a more involved setup — matching the repo’s overall goal of getting a fragment from “found in the gallery” to “running in your site” as quickly as possible.

A few examples worth knowing about

The update highlights three fragments in particular as a sense of what’s in the collection: an automated meter-reading input utility, a dynamic badge overlay built for Commerce, and a set of collection-based date display components. None of these are exotic — they’re the kind of small, reusable UI pieces that are easy to justify building from scratch each time, which is exactly the case for pulling from a shared, version-verified library instead.

Contributing

The repository is explicitly open to outside contributions — pull requests and feature suggestions both — so if you build something reusable on top of it, or hit a gap, that’s the intended path back into the project rather than a one-off fork.

This article is LR Tools’ rewrite of the original post by Peter Richards — read it on Liferay.dev for the author’s own framing, or browse the repository directly on GitHub.