Samuel Stroschein

**Notes from convo with @NilsJacobsen ** - main point: how to expose styles from host app - awesome: settings.json JSONSchema and module `settingsSchema` (also a JSONSchema) can be used to...

Insight: The entire component is "just" a rendering engine for JSON SChemas. APp settings, module settings and project settings can all be rendered from a JSON schema. - make project...

> Do we want to have versioned releases for UI? (Yes) Yes. Create a separate package for the settings component that is released like the other NPM packages. > Does...

Notes after a call with @felix: 1. no need to ship themes. Apps need to adjust the style to their env anyways 2. thus, ship the component with "base" style...

please just agree to ship icons with the component. this will ensure that: - less maintenance for apps - unified icons for settings! (imagine app 1 having a different icon...

> Should we name the component while the package is named @inlang/settings-compoenent? Don't abbreviate. Name it ``. The package name and HTML tag name prob do not need to align....

> Proposal: Let's start with save whole form Agree. Have a save button that is always visible (not at the very bottom!) and nudges users to save their changes.

@NilsJacobsen i propose to design the settings UX in figma before you code stuff. you can align everyone much better if you show what the resulting UX will be rather...

@NilsJacobsen can you share the link to the exaclidraw? It's likely easier to comment directly on the excalidraw. I have several questions about the UX flow: - what happens if...

**Decision in call with @NilsJacobsen @felixhaeberle:** Design the settings component as a dedicated "page". The tradeoff to design the component "embedabble" (to be rendered in the page of an app)...