-
Notifications
You must be signed in to change notification settings - Fork 39
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
@dwyl Component Guide in Tachyons? #UXQuest #9
Comments
@nelsonic this sound fantastic!!! I think its a very sustainable way for everyone to go about... for you as a team as well for your clients. In terms of the design of the components, I will have a look at your suggestions but would like to say that I personally really like the "power of 2" system that Tachyons itself adopt- no "magic design numbers" means that there is a mathematical thought behind the Tachyon ecosystem- that is why its mostly pleasing to the eye :) But obv, there is work that can be done using DWYL's brand guidelines to customize it and create DWYL's unique ecosystem.. Would be very glad to contribute and perhaps pair with @harrygfox and help :) |
Sounds like it could be a lot of fun! 🔬 👩🔬 |
@harrygfox + @nogainbar when do you have availability to discuss/start? |
@nelsonic: @Cleop is already coming up with a suggested implementation based on her experience with HL and LDMW. |
@nelsonic @harrygfox I'd love to share with you my experiences so far. Let's discuss this afternoon! Exciting stuff! |
@Cleop sweeeet! 🍭 |
I'm not entirely impartial, but think the Lost My Name design system is pretty sweet: http://design-system.lostmy.name/ Just remembered as they just did a blog post on it: https://medium.com/making-lost-my-name/benefits-of-a-connected-design-system-608199816f00 |
Also here's Clearleft's take on component libraries: |
Why?
All Client Projects & dwyl Products (for the next couple of years) will be using the "PETE" Stack.
We need to make it easy for people to
ship
as consistently, quickly and painlessly as possible. To aid that we need a Component Guide with detailed examples people can "copy-paste" from.What?
A Component Guide people can use to build/ship their apps fast.
Something similar to:
How?
Initially the idea is for a week of Tachyons "Apprenticing" where the outcome is:
e.g: https://ui.dwyl.com
.then
taught to NHS/MWV/SL etc.) Note: I know recording videos may end up taking us over our1-Week
initial estimate, but we will break down the tasks a lot further.This will be the first "project" our "Full Time UX person will undertake.
@harrygfox / @nogainbar let us know your thoughts & discuss!!
TBD...
We need to discuss/decide:
else
do you want/need to knowbefore
we can get cracking on this?And Then...?
Longer-term we could help @mrmrs & Co with their "WYSIWYG" UI builder which we can then use to rapid-prototype with Clients and Products. But let's not get ahead of ourselves just yet.
CC: @markwilliamfirth / @iteles this is highly relevant to Product.
The text was updated successfully, but these errors were encountered: