This may be a bit premature but are there plans to come up with some sort of API documentation for the Jsonnet libraries, in particular the Kubernetes (ksonnet) library?

I find it really difficult to use without lots of string searching. IDE support would help but most plugins are limited. I just found http://g.bryan.dev.hepti.center/ which looks pretty cool. How do others manage to use it?

Preamble

I find myself doing things differently while creating this repo and companion content, trying to focus on defaults of libraries. I would normally not use a .storybook directory and opt for my own config folder, but keeping scripts as simple as possible is really refreshing. I feel like I am constantly coercing my projects to work with my opinionated structure instead of relying on t

Thanks to @sebastianflorica for the suggestion.
Having a place to document the FAQ from #dev-tradeshift-ui can be really beneficial for developers.
Some stuff like integration with react and angular or how to use attributes with . in jsx can't be fitted anywhere else in the documentation as far as I can see.

Having it as a page in ui.tradeshift.com
OR
Create a wiki page
are two pla

When opening the soldoc page there is no link to go to the repo. When opening the repo in github there is no link to go to the soldoc page.

Ideally we should have a method createStore so we can do something like

class App extends Reduxable { ... }

const myApp = new App()
const store = myApp.createStore()

The idea would be call Redux's createStore(reducer, initialState, enhancers) with the reducer and initialState we already have from the Reduxable instance and give the user the option to pass `enhan