Should HungerRush require us to protect the content of this documentation site, we will need a solution to do so. This document is a spike to investigate the options available to us.
Use .htaccess as a simple authentication mechanism to password protect the static site
Findings: Although there are numerous articles claiming this is possible with a static Hugo site, we have been unsuccessful in implementing it on our site. See links:
Outcome: Unconfirmed. I suspect this is because we the necessary access to setup a valid subdomain on hungerrush.com’s DNS. We would likely need to request this from the HungerRush team if we were to persue this option.
Protect specific content within Hugo pages with a password prompt
Findings: Use Hugo Encryptor shortcode plugin to protect only sensitive information in the docs
Outcome: Although not attempted this seems like a feasible solution. If We’re unable to resolve option 1, we should attempt implementation of this solution.
Private pages via github settings as discussed in the below video
Findings: We would need to be an enterprise customer to and add all users to our github to give them access to the content
Outcome: Not feasible.