{"title":"Meet Amber: The Framework Has a Face","summary":"The new site gives Amber a playful face, a clearer job, and a public application that demonstrates the framework's own V2 web path.","date":"2026-08-11","category":"Website","author":"Seth Tucker","url":"https://amberframework.org/blog/2026/08/11/meet-amber-and-the-new-website","markdown_url":"https://amberframework.org/blog/2026/08/11/meet-amber-and-the-new-website.md","json_url":"https://amberframework.org/blog/2026/08/11/meet-amber-and-the-new-website.json","image_url":"https://amberframework.org/assets/blog/amber-new-website-character-2026-105d6ec8ff96d333dacbc76acd5563db.webp","content_markdown":"# Meet Amber: the framework has a face\n\nAmber has had a crystal for a long time. With the new website, the framework\nalso has a face.\n\nThe character Amber is both our mascot and a personification of the framework\nitself. She gives a memorable identity to a fairly practical set of\nresponsibilities: routing, controllers, ECR views, configuration, schemas,\nWebSockets, jobs, and the structure that connects an application. When the site\nsays “Amber owns the web application,” that is the boundary we mean.\n\nAmber is not a fictional maintainer, a spokesperson who approved a claim, or a\nsubstitute for the people doing the work. She is a visual and teaching tool. A\nnew developer should be able to recognize who owns a concern before learning\nevery package name in the ecosystem.\n\n## The original studio, on purpose\n\nThe new art returns to Amber's playful original-studio style: open expression,\nwarm blush accents, rounded shapes, and a little bit of mischief. The framework\nis serious about performance and correctness. Its mascot does not need to look\nstern to communicate that.\n\nGrant and Gemma use the same idea to name adjacent responsibilities. Grant\norganizes relational records. Gemma handles files and attachments. Their pages\nalso state when an integration is supported, preview, or still ahead, so the\ncharacters make software boundaries clearer rather than hiding them.\n\n## The website is an Amber V2 application\n\nThis site is part of the product demonstration. It uses Amber controllers and\nECR views, local CSS, browser-native modules, an import map, Markdown-backed\ndocumentation, JSON representations for tools, RSS for people, and an Amber\nWebSocket channel. There is no front-end framework or bundler behind the\nexperience.\n\nThat matters because a framework website should show the development style it\nrecommends. The examples in Amber's Way are not an imaginary showcase; they\ndescribe how this public application is organized.\n\nThe same standard now applies to the claims around it. Release status has a\ndate and a source. Performance numbers lead to a human-readable method before\nthe raw data. Preview features are named separately from the release-gated web\npath. Migration guidance starts with the smallest honest change and then calls\nout the few boundaries that need more care.\n\n## A warmer invitation to build\n\nAmber V2 is an invitation to test a clearer web path, not a declaration that\nevery idea is finished. The web framework core is the thing being\nrelease-gated. The supported generated application now includes Grant\npersistence and manifest-backed CSS, JavaScript, images, and fonts. Gemma file\nattachments, generated authentication, and native applications keep separate\npreview boundaries without making an ordinary ECR application feel\nprovisional.\n\nSo: meet Amber. Then install the CLI, build something useful, and tell the real\nmaintainers where the path still gets in your way.\n\n- [Start the Amber V2 web path](/docs/v2/getting-started/installation)\n- [See current releases and dates](/releases)\n- [Read Amber's Way](/amber-way)\n- [Meet the whole crew](/characters)\n"}