Being a web developer seems to be increasingly popular as we reach “critical web” where creating a website is a introductory activity for many. Entry Level Bootcamps mostly teach students to become web developers.
Understanding Business Needs
Business needs generally come first when a webpage is being built. But, there may also be exceptions to rules of thumb simply because the business needs dictates it.
Option 1: Use Static Site Generators
My favorite example of a static site generator is Hugo which I used to make this blog. I really like Hugo for this because it’s crazy fast, written with Go, and it’s got great hot-reloading to see changes as they are made. Themes seem very customizable and their documentation is really exceptional.
Option 2: Server Side Rendering
Server side rendering is generally slower than static site rendering because the server spends time building the webpage. It also requires a dedicated server rather than a Content Delivery Network (CDN) where the site can be served from. Dedicated servers generally cost more and require maintenance.
Option 3: Blunt Force
Every page has it’s own separate files and I’m OK with repeating myself. This is not a good path and it leads to significant tech debt. Look up the DRY Principle.
What does Ben use?
Static Site generation seems like a good tool for me to use because it’s simple to host and update. I’m working on spinning up a documentation website for web developers and I find a lot of advantages to making the documentation as easy to consume as possible.
Ultimately it depends on what I’m building.
I’d like to add that I improved this article by following guidelines found in Scott Adam’s article “The Day You Became a Better Writter”. I suggest you give it a read