The ideal tech-stack for a website? There’s no such thing. Ideal things don’t exist in real life, but opinions do. And here’s mine.
Content management
Don’t have a favorite CMS (content management software) and maybe I’ll never have one. None of them made a lasting impression. As you may have read in my previous post this site does use WordPress but this is no way an endorsement of it. The choice was strictly influenced by market share. High market share means high usage. High usage usually translates to better support. Support is crucial, especially when you’re building and managing your site on your own.
If someone put a gun to my head I might choose
the filesystem to manage my content. You
know, files, folders, the trash can and such. It’s much
more available and familiar to everyone than anything else.
There’s not much support needed to use it either. Sounds
ideal, right? Hard to argue with all that. But there’s a
catch. The filesystem isn’t strictly
speaking a web-content management system. It lets you manage
the files you’ll need to create a website but
you’ll still need to format those files as
HTML, CSS and JS.
Unformatted, raw text files just won’t do. Browsers need
a rich text format to be able to render your content the way
you’d like it to look.
In short, when it comes to CMS, it doesn’t really matter what you use. It just shouldn’t get in your way.
Content authoring
Writing posts or creating content is actually a job description. Copywriters are paid to do that and they deserve it. It’s hard to create useful content. Popular content is even harder to come up with and what you post on your website will make the difference between it becoming a hot zone or an abandoned graveyard.
As it may be apparent I do not have copywriter qualifications
but I’ve written texts before so I do know letters,
words and sentences and I can attempt to combine them into a
coherent blog post. It’s never going to be as
professional as paid content but it’ll have to do. All I
need to figure out now is what tool to use to create those
HTML files. And the list is endless. Could never
review them all.
To simplify things we can take a look at the
two types of HTML editing software:
the what-you-see-is-what-you-get editor
(WYSIWYG) and
the integrated development environment
(IDE). The first is easy to use but might
offer inconsistent results, the second is hard to use but will
give you consistency. The first might limit you to the editors
functions, the second gives you power to do whatever (even
stupid things). The first is like writing a document in your
favorite Office suite, the second is like programming.
It’s hard to choose a favorite with so many things to
consider and it feels like it would be wrong to choose a
favorite. In my daily work I use an IDE because people pay me
to write code (not content). But the content of this website
was written in WordPress’ built-in WYSIWYG editor
because by creating my own online presence I suddenly became
an amateur copywriter and didn’t have time to write
HTML in an IDE anymore.
So author your content using the easiest tool you can put
your hands on that spits out HTML,
CSS and JS.
Hosting
Simple. Whatever is free or cheap, easy to use, secure but also stable and reliable. And there’re too many hosting services out there to mention. And there’re too many pricing schemes out there. It’s just too much. So actually it might not be that simple.
This site is what you might call a static web page. This makes choosing a hosting provider a somewhat easier task because all this site needs is some storage and a domain name. These types of sites even have a preferred tech-stack, the JAMStack. There’re quite a few jamstack compatible and dedicated services on the internet. The great three (AWS, GCP and Azure) all support these types of sites and they cost close to 0 dollars to host.
This site is hosted on GitHub Pages as you
might have read in
my previous post
and hosting it there cost me 0 dollars. It was absolutely
free. GitHub gave me a subdomain for free:
szilvesztercsab.github.io. As a developer it made
sense to use GitHub Pages to host my own site. GitHub is
slowly becoming the facebook and the linkedin of developers
and techies. Tech people spend a lot of their time around
there and most of us are intimately familiar with their
offering. But if suddenly GitHub would make it harder for the
average developer to host a static site, people would be
migrating in mass to other similar platforms.
So hosting doesn’t matter much either but knowing how many free solutions there are on the internet you’d be negligent not to consider them.
In conclusion
The best tech stack for the web (in my opinion and particularly for these types of websites) is the JAMStack. And it always has been.
After all, the first ever web page also was and still is static. Check it out: http://info.cern.ch/hypertext/WWW/TheProject.html.