8th of March

• Maria L from Builders showed us the new Core 30 components.
  • Month-picker is now released.
  • Date-picker is now in released.
  • Work on Table has almost completed, only some minor issues remain.
  • Remember their board that shows what is worked on.
  • All Core 20 components have after this been developed for NCI in Core 30! Huge milestone 🥳
  • There's some new components being worked on until Core reaches "complete NCI"-status.
• Som good questions around Core came up:
  • Versioning - `core-components` will not (for now) bump major version even for breaking changes, as it is currently evolving a bit too rapidly.
  • When it is more stable, Builders might consider going for always signaling any breaking change with a major version bump.
  • Follow the updates on the Change Log page from the Core docs and pay attention to the details there when upgrading.
• The Form Loader (a Part for the CMS) is soon updated, it can then also load Vite-apps, and pass key-value pairs as a `data` attribute on the containing div.
  • Reach out in #frontend or #team-builders when you need to create forms and I can show you the ropes.
• Last but not least, Global Navigation, was demonstrated by Jonathan from Team Service.
  • It's work in progress.
  • It's almost at a stage where the code for desktop can be tried out.
  • Mobile version not begun yet.
  • It is a package of its own called core-navigation, and you will find it in the Core source code, but installed individually.
  • It contains key building blocks in form of components and wrappers, that can be used to create a menu looking the same way across apps.
  • It has a "config or children"-concept, where you can construct react nodes and pass in as children to every component, or you can (for some) pass in configuration in form of JSON to generate the right sub-components.
  • The CMS integration of building menus is now in a beta-staged, developed by yours truly. Editors are trying it out now.
  • Builders will soon try to tie these two things together so that editors can preview the new menu.
  • Application-portal will have some form of opt-in config for using the new menu.

Some questions/discussion from the participants:

• "I want to discuss something for next forum, what's the correct approach?"
  • Post openly in #frontend on Slack, or PM me, Bobby Westberg.
• Do you recommend using Vite instead for apps?
  • Yes, but we're aware that there will always be cases where this doesn't fit you, so this is not forced. You don't have to migrate all your apps.
  • Team Service have moved almost all their apps to Vite as they saw a lot of benefits for this.
  • The CMS, as well as application-portal, can load both types of apps.
  • Here's a good little tutorial by Team Service on how they did it, this might be inspirational.
  • Here's an example of the build-scripts they use. And here's the source for them.
  • They rely on using their teams @gjensidige/service-scripts npm-package.
  • It will not be a plug-and-play journey, but hopefully some inspiration.