At work, I'm still doing in design documentation, It is a combination of Sketch/Figma + Zeplin. However, it's not great for scale, terrible for discoverability and searchability, but great for direct communication with the team that you are working with.

Storybook is always talked about for living web component with documentation. https://storybook.js.org/

I have seen some people using Notion with good results https://www.notion.so/

Overall, whichever approach you use, it's good to find the right fit for your team and the documentation strategy that the team is adopting. It's really down to how you want to communicate and maintain it. Really like how designbetter.co sum up on the team model. https://www.designbetter.co/design-systems-handbook/designing-design-system

I'll set some context as I'm conscious that the response can differ based on geographical region. Currently, where I am in Singapore, the design industry is still playing catch up. Businesses are starting to shift from a culture of cost-saving measures to a focus of better overall delivery.

There is a tiny pool of experienced talent but an explosive growth of entry-level talent in the market, thanks to places like General Assembly. There is a considerable gap for an experience designer.

Some larger teams are starting to build a better culture of learning and exporting it through meetups. However, there's still a ton of small team of one and individuals who find a lack of opportunity to learn to hone their craft better. So there's been a growing demand for mentors.

There is no formal network of mentors outside of work as far as I'm aware. Culturally, it is also fairly conservative, so you don't get people reaching out to talk about this openly.

I'd love to hear what others have experience before.

no harm doing a little self-promotion. ;)

People forget that to get a system running, you need people to first build it, and then continuing maintaining it. If anything, it creates more work rather than less, at least this holds true for bigger organisation.

Tackling changes and updates from multiple teams, along with communication, documentation, and releases, heck it's a teams worth of work on it's own. Smaller teams can afford to skip some steps, but the true worth is about efficiency, so designers can focus on other parts that attention is sorely needed. At some point, you'll have to split you attention and get back into greasing the system's gear.

I would pick up magic tricks. The idea of misdirection and sleight of hand is great foundation to apply it in the dark arts of design.

Designer Hangout is one the best and most active one that's still around. They even have their own forum now that's outside of slack because of the noise. Quality is high because it's still an invite-only community ;)

Throwing Sympli into the ring. Some nice touches here and there, and it plugs right into Xcode or Android Studio for mobile devs.

I've always use pngyu http://nukesaq88.github.io/Pngyu/ even though its old. It uses pngquant too. The simple UI optimises at lighting fast speed and pretty aggressive at crushing down the file size.

Couple of good communities in Singapore. 2 of which listed below, I have worked with as a venue host.

• UXSG
• IxDA SG
• Sketch Design Singapore

Pretty sure there are plenty of others I have miss out too.

I felt like we seen this popped up now and again about DN turning into a cesspool of negativity/bots/self promotion/ads even before it was bought over to Andrew's team. (although it was uncommon when it was invite only).

It's an issue that people will need to learn to deal with, but you can decide on how. Just like a decent neighbourhood, you can always choose to move and relocate when things go bad, or you find ways to help the community tackle the issue.