...
Discussion about approach for implementation of authorization. Conclusion was that we should create a separate ontology for Vitro AuthZ solution. One, or two person should work on designing it before we implement that into Dynamic API. Georgy thinks this is a big issue deserving a complete sprint, and we need a quick and simple solution for forthcoming sprint. That solution might be that users with role Administrator can modify (create, update, delete) dynamic actions, while a role for execution of a dynamic action is defined by using hasRole object property in the Action class.
Angular and Angular Material will be used for development of UI. William thinks generators are not solution for our case, it should be dynamic UI capable to adopt on any change in a dynamic action on the fly. Angular Universal will be used for implementation of Server Side Rendering for the improvement of Performance and Search Engine Optimization. NGRX will be used as a central state management. A runtime i18n is needed.