Amber has had a crystal for a long time. With the new website, the framework also has a face.
The character Amber is both our mascot and a personification of the framework itself. She gives a memorable identity to a fairly practical set of responsibilities: routing, controllers, ECR views, configuration, schemas, WebSockets, jobs, and the structure that connects an application. When the site says “Amber owns the web application,” that is the boundary we mean.
Amber is not a fictional maintainer, a spokesperson who approved a claim, or a substitute for the people doing the work. She is a visual and teaching tool. A new developer should be able to recognize who owns a concern before learning every package name in the ecosystem.
The original studio, on purpose
The new art returns to Amber's playful original-studio style: open expression, warm blush accents, rounded shapes, and a little bit of mischief. The framework is serious about performance and correctness. Its mascot does not need to look stern to communicate that.
Grant and Gemma use the same idea to name adjacent responsibilities. Grant organizes relational records. Gemma handles files and attachments. Their pages also state when an integration is supported, preview, or still ahead, so the characters make software boundaries clearer rather than hiding them.
The website is an Amber V2 application
This site is part of the product demonstration. It uses Amber controllers and ECR views, local CSS, browser-native modules, an import map, Markdown-backed documentation, JSON representations for tools, RSS for people, and an Amber WebSocket channel. There is no front-end framework or bundler behind the experience.
That matters because a framework website should show the development style it recommends. The examples in Amber's Way are not an imaginary showcase; they describe how this public application is organized.
The same standard now applies to the claims around it. Release status has a date and a source. Performance numbers lead to a human-readable method before the raw data. Preview features are named separately from the release-gated web path. Migration guidance starts with the smallest honest change and then calls out the few boundaries that need more care.
A warmer invitation to build
Amber V2 is an invitation to test a clearer web path, not a declaration that every idea is finished. The web framework core is the thing being release-gated. The supported generated application now includes Grant persistence and manifest-backed CSS, JavaScript, images, and fonts. Gemma file attachments, generated authentication, and native applications keep separate preview boundaries without making an ordinary ECR application feel provisional.
So: meet Amber. Then install the CLI, build something useful, and tell the real maintainers where the path still gets in your way.