/admin, the Administrations components implement a number of cross-cutting concerns. The most important are:
platform/src/Administration. Therefore, the SPAs main entry point is:
./Resources/app/administration. Everything else inside
platform/src/Administrationcan be seen as wrapped configuration around the SPA. This bundles main concern is to set up the initial Routing (
/admin) & the Administrations main template file, which initializes the SPA (
./Resources/views/administration/index.html.twig) and to provide translation handling.
srcdirectory of the SPA below is structured along the three different use cases the Administration faces: Provide common functionality, an application skeleton and modules.
app: Contains the application basis for the Administration. Generally you will find framework dependant
core: Contains the binding to the Admin API and services.
component, adjacent to web components.
pagerepresents the entry point or the page that needs to be rendered and encapsulates views. A
viewis a subordinate part of the page that encapsulates components. A
componentcan itself encapsulate different components, from this level on there is no distinction in the directory structure made.
pageis mandatory in each module. Though views and components can be present in the module a vast default component library is present to help with default cases.
Component.extend()a new component is created. With
Component.override(), on the other hand, the previous behavior of the component is simply overwritten.
aclincluded. In this directory one will find specific mappings of privileges (permissions for roles; additional permissions) for the default roles:
deleter. A more guided article about ACL can be found here: