Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The ideal tech stack for a personal developer blog in 2020

vriad.com

Post reply on HN
Print view View original

31–40 of 275 posts

Re: The ideal tech stack for a personal developer blog in 2020

#31

Post by NalNezumi »

ferros wrote: post #5

Personally I work in tech all day, I want my blog to be as simple as possible and to focus just on my writing. Still using Jekyll.

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 experience in web design but no programming skill at all (I can at least set up her github account). My guess she would be more picky with how the page looks though.

Re: The ideal tech stack for a personal developer blog in 2020

#32

Post by nicoburns »

DJHenk wrote: post #10

A personal blog should be whatever the author wants it to be of course, and a developer should play with whatever technology he/she wants. But as a backend developer, I don't want any Javascript on my site, because I hate writing it and I don't like browsing it. These statements indicate to me that this "ideal tech stack" is rather personal to the author: > I want to build the site in React and TypeScript > I don't w…

As a full-stack developer who spends a good proportion of my time at my day-job working with React, I totally agree. My personal website is Hugo, and entirely JavaScript free.

Re: The ideal tech stack for a personal developer blog in 2020

#33

Post by mhh__ »

jasode wrote: post #25
clarry wrote: post #3

> I worry that many developers (maybe even you, dear reader) are settling for suboptimal, restrictive static-site generators that place limits on the interactivity and flexibility of your website. I wonder what sort of interactivity you want on your text? > This degrades page load speeds and user experience, which accordingly degrades your rankings on Google. Instead I want every page of my site to be pre-rendered to…

>I wonder what sort of interactivity you want on your text? In case you glossed over it, I think he said it in his post: "But down the road, I may want to build a page that contains an interactive visualization, a filterable table, or a demo of a React component I'm open-sourcing."

Isn't all of that done client side i.e. still possible with a static site?

Re: The ideal tech stack for a personal developer blog in 2020

#34

Post by dusted »

encom wrote: post #6

Here'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".

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 that seems somewhat stable are plain text or pure html. I know I can edit them in 2000 years, if I am still alive by then.

Re: The ideal tech stack for a personal developer blog in 2020

#36

Post by pizza234 »

soygul wrote: post #19

For a techy person, GitHub pages + markdown is all you need: https://quanticdev.com/articles/website-with-github-pages When you already know Git & GitHub, you get an all-in-one experience with your code & website side by side.

I'd add to use Jekyll now (https://github.com/barryclark/jekyll-now) for a few more out-of-the box conveniences. Sadly, it's unmaintened, but the it gives a sufficient base as-is.

Re: The ideal tech stack for a personal developer blog in 2020

#37

Post by rlayton2 »

mhh__ wrote: post #33
jasode wrote: post #25

Earlier quoted context omitted.

>I wonder what sort of interactivity you want on your text? In case you glossed over it, I think he said it in his post: "But down the road, I may want to build a page that contains an interactive visualization, a filterable table, or a demo of a React component I'm open-sourcing."

Isn't all of that done client side i.e. still possible with a static site?

Even if you need a data API - if its just a demo (or slow moving data), you can just directly serve .json files.

Re: The ideal tech stack for a personal developer blog in 2020

#38

Post by orwin »

hawkice wrote: post #7

As a non-React developer: forms, before React, were actually super simple. The author mentions they forgot how to do forms the normal way, but like, can you imagine how excited they'll be by the simplicity?

i think (but i'm not sure) that this blog post is a joke?

Re: The ideal tech stack for a personal developer blog in 2020

#39

Post by NewEntryHN »

encom wrote: post #6

Here'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".

It becomes more complicated as soon as a you have a sidebar with "Last articles" in which case you would need to edit each single HTML files to edit the sidebar consistently. Even with a single archives page you need to think about updating the archive for each new article. Also Markdown is definitely more author-friendly than HTML, but that's more like an extra.

Re: The ideal tech stack for a personal developer blog in 2020

#40

Post by ferros »

NalNezumi wrote: post #31
ferros wrote: post #5

Personally I work in tech all day, I want my blog to be as simple as possible and to focus just on my writing. Still using Jekyll.

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…

It’s much like Wordpress in the sense that you can get it up and running very quickly. The time cost is in how much you want to customise it.

Once it’s set up it’s just markdown, no ruby required.

Post reply on HN