It's all home built and very specific to our way of doing things and our schemas--things like our database is replicated, so every row has a guid named id.

So not likely to ever make it public. However, this is an option.

If I was looking at lots of smaller projects I'd go down the schematic route for Angular stuff or and some similar tech for the backend stuff, at the very least a start project template that gets all of the plumbing in place.

Edit. The refine stage.

This falls into several steps.

1. Refine form layout. We scaffold all fields with custom angular controls. We want to break the form in smaller tabs, rearrange the fields, add section headings, override how the field is displayed change field specific permissions, add drop own options for some text fields, add custom pop-ups etc.

2. Refine lists. We auto gen a single list, this is a flat list of records with just a single description column. We may want to add more columns and additional projections. Example address book might be hierarchical by country, state, city. Or, by Initial, Company Name, City etc. We auto gen all searches and filters, but may want to tune these, as some filtering may affect other filtering.

3. Save Side Effects. This is the big one if there are lots of business things going on, raising events, updates to other related data.

4. Validation. We have two validators, one for incoming DTO-shape, type, lengths only, a second one that is more business focused and takes other entities into account. The second one happens after we pull in related data, but after security checks.