What shipped, why it matters, and where to investigate next.
Product updates, architecture milestones, and release notes presented like an operational timeline instead of a blog feed. Scan the latest themes, open the relevant entry, then jump into docs or the product.
Current shipping themes
May 17
Docs and blog now ship from the web app
Callra now publishes its public docs and editorial blog from the same Next.js app, using the Fumadocs MDX pipeline for navigation, rendering, and metadata.
May 17
Web app branding refresh lands across public pages
The public-facing web app metadata and navigation now present the project as Callra, aligning the product copy with the monorepo and docs naming.
May 17
Analytics core and speed insights split into workspace packages
Shared analytics logic now lives in dedicated workspace packages, making the web app, ingest service, and future runtimes easier to evolve without duplicating contract logic.
Filter by topic to inspect the latest work stream, then open docs or blog only when you need a deeper implementation note.
2026
May 17
Why it matters
Callra now publishes its public docs and editorial blog from the same Next.js app, using the Fumadocs MDX pipeline for navigation, rendering, and metadata.
2026
May 17
Why it matters
The public-facing web app metadata and navigation now present the project as Callra, aligning the product copy with the monorepo and docs naming.
2026
May 17
Why it matters
Shared analytics logic now lives in dedicated workspace packages, making the web app, ingest service, and future runtimes easier to evolve without duplicating contract logic.
2026
May 16
Why it matters
The ingest service now uses updated analytics endpoint and response handling so batch flushes stay aligned with the current API behavior.
2026
May 16
Why it matters
The project moved into a workspace layout with a dedicated web app, ingest service, and shared schemas package so analytics contracts can evolve in one place.
2026
May 16
Why it matters
Callra can now ship the public web product through OpenNext and Wrangler, giving the app a production path that keeps the web surface lightweight.