Ask HN: Why is sharing private static HTML with non-engineers still hard?

3 points by nate 13 days ago | 1 comment

This sounds like a problem from 2005. But I keep running into it.

I have a folder of static HTML and CSS. Think: docs, reports, AI prototype, whatever. It’s just a tiny html microsite. Nothing dynamic.

And I want to share it with some people. Easily.

But now the hard stuff: SSO gets involved. Github Pages is public unless you are using an Enterprise account and just with engineers? Google Sites? I guess the old days that would work like you would hope: and let you upload sites. Today, it's more like a website builder? Can't upload raw HTML sites there.

My wife works at 1pass :) So my brain is in 1pass a lot. Would you use some kind of additional app that is basically “Vault Pages”? I don’t think you can have any kind of tree inside a vault. So things have to be pretty flat or deflate something like a zip file with the folder structure in it. You’d be able to share urls like (as long as you all agree to use this additional .app, and I’m assuming you're a Mac shop):

`vaultpages://engineering-handbook/deploy-checklist`

Would you us this? Or you already have a great private microsite solution that isn’t messing with additional SSO, VPNs, IAM policies, etc.

PaulHoule 13 days ago |

I build a microsite with Vite and then run a Python script that copies the files to S3 and does the Cloudfront setup which is usually just an invalidation because I will put many microsites on the same domain. I don’t see what is so hard about it.