Lossless Changelog
product

Project Scaffold Summary — cilantro-site

Multi-product marketing and changelog platform built with Astro 5 + SSR + Tailwind 4 — home to the Neo AI assistant landing, a changelog architecture that aggregates multiple products, and a Twenty CRM newsletter integration.

Michael StatonMusic Editoraugmented with Claude Code on Claude Sonnet 4.6

Project Scaffold Summary — cilantro-site

Why Care?

Cilantro-site is the marketing and product-showcase platform for the Cilantro brand — a multi-product organization whose public presence spans three products (Cilantro-Site itself, Neo, and Parslee). The site is built to be as multi-product as the team behind it, with a live changelog system fed by separate product-specific content sub-collections.

This entry initializes the root-level changelog/ convention for the repo. The site already ships its own internal changelog rendered through Astro content collections at src/content/changelogs/ — this directory is the parallel, convention-level log for the repo itself (infrastructure, dependency changes, architecture decisions), written for the Lossless Group changelog aggregation system.

What's New? (as of 2026-07-06)

  • Multi-product changelog system — src/content/changelogs/ aggregates three product-specific changelog submodule collections: changelog-cilantro-site, changelog-neo, changelog-parslee. Displayed at /changelog with an RSS feed.

  • SSR via @astrojs/node — the site runs in server-side rendering mode, enabling API routes.

  • Twenty CRM newsletter integration — newsletter signups at /api/newsletter feed directly into a Twenty CRM instance.

  • Design system page at /design-system — the canonical component and token reference for the site.

  • Formalities pages at /formalities — privacy policy, terms, legal.

  • Jam with pages at /jam-with — collaboration / contact surfaces.

  • Changelog preview on the homepage — the index surfaces the three most recent changelog entries from the collection.

Architecture Notes

The site uses a two-tier changelog architecture:

  1. src/content/changelogs/ (internal, rendered) — Astro content collections for each product, displayed at /changelog. These entries document product features and are written for end users.

  2. changelog/ (root-level, this directory) — Lossless convention log for repo-level work (infrastructure, deps, architecture). Feeds into the cross-repo Lossless changelog aggregation. These entries are written for the team and open-source audience.

Both serve different audiences and neither replaces the other.

What's Next

  • Upgrade from Astro 5 → 7 (currently on ^5.14.1)

  • Add root-level context-v/ directory to match the pseudomonorepo convention

  • Connect the root-level changelog to the Lossless changelog aggregation feed