Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Components: agree on components classification #34305

Open
3 tasks
Tracked by #34304
ciampo opened this issue Aug 25, 2021 · 2 comments
Open
3 tasks
Tracked by #34304

Components: agree on components classification #34305

ciampo opened this issue Aug 25, 2021 · 2 comments
Labels
[Feature] Component System WordPress component system [Package] Components /packages/components [Type] Discussion For issues that are high-level and not yet ready to implement.

Comments

@ciampo
Copy link
Contributor

ciampo commented Aug 25, 2021

Why

As the components library grow larger, it may beneficial to split (and list) the components into separate groups (e.g. low level, high level, utilities)

What

The "what" will be the outcome of this conversation

A/C

  • Agree on components classes (e.g. low level, high level, utilities)
  • Potentially create folder structure in the components package
  • Update documentation
@ciampo ciampo added [Feature] Component System WordPress component system [Package] Components /packages/components [Type] Discussion For issues that are high-level and not yet ready to implement. labels Aug 25, 2021
@mtias
Copy link
Member

mtias commented Aug 27, 2021

I'd prefer to avoid any classification for now and retain a flat list. We can introduce some order later on when things decant.

@ciampo
Copy link
Contributor Author

ciampo commented Aug 27, 2021

Make sense. We can continue the conversation here at a later time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Component System WordPress component system [Package] Components /packages/components [Type] Discussion For issues that are high-level and not yet ready to implement.
Projects
None yet
Development

No branches or pull requests

2 participants