Luigi consists of two components: Luigi core and Luigi client.
Luigi core is installed in the web application while Luigi client is installed in the application(s) running in the content-view. Both of these components interact with one another to leverage communication between both the web application and the content-view, without compromising the security principles behind the iframe pattern.
Luigi core is the part of Luigi that enables navigation, security and routing. To get started with Luigi, read this document.
- Application setup shows you the first steps to prepare your application for development.
- Navigation configuration shows you how to configure navigation.
- Authorization configuration shows you how to secure Luigi.
- General settings provides you with configuration parameters.
Luigi client enables integration of Luigi in views. You can easily configure the lifecycle and links of the client, as well as customize the appearance of your navigation.
- Lifecycle gives you details on the life cycle of listeners, navigation nodes and event data.
- Link Manager allows you to navigate to a specific route.
- UX Manager helps you to manage the appearance in Luigi.
See this document to learn more about the Luigi client.
View example applications.
Code formatting for contributors
All projects in the repository use Prettier to format source code. Run the
npm install command in the root folder to install it along with husky, the Git hooks manager. Both tools ensure proper codebase formatting before committing it.
To ensure that existing features still work as expected after your changes, run UI tests from the Angular example application. Before running the tests, start the sample application by using the
npm start command in the application folder.
When the application is ready:
npm run e2e:runin the
core/examples/luigi-sample-angularfolder to start tests in the headless browser.
npm run e2e:openin the
core/examples/luigi-sample-angularfolder to start tests in the interactive mode.