-
Notifications
You must be signed in to change notification settings - Fork 6
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
Improve global look and feel of the pattern library #106
Comments
Thanks for opening this @ThePeach, this is definitely a subject that warrants further discussion and, I'm sure, will spawn quite a few tasks. Here are my initial comments, thoughts and ideas... ParticlesAgreed that these have been shoehorned into PL as there was nowhere else to showcase them. We should rectify that. Some options we might consider are:
Whatever we end up doing, my only hard requirements are:
AtomsI think there's a lot of value in PL's lineage feature to help Gravity consumers and maintainers better understand which UI components other components are composed of. Likewise, to determine what will be affected by changing, say, an atom. I know due to limitations in Mustache and PL it's not always practical to As for the classification of what, exactly, should be an atom and what not - I'm sure we haven't got that quite right yet. So, definitely support reviewing and revising that stuff. Maybe we can do another UI inventory exercise? Templates & PagesNow that the Buildit website is mature, I think we can simplify what we have in PL. It's useful to include some templates and pages as examples of what you can build with Gravity, but they do not need to maintain parity with the live site. On a related note, I'd like us to revisit the whole |
The issues raised here have been or are being addressed by a various other issues and PRs.
...and the remainder of adding some docs into the pattern library and making it appear more inviting are sorted by PR #350, which will close this issue. |
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Closing this issue, since it's just repeating what's now being (or, in some cases, has been) addressed by other issues. |
As an effort to make this pattern library easy to browse and consume, I'm opening this ticket as I think we can proceed with a series of small improvements that can largely affect the way we use, consume, and improve this tool.
I'm trying to keep the conversation in here so we are aware of the decisions and what is needed to be done.
Here's a random list of things that I'd love to address:
I'm completely happy to split this ticket in sub tickets as soon as we come to the conclusion that any of what we will discuss is worth investing time into.
The text was updated successfully, but these errors were encountered: