Separation of business logic from UI in Reference App

I noticed that business logic, i.e. entities and microflows, in the AtlasUI Reference application is stored in one module while pages and UI widgets are stored in a different module. Does this represent the “new” best practice? I think this is the right way to go. Just wanted to receive community feedback.
0 answers