jaffoneh

The main reason to do a Twitter thread (which the author alludes to but doesn’t look at enough) is audience. Good thoughts can go viral quickly on social media. The same cannot be said for blog posts (even when shared). This could be speaking to a larger issue but still the case.

As an example, I published this blog post [1] in November of 2019. It was probably read by hundreds to low thousands in about a year.

I then made a twitter thread out of the same content a year or so later [2], it was seen by over half a million people.

This is not to say audience is the only consideration but a combination of a blog post turned thread might be the best way to get audience and an archive.

[1] https://www.mynameisjehad.com/making-the-case-to-decision-ma...

[2] https://twitter.com/jaffoneh/status/1376945166771056641?s=21

There is Clarity: https://clarity.design/

Having worked remotely for the past few years, my experience has been that working remotely depends on the team itself as much as it depends on the individual's ability to work from home/remote.

The #1 factor that made the difference for me is how many others in the same team are remote. For Clarity (a team I lead), we decided early on to have a completely remote team. Few members of the team do work in HQ but most of them are remote. We wrote something about it here: https://medium.com/claritydesignsystem/working-remote-how-we...

Not to repeat the same post again but having the whole team remote with the option to gather every few months made a huge difference for us.

I've also worked remotely previously with a team that was mostly centered in one location, that wasn't a pleasant experience. Most of the decisions were still discussed outside of scheduled meetings and I constantly felt like an inconvenience to the team especially when having to setup communication and video conferencing tools at the beginning of each meeting just for me.

Fixed. You can click on the top-right menu to get the sub-menu and from there navigate to the icon set.

Good point. Working on it

I shared a bit of our thoughts getting here and getting to custom elements as well as how we support in a medium post we wrote earlier, not sure if you noticed it. Here is a link again: https://medium.com/claritydesignsystem/the-road-to-svg-and-c...

Yep, that's a bug we're currently working on, should be fixed today. Thanks for the heads up

I believe it's a coincidence especially with how common names are when they are a word. Clarity is based on the name of the design system itself

Clarity overall (including the icons and icon system) is under the MIT license: https://github.com/vmware/clarity

Thanks for the feedback, polymeris. I'll into why they're looking blurry, I haven't seen that before.

As for why not use an icon font, we've actually outlined the research in details here: https://medium.com/claritydesignsystem/the-road-to-svg-and-c...

Really excited to see this at the top of the home page for HN. My name is Jehad and I lead the Clarity Design System team. Happy to answer any questions.

For those interested in the work we've done and the road we've taken to get here, we wrote a post originally on our iconography system here:

https://medium.com/claritydesignsystem/the-road-to-svg-and-c...

It is titled: "The Road to SVG and Custom Elements in Clarity Icons"

Much of the content made it through to the "get started" page this thread is linking to.

You can check out the icons themselves directly here. We have over 200+ icons at the moment and counting! https://vmware.github.io/clarity/icons/icon-sets

I can't generalize to everyone's motivation but I can tell you ours when it comes to Clarity.

Iconography is an important piece of a design system. Designing iconography that fits within the general look and feel of a design system ends up defining a big part of it especially if that design system is used across many application (within and outside of VMware) as Clarity is being used.

With that in mind, we ended up designing our own. Since Clarity itself is fully open source under the MIT license, it only made sense to open source the iconography system itself and the icon set.

If you take a look at the link posted, there is also an interesting iconography system behind this (You can read more here: https://medium.com/claritydesignsystem/the-road-to-svg-and-c...).

Does not answer your question in general but thought I'll offer our own point of view.

The submission is specific to the new icons website and icon system we've just released (vs. Clarity Design System itself that was out and open source since November)

You can take a look at all the categories, icons, and how to use them here: https://vmware.github.io/clarity/icons/icon-sets#core-shapes

In case anyway checks this out, an update to the Clarity site has already went out that improves the performance of the website drastically. Let me know if you're still seeing any issues and thanks again for the feedback :)

We do have a bug on the website, it doesn't really have to do with the design system itself but with the way the website itself is built. Should be fixed soon. Thanks for the feedback :)

Clarity just moved to headless Chrome from PhantomJS today: https://github.com/vmware/clarity/pull/803

Thanks, we're excited! We started using Angular 2 early this year for Clarity (it was at one of the betas). We should probably write a longer blog post around that (around the journey itself as well as adoption across VMware when Clarity was private), might be useful to others!

As for TypeScript, yes we mainly use TypeScript!

Hi choward, you are not blind! :) We're working on a date picker. If you have specific requirements (especially around localization) we'd love to hear it to make sure we consider it but it is in the works1

