Seek adventure.

Help us prove the
whole journey.

Our release contract is a promise: each release should give you compatible versions, documentation you can follow, tutorials that work, and guidance your agent can use.

We've already exercised the supported web app, packages, guides, and public website together for beta.5. Now we're testing that experience with real apps and connecting the remaining pieces.

1. Start: install the released tools and build a working web app.
2. Learn: follow a tutorial and ask your agent to make a change you can inspect.
3. Update: try the next beta when it arrives and check that your app, guides, and agent context still agree.
4. Report: share a mismatch, a missing step, or a successful journey, with your versions.

Use your own app as the test. A small app and a clear report are enough to participate.

What will
you build?

A portal for your customers. An inventory app for your team. A service desk that keeps work moving. Pick a starting idea and make it yours.

We're building a small collection of business templates around patterns we can explain and test. Each recommendation should come with a working example, a migration guide, and a published operating range you can choose in advance.

These are app invitations. Packaged business templates and their measured capacity profiles are being prepared.

Selecting an idea adds it to the request you give your coding assistant.

Start with your agent.
Bring your own idea.

Contributions require a coding assistant. You decide what your app should do and accept the result. Your assistant inspects the project, makes changes, runs checks, and prepares the evidence.

The first checkpoint is small: one working page, a record you can create and edit, and a restart that keeps your data.

Your starting request

Help me build a web app with Amber V2. Read the current beta installation and support guides at https://amberframework.org/docs/v2. Use the read-only documentation MCP at https://amberframework.org/mcp and the available Minecart/Shards Alpha agent guides. Verify the framework, CLI, crystal-alpha, and dependency versions and hashes. Explain the supported path and any preview features we choose. Help me get one page working, create and edit a record, restart the app to verify persistence, and make one change I can inspect. I own the app's intent and acceptance.

My app idea: [describe what you want to build]

For a discovery or contribution, inspect the relevant repository and existing issues at https://github.com/amberframework/amber/issues. Reproduce the behavior, record exact versions and evidence, and prepare an issue proposal before a linked PR. Review my evidence with me; I approve scope and submission.

Paste this into your coding assistant and add your app idea. Work with the project on GitHub; join Discord when you want to talk with the community.

Tell us what
you discover.

A smooth first install? Confusing setup? A missing example? An update that needs a clearer guide? Bring those discoveries to GitHub.

Use your coding assistant to inspect the repository and existing issues, reproduce the behavior, and prepare a proposal with your versions and evidence.

Start with an issue.

Review the evidence, then open or join a GitHub issue. Describe what you wanted, what happened, and how to reproduce it. Maintainers agree on direction before a linked PR.

Proposals, reports, decisions, and follow-up stay with the project.

Your app could inspire
the next pioneer.

Share what you built and what you learned in a GitHub issue. Your coding assistant can help prepare the story and public project link.

We're proposing a pioneer showcase on the projects page: your app, your story, and credit to you. Maintainers confirm your permission and agreed credit in the issue before publication.

Proposed showcase program · Maintainer review and your permission required.

Talk on Discord.

Ask questions, compare notes, and meet people building with Amber. Discord is the place for conversation with the community.

When a conversation leads to a contribution, bring the proposal and evidence back to GitHub with your coding assistant.