what's the advantage of a static site generator over pandoc + makefile?
Huh? What’s the advantage of a car over a Toyota Camry?
Moving from WordPress to Jekyll (and static site generators in general)
11–20 of 60 posts
Re: Moving from WordPress to Jekyll (and static site generators in general)
#12I have a legacy WP blog that I wanted to migrate to some static architecture for ages but IMHO users should be able to comment and maybe even post a pingback. I know, old MT days. But social media is always about getting (positive) comments and feedback, not just dropping statements and knowledge. I also don't want to tie my site to disqus or other 3rd party cloud services and their implication on GDPR.
A buddy found Cusdis - a self-hostable Disqus alternative: https://cusdis.com . But this only does comments, no pingbacks - and via a separate product that you need to integrate using JavaScript.
And running this opens you up to security issues you were trying to avoid by going the SSG route. In a way you could just keep WP, then.
(Also, WP has this beautiful ActivityPub plugin that makes your blog a fediverse account that people can subscribe to and even comment on your posts from Mastodon/Pleroma/etc.)
Re: Moving from WordPress to Jekyll (and static site generators in general)
#13Re: Moving from WordPress to Jekyll (and static site generators in general)
#14I don’t get it. Their setup is so much more complicated and limiting than what they had on Wordpress. I won’t argue with their reasons to move (which don’t stack up for me either but agree to disagree).
[dead]
Re: Moving from WordPress to Jekyll (and static site generators in general)
#15what's the advantage of a static site generator over pandoc + makefile?
I’m using Jekyll for includes and so I can use Ruby to render pages from yaml data. I’m sure Pandoc can do this too one way or another but it’s dead simple out of the box in Jekyll.
I mean, it’s tempting though.
Re: Moving from WordPress to Jekyll (and static site generators in general)
#16I feel this article is more about all the tools they built with AI than about moving to Jekyll. None of these tools required the move in first place, since they could have literally just dumped the DB.
Re: Moving from WordPress to Jekyll (and static site generators in general)
#17I did something similar, but killed my old WP blog. played around with 11ty, sveltekit, i eventually settled on hugo.
Re: Moving from WordPress to Jekyll (and static site generators in general)
#18Wordpress is better because it's easy to setup these days, can be fast if you enable caching, and has a comment system, which is a big deal if you want people to interact with your content. Other things like contact forms can easily be added. The CMS is also amazing.
With SSGs, you have a few options for comments, like Disqus, but the ad-free version costs money, it's slower because it needs to load JS, and your comments are owned by a third party company. Contacts forms can be built by integrating an external API. And anything else that requires storing data will require an integration with a third party service of some sort.
SSGs are a great concept but they're mostly for nerds who get boners by seeing over-engineered systems. They're also great for companies like Cloudflare because they can sell you services that come for free with Wordpress (CMS, image uploads, databases, workers, etc). For serious blogging, I'd opt for Wordpress.
Re: Moving from WordPress to Jekyll (and static site generators in general)
#19[deleted]
Re: Moving from WordPress to Jekyll (and static site generators in general)
#20Well, I migrates from wordpress to... Google Sites recently so...