this looks indeed very promising. I will definitely give it a try.

Hi, I am also still looking for something easy & intuitive.

We did take a look at several tools, like gitbook, fractal, Gatsby.js, Cogear.js, Zeroheight, InVision DSM, Storybook, Confluence etc.

So far we still work with our own solution which is basically a light weight CMS based on markdown JSON files.

But we are not 100% satisfied so still looking. We might try out Cogear.js as we are developing with angular and not react.

This is a very interesting topic. The way I see it is that a design system is split up into to levels of documentation.

1. Documentation for really building the design system. So basically a typical designer -> developer hand-off.

2. Documentation for using the design system to build stuff.

For the first documentation level I would recommend to use a combination of Confluence, Jira, and a hand-off tool like Abstract (Inspect) or Zeplin. Why not only Jira? Because we for example build a design system for multiple frontend frameworks. And tickets get closed, that's why I would recommend having a general documentation in confluence and move them to Jira when the dev team of each framework need them.

For the second level of documentation I would recommend to use something like Zeroheight.io, InVision DSM or things like that.

In addition to that you should also maintain a Sketch Library and have it available for everyone to use and link it. We use abstract for that but you could also use Sketch Cloud or something else. Key is to make it available and easy to update.

Hi Josue,

so we are a Sketch + Angular + SAPUI5 + ReactNative company as of now. We are looking into Figma, Adobe XD and all the others. But for now we are sticking with Figma.

For collaboration and versioning we introduced Abstract a couple of weeks ago which supports our workflows really nice.

For prototypes and communication we use InVision. For the design specs we also use Abstract.

For the communication with more than just design specs we use Confluence / Jira. Although thats also the point where we are not 100% happy with.

We are also looking into InVisions DSM and tools like Storybook, AirBnB Lona, SwankyDocs and things like that. Our goal is to automate the process and documentation for already developed components while also bringing in design documentation.

As of now and with all the history we are not ready to move to a tool like FramerX for example. Better more automated / synced documentation tools are what we are looking for.

Custom solutions always seem nice but we experienced that they get too less attention over time.

So will that be part of the regular enterprise team account or is it gonna cost us extra $$$?

cool cannot wait to see what you have been working on.

One question: Where / or how will be a design system shared?

There is a workaround that worked for me. Download the new version from http://www.sketchapp.com and replace the one in your applications folder.

After that it worked for me and opens all files just fine.

I am personally not a fan of online design software like "figma". I love the native performance of tools like sketch and their abilities with plugins.

What is your take on tools like that?