improving help pages infrastructure about skeleton-bridge HOT 4 OPEN

This issue assumes that we agree that maintaining our own help infrastructure is necessary to be allowed to add the support for our own "plunker" and other additions we are considering. The alternative option (to switch to Aurelia's own help system) may take too long and be too constraining.

from skeleton-bridge.

Just to throw it out there, we could extract the docs infrastructure into a different app. I'm thinking of one website where you can login via Github, and where you can create docs per repository (we could use the github api to check which repositories a user has access to).

Some advantages:

• Extensible (the app would be in our control)
• We don't have duplicate code (docs infrastructure is the same for each repository, making it hard to update / maintain)

The disadvantage is that it's going to take more time as we need to design/build the infrastructure, but then we only need to do it once vs for each repository

from skeleton-bridge.

I like the idea in general.
Our users would then have to leave the catalog app, right?

from skeleton-bridge.

Yep.

from skeleton-bridge.