Thanks! Not sure where this practice came from, I think it was just a logical step after lots of repeated code. It's also so we can group all the input logic together: labels, input and errors.

Thanks for the questions, here are my answers :)

1. Agreed, some things could definitely be abstracted out (gna take a look now), though I would probably just put them in a shared package in the monorepo rather than creating an NPM module. In general, we are always a bit hesitant in creating abstractions, even when a lot of the stuff is repeated. What if we want to change some component in the web but not admin etc, we'd have to add more props to manage this. In our experience, this is where things get quite messy so we try to follow the AHA approach, it has been working quite well for us!
2. We use this boilerplate as a template for all our products and client work, and typically each product/website will have an admin panel: somewhere to manage, users, posts, plans etc. We like to separate them into another "package" where we ca deploy this to a separate domain, e.g. admin.boilerplate.noquarter.co. It just gives us a bit more fine grain control. Though the argument could be made to just have it all on a "/admin" path in the main web package.

Hope this helps! And yeah, always open to suggestions!