How hard would it be to add a basic authentication layer? (ie: for documenting private git-hub projects on a GitHub pages site)
I realise the published documentation content/back-end files could still be accessed by an unauthenticated user by guessing their URLs, but a simple authentication mechanism on the front-end SPA would be sufficiently-secure for many private projects.
Ideally, authentication linked to GitHub would be awesome if it allowed access to the published documentation based on a user's permission to access the underlying documentation's GitHub repo.
(This is something I would be interested in contributing to, since most documentation systems are focused on public vs private documentation, and I'm still looking for a GitHub-centric alternative for documenting our team's private projects. )
How hard would it be to add a basic authentication layer? (ie: for documenting private git-hub projects on a GitHub pages site)
I realise the published documentation content/back-end files could still be accessed by an unauthenticated user by guessing their URLs, but a simple authentication mechanism on the front-end SPA would be sufficiently-secure for many private projects.
Ideally, authentication linked to GitHub would be awesome if it allowed access to the published documentation based on a user's permission to access the underlying documentation's GitHub repo.
(This is something I would be interested in contributing to, since most documentation systems are focused on public vs private documentation, and I'm still looking for a GitHub-centric alternative for documenting our team's private projects. )
Regards, Michael