3 ms·
Replying to myself. It's distressing how many of the options assume command line competence. It used to be that graphic designers, photographers, families, etc
by ridiculous_fish 9y ago
Replying to myself. It's distressing how many of the options assume command line competence.
It used to be that graphic designers, photographers, families, etc. could set up a simple site with a shared host, an FTP client, and a bit of HTML. Now requiring HTTPS will push this further out of reach.
This content is now funneled into either managed platforms, either free ones that monetize it (Medium, Flickr, Facebook, etc.) or more expensive higher-touch services (SquareSpace, Wix, etc). The de-democratization of the web continues.
- jacobparker 9y agoWhatever company offering you FTP access and hosting those files for you over HTTP should be setting up HTTPS for you automatically without any extra input from you. That’s why all the instructions assume command-line competence: designers are not the target audience; sys-admins are. If your host hasn’t caught up with the times yet it’s very straight-forward to get this for free (along with other benefits) from cloudflare with a few clicks. This is misinformed FUD.
- AndrewConn 9y agoGenerally agree with you... however, I’m a designer and I’ve had surprisingly positive experiences with AWS. I thought it was going to be highly technical and frustrating, but for basic static hosting AWS doesn’t require any command line skills. It’s all point and click. You can even set up SFTP to your S3 bucket with something like Transmit from Panic (Mac). More of what you’ll find yourself dealing with is AWS’s confusing UX, understanding how all the AWS parts fit together (Route 53, CloudFront, etc,) and discoverability in their help documentation.