Skip to content Skip to footer

Managing my personal website

Last post in my ‘degrowth’ series: a few points around my concept of a personal and sustainable website.

Simone Silvestroni's avatar

I’ve been expressing myself on a personal website since 2002, writing about what I do — or want to do, along with personal thoughts. Two years ago it’s gone back to its static HTML and vanilla CSS roots, perfectly reflecting my attitude towards designing and developing for the web. I’ve always regarded the value of web performance as paramount, thus it was only natural that I kept my site as fast as I could, reducing its footprint to the very minimum. It’s not just about how fast a page loads, but also the weight of the data, along with its back-and-forth between client and server.

There is no database. I don’t use images unless necessary. The ones I use are thoroughly optimised, reduced in size as much as possible. Usually, they’re never larger than a certain width, exported (lossy) at 72dpi, and stripped of metadata. They’re properly described through alt tags, same as I do on the Fediverse (this is still a work in progress). Due to my vehement opposition to ads and trackers, plus a zero interest for web statistics, the site has no Javascript and no third-party calls.

Despite a bunch of available solutions, I chose not to have comments. The way to discuss posts is via email, through a link available at the bottom of each post. Even if the site is capable of sending and receiving webmentions, they’re not shown publicly. I grew distant from likes, comments, reposts, perceiving them as ego-boosting practices. My feeling is that they’re personal, hence why I keep them to myself.

Finally, I stopped sending out newsletters a while ago, deleting the Mailchimp account as a consequence. I’m not against them, however there’s been a deluge in recent years. I prefer to offer a full-text RSS feed for the latest 20 posts, reducing the back-and-forth of “content” on the internet.


Related topics
DEGROWTH
INTERNET
PERSONAL
SUSTAINABILITY
WEB DEVELOPMENT
WORKFLOW