Live data from Hacker News

Why You Should Write Your Own Static Site Generator

arne.me

131–136 of 136 posts

Re: Why You Should Write Your Own Static Site Generator

#131

I recently had to nuke the Linux environment where I had my Jekyll environment finely tuned (Ran it on Debian WSL). Then I realised I had to reinstall Ruby, but the current Jekyll version (or the gems I use) uses a version that needs to lock OpenSSL at a certain version because of some breaking changes. Tried to lock the version in Debian and I was having a really hard time. Then I realised I just could grab the late…

If you used Go (or something equivalent) couldn’t you bundle it into a binary and then it can be more portable?

Re: Why You Should Write Your Own Static Site Generator

#132

I see a lot of people building their own static site generators. There's probably a lot of common elements to the process, right? We should abstract those commonalities into a static site generator generator, so that everyone who needs to write a static site generator doesn't need to reinvent the wheel.

There are a few that take that approach, but people usually want one in their preferred programming language/runtime. Examples: Metalsmith (Node/JS): https://metalsmith.io/ Haunt (Guile Scheme): https://dthompson.us/projects/haunt.html I’m sure there are many more.

A while ago you were looking at small languages such as lua - there's also micropython. https://docs.micropython.org/en/latest/

Re: Why You Should Write Your Own Static Site Generator

#133

I recently had to nuke the Linux environment where I had my Jekyll environment finely tuned (Ran it on Debian WSL). Then I realised I had to reinstall Ruby, but the current Jekyll version (or the gems I use) uses a version that needs to lock OpenSSL at a certain version because of some breaking changes. Tried to lock the version in Debian and I was having a really hard time. Then I realised I just could grab the late…

If you used Go (or something equivalent) couldn’t you bundle it into a binary and then it can be more portable?

It's good to have a binary that you can run, but you'd still have to deal with Go dependencies at build-time, and Go dependencies sometimes can go sideways as well (probably not as bad as Ruby, though)

Re: Why You Should Write Your Own Static Site Generator

#134

Earlier quoted context omitted.

But if you write a static site generator, you can blog about it. And that can be the first and the last post of your blog. If you don't write one, the chance is good, your blog would stay empty.

This is the perfect summary all the setups people have, with lots of "wow, I feel personally attacked" included: https://rakhim.org/honestly-undefined/19/

Nice. Your comics are rather amusing.

Re: Why You Should Write Your Own Static Site Generator

#135

Earlier quoted context omitted.

If you used Go (or something equivalent) couldn’t you bundle it into a binary and then it can be more portable?

It's good to have a binary that you can run, but you'd still have to deal with Go dependencies at build-time, and Go dependencies sometimes can go sideways as well (probably not as bad as Ruby, though)

Yes, build time will still be an issue. Hopefully if you get to a point where you’re “happy” with the binary you can avoid build issues for a while

Re: Why You Should Write Your Own Static Site Generator

#136
post #102

I made a website that does all the markdown to html conversion right on the client and it still has great SEO. Apparently google and stuff will just index the markdown itself. No compilation step needed.

Yara very interesting! I'm thinking about doing it but was worried about SEO. Doea it load, parse and draw the content fast?

Performance = 73

Best Practices = 95

SEO = 90

and that's using the marked.js library

Post reply on HN