Why a Static Site?

The Static Sites

Since the internet exists, web sites started as simple pieces of static text and images. Over time, technology has evolved and web sites have become more dynamic and complex, but I have always felt a special connection with the simplicity of static sites.

Just think, in the 90s there were about 56 kbps connections, and web sites were mainly static. Despite bandwidth limitations, these sites were able to provide valuable information and a satisfying user experience. The simplicity of static sites has inspired me to create my own personal website using this technology.

Or rather, if you just need some text or an image, why complicate things with a dynamic site? If you wanted to see a photo, read an article, or simply get information, a static site is more than enough. But here enters an inconsistency with my story...

Hey, but you're using Flask? That's not a static site...

You've caught me, it's true. Although my personal website is primarily static, I use Flask to handle some dynamic functionality, such as the contact form and dynamic content generation for certain sections. However, most of my site's content is static, which allows me to maintain the simplicity and efficiency that I value so much in web sites.

According to GitHub... More than 53% of the code is pure HTML, I think that's a good indicator that my site is primarily static, albeit with some dynamic functionality added to improve user experience.

Anyway, the simplicity and efficiency of static sites remains a fundamental part of my web development philosophy.

I would love to use this page corporately, but of course it's too modest for that. The problem isn't the technology, it's people and their trends, like little lambs following what's fashionable, even if it's not best for them. Anyway, to each their own style. I prefer the simplicity and efficiency of static sites, and that's what inspires me to create my own personal website using this technology.

Back to Philosophy

Back Home