The retro asset library

The asset library is a curated, rights-cleared collection of retro web media — animated GIFs, tiled backgrounds, dividers, cursors, and 88×31 buttons — you can drop straight into a site. It's the fast way to decorate a page without hunting the web for the right "Under Construction" sign.

Using the library (for site owners)

1. Open a file in the studio (the in-browser editor).
2. Click Assets in the toolbar to open the picker.
3. Browse by category or search by name/tag.
4. Click an asset to place it. The file is copied into your site (under library/) and a reference is inserted at your cursor — an <img> tag in HTML, or a url('…') in a stylesheet.

Quota

Browsing and selecting are free. An asset only counts against your storage quota when it's placed on a site. Placing the same asset more than once on one site is charged once (it reuses the same file). Deleting the placed file from your site releases the quota again.

What you can rely on

Every library asset is static raster media (GIF, PNG, JPEG, WebP, AVIF, BMP, ICO) — never SVG, HTML, or anything that can run code. Assets are served with an image content type and X-Content-Type-Options: nosniff, so they render as pictures and can never execute. This is enforced both by the catalogue (which rejects non-raster files) and by a CI test over the shipped pack.

Contributing assets (for instance maintainers)

Asset files live in the repository under library/<category>/. The bundled pack is seeded from database/seeders/data/asset-pack.json via php artisan db:seed --class=LibraryAssetSeeder (idempotent).

Requirements for a contributed asset:

• Static raster only — one of: gif, png, jpg/jpeg, webp, avif, bmp, ico. No SVG/HTML/scripts. The CI static-only test fails the build otherwise.
• License + attribution are mandatory. Only contribute media you have the right to redistribute — public-domain/CC0 or appropriately licensed — and record the license (e.g. CC0-1.0) and a human-readable credit.
• Category — one of gifs, backgrounds, dividers, cursors, buttons.

Admins can also create and manage assets through Admin → Assets in the Console; the source_path there is confined to the configured asset root and must point at an allowlisted raster file. License and attribution are required.

The shipped starter pack is intentionally simple, CC0 placeholder art — replace or extend it with your own curated, rights-cleared media.