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