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

71–80 of 275 posts

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

#71

Post by woutr_be »

jcpst wrote: post #11

I’m sorry, but this is ridiculous for a static site. React and Typescript with embedded markdown? This problem has been solved a thousand times over with much simpler tooling. > I literally have zero memory of how we used to build forms in the pre-React times. :(

> I literally have zero memory of how we used to build forms in the pre-React times.

This is honestly quite a disturbing trend with a lot of front-end developers these days.

I recently asked a front-end dev why they chose React for a simple app over simple server-side templating, he's reaction was "we don't need SEO, so why do we need React SSR", like how does that argument even make sense. They seem to have forgotten you can build stuff without a JS framework.

The default has to be SPA + API, even when you don't actually need it.

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

#72

Post by woutr_be »

nicoburns wrote: post #32
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.

Same here, even a lot of my personal projects are now just SPA free by default. I do use Node on the backend, but most of the time, a templating language like pug gives me everything I need.

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

#73

Post by [deleted] »

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…

[deleted]

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

#74

Post by johnonolan »

christiansakai wrote: post #62
sub7 wrote: post #4

Why 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?

Hi! John from Ghost here - Ghost has no bloated styles or scripts which are injected by default. You have full control of the frontend and can make it as minimal (or maximal) as you like.

My answer to the OP would be:

If you want to write (on a blog) then do literally anything but turn your blog into a development project that you'll definitely never finish - because it just becomes the excuse for not writing. (almost all developer blogs)

If you want a fun developer project to experiment with your personal website, and messing with new technology is the goal, then this stack sounds like a lot of fun. It also sounds like it will be obsolete and no longer shiny in 12 months, but again, if this is your goal then you probably don't care.

TLDR: developer tools will usually end up being great for development, publishing tools end up being great for publishing. Pick the one that suits your desired outcome best.

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

#76

Post by clarry »

frereubu wrote: post #48
NewEntryHN wrote: post #39

Earlier quoted context omitted.

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.

If you're using Apache, which he said he was, you can just use server-side includes: https://httpd.apache.org/docs/current/mod/mod_include.html#e...

In the distant past, we used client side includes. They were known as framesets.

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

#77

Post by flohofwoe »

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

I wonder if he actually tried embedding HTML into Markdown, because that's as simple and straightforward as it can be: just start writing HTML in the Markdown document, and after the closing element, continue with the markdown text. This should completely cover the requirement to embed interactive elements into markdown using a static site generator like Hugo or Jekyll without having to deal with an overly complex dependency like React.

Here's an example of embedding a WASM home computer emulator with just a few lines JS (and I'm not exactly a web development expert, so with a bit more knowledge and experimentation I'm sure this could be made much more fancy):

https://floooh.github.io/2019/01/05/wasm-embedding.html

Post reply on HN