![]() This is because photos are inherently bandwidth intensive, difficult to organize, and difficult to make accessible to multiple device types and connection speeds. As you’ve probably noticed, this site mostly uses Flickr or Instagram to host photos and embed them, without relying on self-hosting. Photos are a bit of a different animal to a bunch of text. Since all components of the site are contained in the repository, I don’t need to maintain a database server or database backups to restore the site after an issue.Since all components of the site are served to the client, it works better for accessibility.Gives me a progressive responsive site on all device types and connection speeds (which I have relied on first-hand in my travels).Trade’s off the client doing a bit of work during rendering to support any device nicely.Greatly reduces the bandwidth required of my server to host the site. ![]() Nothing on the site relies on my server’s power, so I can use the cheapest instance available to host the site.Every single thing on my site is cachable by the end-user’s browser and the CDN in-between.This confers a lot of advantages over a more traditional approach such as using a CMS like Wordpress, such as: Hugo takes a series of Markdown formatted text files, some HTML/CSS/JS templates, and a theme made of HTML/CSS/JS and generates this entire site each time I run the command hugo inside my site repository. This is made possible by a piece of software called Hugo. Currently this site is being generated offline as a series of static images, HTML, CSS, and JS files that get served almost entirely out of cache through the CDN provided by Cloudflare. ![]()
0 Comments
Leave a Reply. |