To be clear, my proposal is really just about phx-no-feedback, but I do agree with the general sentiment that CoreComponents need to be re-thinked.
Currently they just don’t follow good component based development principles. For example, the smallest component when working with an input is a whole field (label + input + errors). While a field component should exist, it is generally a good practice to compose it from simpler, more generic, components.
Additionally, while the core components are a great showcase for the flexibility of TailwindCSS, they are not e very good example of good TailwindCSS. They make use of arbitrary values all over the place which is generally a poor practice as it reduces styling consistency. Also, they make use of margin all over the place which is almost always a bad idea in component based UI development (padding and/or having the parent provide spacing for its children, is generally considered a better approach).
My advice would be to rename CoreComponents to PhoenixComponents. Then have CoreComponents be a larger set of more generic and composable components that PhoenixComponents use. The idea being, Phoenix expects certain components with certain semantics to exist for thing like generators to work, and that’s reasonable, but that API is a level above the core components of an application. Phoenix could, initially generate a CoreComponents module as well that fills the role of generic composable components and are intended to be used by developers to form more complex UIs.
With this approach, component libraries can still provide a “drop in replacement” for PhoenixComponents, but that module would just be a module which uses the component library’s components. Developers would use the component library’s components directly.
This is a whole other convo I’d love to have, but not in this thread.
Also, it’s always weird when I have a notification from 
