I hacked this together last year, and changing the rendering bits should be no trouble: https://github.com/rcarmo/azure-durable-functions-node-blog-...
The ideal tech stack for a personal developer blog in 2020
61–70 of 275 posts
Re: The ideal tech stack for a personal developer blog in 2020
#62Why reinvent the wheel? Use Wordpress/Ghost etc
Aren't Wordpress and Ghost heavy in a way that it has some number of CSS/JS that we don't need?
Re: The ideal tech stack for a personal developer blog in 2020
#63I've started using 11ty recently and can recommend it as a Jekyll on steroids (and maintained).
Re: The ideal tech stack for a personal developer blog in 2020
#64This is front end only so not really a complete stack.
What do you mean? It is Jamstack, you only need CDN to serve it.
Re: The ideal tech stack for a personal developer blog in 2020
#65Creating your own stack for your personal blog seems to be the modern-day equivalent to creating your own programming language: it's a huge time sink with virtually no sane justification, yet developers are drawn to it like moths to a flame.
Like creating your own DSL, or programming language, or game engine lol. It is the fun that counts.
Re: The ideal tech stack for a personal developer blog in 2020
#66Earlier quoted context omitted.
HERESY! The only true path is mine, I write .htm files in vim and serve them with nginx. Yes, I agree, cloudyelling or not, no stack is better. I recall in my teenage years, I built 2 or 4 "CMS" in PHP/MySQL, at the end, added all that AJAX when browsers blessed us with the possibility of making HTTP calls from JavaScript! But in the end, migrating from server to server, learning more about everything, the only thing…
Nginx? Why not busybox httpd with OpenSSL sconnect? So much bloat. :p
Hmm, you're right, but I do use the nginx as reverse proxy for some of the other sites which are not static :P
I'm also running everything in docker containers, so I'm closet-hipster I guess xD
Re: The ideal tech stack for a personal developer blog in 2020
#67Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet. Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".
I write something like HTML and process it with m4.
Re: The ideal tech stack for a personal developer blog in 2020
#68Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet. Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".
There's nothing wrong with that approach tbh; when you think about it, the only reason to make a dynamic website is to prevent duplication, things like headers, menus, styles, etc. But there's ways around that, like frames.
as a non web developer who needed to get a static site with a consistent header and footer up I just made a makefile which watches an src directory and cats the header and footer onto each file
Re: The ideal tech stack for a personal developer blog in 2020
#69Earlier quoted context omitted.
I'm looking in to Jekyll as well, since it's what github recommend and I really can't be bothered with templates and re-learning all web stuff when all I need is to be able to write text and show pictures. Haven't really gotten started with it, but I wonder where the limitation of the tool will be felt? Do you need to know Ruby and the things around it too? I were thinking of also suggest it to my SO who have past ex…
> but I wonder where the limitation of the tool will be felt I use it and I don't feel any limitation. One can always add Javascript (AFAIK) if they want new functionality. What bothers me is that adding new functionality should be attempted first in the idiomatic (for the platform) way, which in the Jekyll case, is the Liquid language. I personally don't like it, but it's not a big deal to add small features (e.g. t…
thanks for the feedback! If JS can be done (and from a quick look css html and basic stuff is there), I guess I can also recommend it to my SO :)
Re: The ideal tech stack for a personal developer blog in 2020
#70Ideal may be a bit strong, but I'll assume it's ideal for Colin (author.) Learning is a big part of it, but so is familiarity.
I just started the same type of project: a personal website with a homegrown framework that makes everything easier. It was hard! Picking these technologies with no constraints and imperfect knowledge is tricky. Ultimately, I went with tools I wanted to learn more about, but that I was pretty confident would get me to a static site.
This ended up being webpack + loaders/plugins (some homegrown). Plus I'm writing content in Google Docs and exporting it to HTML after being inspired by the wave of Google Docs articles on HN.
Like Colin, I eventually want to put animations or data transformations on there. Fun process.