As it stands I add a "Saved" text, next to the submit button.
Should probably, use a toast, or just make that message prettier.

I'm a bit conflicted. Adonis is fantastic, but I have two issues:

1. I keep replacing its default, out-of-the-box tools. (Validator, ORM), so I'm debating if it's worth keeping it around. The alternative would be to pull this functionality in Remix
2. Sharing types is a pain. I'm working on a api-contract package, so that I can share some types, but it feels odd. If I was using Graphql, then I could have type-generation. There's also the OpenAPI approach, but I don't like it.

A new version will land soon, so I have to either upgrade and commit or move ahead and remove it.

• Introduce Dockerfile for deployment
• Introduce docker-compose.yml for local develoment

• Split logic to Domain (business) & Entity (persistence)
• Use Ports and Adapters instead of direct ORM use

Stack:

• Remix
• TypeScript
• RadixUI
• TailwindCSS

The current implementation uses my-app.com/teams/team-id. I would rather have team-id.my-app.com.

Remix makes this a bit tricky from what I've seen in discussion, while Next.js has first class handing for that.

Adonis v6 will replace it either way, go all in on the fp-ts/effect-ts ecosystem

• https://www.jacobparis.com/content/remix-rpc-pattern

Loaders fetch normally in the routes that we have. The benefit is that we will never have an action that handles multiple forms.
One caveat is that the route won't reload, as we submit to another, and we might have stale data.

• Log on dev
• Mock on tests
• Pass through effect context

The design is rushed, I can take inspiration from here https://www.untitledui.com/components#application-components

Parse FormData with zod, as we currently have no typing in place.