3 ms·
> In the old times, you could only host content if you were really good with the technology. The people who had websites were people who knew how to set up and
by tannhaeuser 5y ago
> In the old times, you could only host content if you were really good with the technology. The people who had websites were people who knew how to set up and run a web server, and to compose the HTML content that was being served.
I don't see what's particularly difficult with hosting a static or mostly-static site, and why you'd have to be really good with it (many early content creators weren't). With Apache shared hosting (where your domain, certificates/acme, and basic htaccess are setup for you), this is a matter of putting a couple of HTML and optional CSS files into your document root via ftp/sftp back in the day, or scp, or WebDAV. And HTML is really not that complex a format (or at least used to be before responsive/mobile web), being based on SGML which was designed as structured text format that can be created with a plain text editor in a way that's being taught in secondary school for decades now, and tips available in magazines etc.
- Nebasuke 5y agoI think you're still missing OP's point. Sure, using ftp/sftp or scp is pretty easy for a software engineer, or technology enthusiast. However, that doesn't mean a content creator is happy to learn it, since as OP said, they care about the content not the actual tech. If they have a choice between using something that requires scp and writing HTML versus a graphic environment that is WYSIWYG, then the choice will very likely be the latter.