Change Details

Some requests have come in from various teams about customizing Codex components to cover a particular use-case. [ TK - examples of this ] We want to support our users in these situations, but we also want to ensure that Codex components follow a consistent set of design guidelines. What level of customization do we want to allow across most of our components? For example, do we want to lean more heavily on Vue's `<slot>` feature, which would allow users to inject arbitrary markup inside of components where desired? We could write our code so that components might include default elements which could be overridden when a user wanted to do something custom. If we do go down this route, how do we want to ensure that customized components still follow our overall design guidelines? Maybe additional specs or documentation is needed for this.

== Background goal Some requests have come in from various teams about customizing Codex components to cover a particular use-case. [ TK - examples of this ] We want to support our users in these situations, but we also want to ensure that Codex components follow a consistent set of design guidelines. What level of customization do we want to allow across most of our components? For example, do we want to lean more heavily on Vue's `<slot>` feature, which would allow users to inject arbitrary markup inside of components where desired? We could write our code so that components might include default elements which could be overridden when a user wanted to do something custom. If we do go down this route, how do we want to ensure that customized components still follow our overall design guidelines? Maybe additional specs or documentation is needed for this. === User stories - As a developer I need to customize some components in order to cover new use cases. - As a designer I need to add new properties or styles to my components in Figma. === Open questions - Do we want to let our components be customized? - Should we provide additional specs or documentation to ensure customized components follow our design guidelines? === Acceptance criteria (or Done) [] Decide if we want to let our components to be more customized [] Decide the work process we want to follow [] Decide on what type of specs do we want to provide in these cases

== Background goal Some requests have come in from various teams about customizing Codex components to cover a particular use-case. [ TK - examples of this ] We want to support our users in these situations, but we also want to ensure that Codex components follow a consistent set of design guidelines. What level of customization do we want to allow across most of our components? For example, do we want to lean more heavily on Vue's `<slot>` feature, which would allow users to inject arbitrary markup inside of components where desired? We could write our code so that components might include default elements which could be overridden when a user wanted to do something custom. If we do go down this route, how do we want to ensure that customized components still follow our overall design guidelines? Maybe additional specs or documentation is needed for this. === User stories - As a developer I need to customize some components in order to cover new use cases. - As a designer I need to add new properties or styles to my components in Figma. === Open questions - Do we want to let our components be customized? - Should we provide additional specs or documentation to ensure customized components follow our design guidelines? === Acceptance criteria (or Done) [] Decide if we want to let our components to be more customized [] Decide the work process we want to follow [] Decide on what type of specs do we want to provide in these cases