Scans to see how he is dealing with native comments... Realises the issue remains unsolved, along with 99% of ’CMS’ solutions...
Continues with Wordpress.
The ideal tech stack for a personal developer blog in 2020
101–110 of 275 posts
Re: The ideal tech stack for a personal developer blog in 2020
#102This is so strange - I am on course to build my own developer blog with a similar stack (minus TypeScript, and syntax highlighting).
I am also using a CMS instead of just plain markdown - in this instance it is NetlifyCMS.
Netlify CMS is the perfect go-between of a fully-fledged CMS, and a much too basic static site with just markdown - I dislike the experience of writing markdown and would rather use an editor.
With NetlifyCMS - the blogging flow is as follows:
- User logs into NetlifyCMS
- User updates content
- Content is 'pushed' to the repo as a commit.
- CI / CD picks up changes on master branch
- CI/ CD publishes changes
- The site is updated!
The example code can be found here: https://www.netlifycms.org/docs/nextjs/
It is extremely simple to get up and running - but also offers great flexibility if, as the author has stated, you wish to use your website to demo components - visualise data, anything custom really!
The only difference with my implementation is instead of using the `public/` folder, I created an 'admin' folder within 'pages', with an index.js file for the HTML contents, as referenced here: https://www.netlifycms.org/docs/nextjs/#adding-netlify-cms. The only reason being, I didn't want to have to specify '/admin/index.html' every time i want to edit the content.
My only gripe with this blog post - is its insuniation that it is 'ideal'. I think its pretty clear from the post, it is only 'ideal' for the author. Unfortunately, the HN community has taken the opportunity to rip apart the authors opinion - which is disappointing. Thanks for the content, Colin!
Re: The ideal tech stack for a personal developer blog in 2020
#103A 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…
Came here to say Hugo is the correct answer for a Personal Developer blog, unless you're using it to showcase your skills in a particular technology, at least in my experience.
Finally dived into Hugo and it's just so easy to get going with making Markdown content and turning it into a static site with one of the themes from their gallery. There's a bit of a rabbit hole to go down if you want to get more custom than that, but it's extremely customizable and you can learn a lot about how to do so just looking at the source code from themes in the gallery.
The only tech I really have to worry about is HTML, CSS, Markdown, and a little bit of template scripting for ranges and reading variables from the config files, if I want to customize the theme.
I've gotten excited about building my personal website again because I don't have to screw around with the technology hardly at all, I can focus on just making content. Which is what you want for a personal site. You don't want a bunch of friction slowing you down from actually getting content out there.
I don't have to worry about dependency hell with Hugo either, it's just an executable.
Re: The ideal tech stack for a personal developer blog in 2020
#104This setup is going to lose its sheen really quickly when every attempt at writing a blog post also accompanies three hours of npm package bumps
> Three hours of package bumps
It takes less than ten seconds to type `npm update`.
Re: The ideal tech stack for a personal developer blog in 2020
#105Authors first requirement is
“I want to build the site in React and TypeScript. I love them both wholeheartedly, I use them for my day job, and they're gonna be around for a long time. Plus writing untyped JS makes me feel dirty.”
That preference is not true for others and I feel like that makes the article’s title misleading.
Re: The ideal tech stack for a personal developer blog in 2020
#106Earlier quoted context omitted.
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...
Another option is to use cat and a shell script or Makefile, or I guess some people use m4.
I use a makefile that runs a short python script, very simple
Re: The ideal tech stack for a personal developer blog in 2020
#107I'm quite surprised by the negativity here. If I was commissioned to make a custom blog site for someone, I would probably go down this route, and use a headless CMS to make it easier for others to generate content. But using plain markdown is not a bad choice if you can't be bothered with, or can't afford a server. With the stack described as I understand it, the front-end flexibility is preferable to what the likes…
FWIW I just finished building a (very) basic blog using Gatsby (which is based on React) and SEO scores are fine. Accessibility should also be achievable, though I find that failures in that regard are usually due to developers not caring/having deadlines instead of a lack of available tools.
Re: The ideal tech stack for a personal developer blog in 2020
#108I recommended this on another HN post a few weeks ago: use Emvi [1] to write your blog articles and access them on your personal page on a server you control through the API to display them. You can store the HTML and attached files to serve it statically and update it from time to time. Should you decide to abandon Emvi you still have everything in place. I did this for a gaming community wiki (sort of, I don't store articles on the webserver). The main advantage is that your site is literally just a dumb frontend and uses Emvi as a headless CMS and the editor experience is nice. You can take a look at it [2] and the source code on GitHub [3].
Re: The ideal tech stack for a personal developer blog in 2020
#109The other day I started an HTML document from scratch, in VSCode.
I kinda blacked out and came to 5 seconds later, and thanks to autocomplete and muscle memory, the whole skeleton of a document was there. HTML and Head and title and body and all that. It was so fast & fluid.
I'm ashamed to say I'd kinda forgotten how easy it is to just write fucking HTML. It's even got me reconsidering things like Markdown—I mean, fine for webforms and such, but if I'm just writing a document, is it of any use? Toss in a script to add a menu & header to every page & dump the output in a folder and I'm not sure I need more, now, and I can write that in Perl or Bash or Python or whatever in a minute or three and it'll run everywhere, nothing to install.
Re: The ideal tech stack for a personal developer blog in 2020
#110I'm quite surprised by the negativity here. If I was commissioned to make a custom blog site for someone, I would probably go down this route, and use a headless CMS to make it easier for others to generate content. But using plain markdown is not a bad choice if you can't be bothered with, or can't afford a server. With the stack described as I understand it, the front-end flexibility is preferable to what the likes…
As another user mentioned, Next.js has a 'next build' command that creates a HTML build at build time. But it also provides server-side rendering by default.
Next.js also provides a very useful function: getStaticProps. This function will be called at build time - and will provide your (now static) build with dynamic data! It's pretty cool.