[RFC]: use styleguidist rather than the Component Library website as a single source of truth for all pubsweet components?
We currently have the Component Library, which describes all pubsweet components. But it's out of date. Ah, classic documentation problems.
Styleguidist solves that problem for us, in terms of React components, by generating docs from the code itself.
At the pubsweet meet, there was a suggestion of using styleguidist
for this too, by adding markdown files against each pubsweet component. But the group was mainly focused on auditing what had already been built and could be shared back, rather than defining new processes that everyone should follow. In any case, this feels like something which everyone needs to collectively agree upon.
Besides that, I'm unsure whether this is actually possible, since styleguidist was built specifically for React components?