15th of February

• Custom Parts were the main talk.
• We have three ways of doing it, the most used one is the App Loader, but we also have a Vite Loader.
  • It's a way for the CMS to load your custom React-applications from the CDN, embedded within a page of editorial content and "parts" from the Builders Platform.
  • Read about the general idea here on Builders, more to get the main idea behind the system.
  • And read about the detailed technical spec in the Builders Platform Docs.
  • Relies on you building your app generating an assets-manifest file, publishing it with all resources in a folder on the CDN.
  • Additional data can be passed from CMS to the app, as data-attributes and/or a unique URL end-point which can be read using POST. Read details in the docs.
  • Bare in mind, all Parts in Enonic will always take the width of the full screen, so you need to add it to the grid yourself.
• The Form Loader uses similar technology but simpler UI for editors.
  • Usually one mono-repo with multiple forms.
  • Each form is one CRA.
  • App.tsx contains the form-code.
  • Contains its own API for doing the e-mailsending, Dynamics-talking, or what you need.
  • Published to CDN.
  • In root of the CDN there's a JSON over all forms, Enonic XP reads this JSON to display a drop-down menu for including the form in the CMS.
• All these ways of loading custom apps are always evolving, so come with feedback!
• You can still load full pages apps as usual with Application Portal.

There were rather many questions here, I'll try to recall them all:

• Is there an overview of all custom apps our there?
  • No, but perhaps we could try to gather some overview of that if people are good with informing about their apps.
• How do I get access to the CMS?
  • Your closest editor could probably help you with that, otherwise each country have an editor in chief that knows how to do this.