Hey Barney,

Thank you very much for the encouragement. Glad you find the article helpful.

We did not get around to creating a design system as nice looking as Lightning or Atlassian. However, the documentation we did was much more detailed and verbose — think Google material design guidelines.

Here’s a sample of what one of the component sheet looks like — https://www.dropbox.com/s/35t8n55z5og0bf7/04-forms.png?dl=0

As you can see, this is very functional because it is aimed at both designers and devs, as opposed to a Lightning or Atlassian style guide where components themselves are black-boxes. The reason is context — WebEngage’s platform is not going to expand to build other products on top off it.

I will stop before I write another 5000 word article :) but again, thanks for asking about it.