That is a good observation. This is something we don't have today but we're working on.

Hi, ceejay! I'd love to know more about how you arrived to that conclusion. I am asking for a couple of reasons:

1. To get more feedback on the docs if that's how you arrived there. 2. To get more feedback on the system itself (design and code) to see if there are bugs we can fix and issues we can improve.

hey robwormald, will definitely do. We will actually reach out sometime today/this week!

Yeah, we definitely feel that and want to address that use case. Some of that research is shared today in places like patterns and for every components (if you scroll enough in the page) but more research is coming in the next few days/weeks. We want you (as a developer) to be able to not just use the code but if you'd like, be able to fully understand the UX guidelines behind building a Clarity applications and go a step further by explaining why given the research/assumptions we have.

Awesome. Glad you like it. Make sure to share feedback with us as you go through that. We'd love to continue to improve the system itself as well as the documentation!

Hi Bahamut, welcome! we'd love to chat with you guys (feel free to reach out to me with a DM on twitter). We'd love to share what we learned and learn from what you learned!

As for the slowness of the page, this is GitHub. It is currently down :(

As for AOT, that's definitely a priority for us (we were talking about it as a team yesterday and are working hard to make it a possibility for Clarity so we're definitely on the same page there).

Hi water42, I think material2 and other frameworks are fine frameworks and are worth your consideration.

We really built Clarity because we were in your position. No framework out there was able to provide us with what we needed to ship high quality, enterprise software but with modern and consumer-like UIs. We needed that framework to care deeply about user experience (not just provide code) and we wanted to make sure that framework is flexible enough that teams across the company (before we open sourced) can have the ability to understand it, build on top of it, etc.

We really looked around and every time we found something it had a part of the puzzle but not really enough of a part that we can depend on it.

Clarity does not depend on material (the design language), we are definitely inspired by material and others but we're building an end to end design system which includes the user experience and visual language aspects. Behind the components and patterns is a ton of research that we've doing throughout the past few months (and sometimes years depending on the data we have) and want to continue to do. One of our goals is to also share that research in case you can reach different conclusions so the community is able to keep us moving in the right direction.

Hi scwoodal, absolutely.

Before deciding to open source, we thought really hard about the long term strategy for Clarity. We did not want to open source the project and not be able to continue to build it. One of the many reasons we felt confident this is going to happen is that in the past year, we've build a very strong Clarity community internally. Over 35 product teams within VMware use Clarity and many more are on the way (many of them have not released yet but they depend on Clarity as a Design System for their future).

The team you see on the community page [0] of Clarity is a 100% dedicated to making Clarity successful. This will become more apparent in the next days and weeks as we continue to push more work into Clarity and continue to have more releases of it!

[0] https://vmware.github.io/clarity/community/

Hi wiradikusuma, for now maybe but when building Clarity we considered a future where we can have ClarityNG/ClarityReact/etc. However, for now, we're focusing most of our energy on ClarityNG to make sure we can deliver the next set of components to complete the library.

Thanks! Please let us know if we can help in anyway and if you have the time, we'd love to listen to feedback on both: the design system itself as well as the tools you used to use it. As a quick note, we've also open sourced Clarity-seed alongside Clarity to make it easier to get apps up and running on Clarity: https://github.com/vmware/clarity-seed so that might be worth a look too!

Hi merb, could you elaborate a little more on why you think it is a challenge to keep up with the speed of development from Angular?

I am not sure if there is confusion here but those components are built on top of Angular 2. We use and love Angular 2. In fact, we talk and work with the Angular team and both Angular and Clarity are open source projects. We contributed and would like to continue to contribute back to Angular as well!