D11What it costs the developer
You are fluent in Go. Then you open the React project.
Nobody funds a frontend developer for an internal admin panel. So you learn just enough React to build screens you are not proud of, slowly, on every project.
What actually goes wrong
The backend is the part you are good at and the part the client cannot see. The admin panel is the part they judge the work by, and it is built by whoever is left.
The result is screens that work and look like they were built under protest, and a developer who spent a third of the project not doing what they are best at.
What Grit does about it
- The admin panel is generated, dark-themed and consistent across every resource, from the same description that produced the API.
- Customising a screen is editing one TypeScript file that is never regenerated, so you change what you care about rather than building from scratch.
- The generated hooks are available to any page you write yourself, typed from the Go model.
The commands
grit generate resource Invoice --fields "number:string, total:money"
The screen, as a file you own
# apps/admin/app/_dashboard/resources/invoices/index.tsx
What it does not do
It is an operator interface and it is opinionated. Reskinning it entirely is a real project, and you will be merging your changes against upgrades afterwards.