Eyy, that’s me! Good excercise to learn actual HTML, instead of directly trying to jump into <insert random JS framework> and getting confused on what’s what.
Anyway, I ended up switching to Hugo as a static site generator, because it was too damn hard to keep all my <header>, <nav> and <main> aligned for all my HTML files.
Now I can just write a markdown file as an article, or switch back to raw HTML if I so need (like rewriting Alan Turing’s paper " On computable numbers" in HTML because I can’t use TTS on the PDFs I found; I still haven’t finished writing it, because I am now reading E. F. Codd’s papers on the Relational Model, which is pretty wild how we already figured that shit out in the 1970s!)
Presumably because we let them by continuing to use their products. It’s definitely bullshit though - every time I log into a site I managed my dashboard is littered with notification banners. Most are legit notifications (albeit there should be a proper log for that), but the actual ads for plugins are maddening.
Yeah, everyone with a decent amount of content will just pick Wordpress and move on. It works, it’s reliable, it’s well supported and will keep running for decades at least.
And once you have found your specific collection of plugins that happen not to put the exact features you need behind a paywall but others, you ain’t touching those either.
And once you have found your specific collection of plugins that happen not to put the exact features you need behind a paywall but others, you ain’t touching those either.
And this is why, when I’m investigating phishing links, I’ve gotten used to mumbling, “fucking WordPress”. WordPress itself is pretty secure. Many WordPress plugins, if kept up to date, are reasonably secure. But, for some god forsaken reason, people seem to be allergic to updating their WordPress plugins and end up getting pwned and turned into malware serving zombies. Please folks, if it’s going to be on the open internet, install your fucking updates!
That or you develop your theme with the features you need baked in. This is the irony of the Hugo people, they’re capable developers that can make themes but they can’t just create a simples Wordpress theme from the ground?
Yeah actually writing Wordpress themes was easier than I thought. But I wrote them for the old editor, not Gutenberg – I opted for ClassicPress instead which was quite a banger in the effort-to-outcome equation
There isn’t much of a difference between writing a theme for Guthemberg and the classic editor. In fact your current theme should work just fine in Guthemberg as it just adds the extra html for the built in blocks to your posts / pages. You aren’t required to create a block based theme and split everything into blocks, that’s kind of a myth around Guthemberg.
Are there? I think they’re super handy for just… Having information. Easily discoverable by search engines, and much more coherent than following a forum thread.
I hate how oddly specific “Moved from Jekyll to Hugo people” is, mostly because that’s exactly what I did as well. I don’t use it to write any blog posts though. It’s more a “Here’s a list of things I’ve created”-generator.
I made a static site with Hexo a few years back. I thankfully didn’t make any “Get started with Hexo” posts but I did only really use it for a few months. I think that puts me in the cluster with the “switch from Jekyll to Hugo” people. Now it just sits there, absorbing some money every two years for the “personal website tax”.
Shame too, I constantly think I need to get back to it. Hexo is nice, popular with Chinese users I think. I don’t recall now why I liked it over Jekyll or Hugo, but I’ve always loved an underdog. Once I got the hang of using it, it was very customizable and fun to work with.
I think the “Moved from Jekyll to Hugo” dot has an implicit catchment area around it, which includes people who don’t technically fit that description, but they’re close. I’ve used neither Jekyll nor Hugo, but the fact I understood that archetype meant I felt pulled in by the gravity of that point.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Eyy, that’s me! Good excercise to learn actual HTML, instead of directly trying to jump into <insert random JS framework> and getting confused on what’s what.
Anyway, I ended up switching to Hugo as a static site generator, because it was too damn hard to keep all my <header>, <nav> and <main> aligned for all my HTML files.
Now I can just write a markdown file as an article, or switch back to raw HTML if I so need (like rewriting Alan Turing’s paper " On computable numbers" in HTML because I can’t use TTS on the PDFs I found; I still haven’t finished writing it, because I am now reading E. F. Codd’s papers on the Relational Model, which is pretty wild how we already figured that shit out in the 1970s!)
I have to say, I’m so over WordPress that those static site generators are looking pretty sweet right about now.
I went with eleventy and pure markdown files and I never looked back.
I say this as a person who loves WordPress and contributes to the open-source project.
Pshaw… just write it in raw HTML. It’s an incredibly legible markup language. I talk to my spouse in HTML just to stay sharp.
I just write all my blog posts inside the empty line of this:
Keep it simple, stupid!
Right? I’m tired of my admin dashboard being a wall of plugin advertisements (especially from plugins I already pay for).
Omg the ads. How are they even allowed to get away with that?!
Presumably because we let them by continuing to use their products. It’s definitely bullshit though - every time I log into a site I managed my dashboard is littered with notification banners. Most are legit notifications (albeit there should be a proper log for that), but the actual ads for plugins are maddening.
Yeah, everyone with a decent amount of content will just pick Wordpress and move on. It works, it’s reliable, it’s well supported and will keep running for decades at least.
Yea but the S in PHP stands for security
And once you have found your specific collection of plugins that happen not to put the exact features you need behind a paywall but others, you ain’t touching those either.
And this is why, when I’m investigating phishing links, I’ve gotten used to mumbling, “fucking WordPress”. WordPress itself is pretty secure. Many WordPress plugins, if kept up to date, are reasonably secure. But, for some god forsaken reason, people seem to be allergic to updating their WordPress plugins and end up getting pwned and turned into malware serving zombies. Please folks, if it’s going to be on the open internet, install your fucking updates!
Because updates also add paywall, which is worse than hackers! /s
That or you develop your theme with the features you need baked in. This is the irony of the Hugo people, they’re capable developers that can make themes but they can’t just create a simples Wordpress theme from the ground?
Capable developers don’t touch PHP ;)
(sorry, couldn’t help myself. I love WordPress, but I don’t much love its innards or the language…)
Capable developers touch whatever language is required to get a job done.
There’s always more than one option and it is rare situation when a language is “required” .
Yeah actually writing Wordpress themes was easier than I thought. But I wrote them for the old editor, not Gutenberg – I opted for ClassicPress instead which was quite a banger in the effort-to-outcome equation
There isn’t much of a difference between writing a theme for Guthemberg and the classic editor. In fact your current theme should work just fine in Guthemberg as it just adds the extra html for the built in blocks to your posts / pages. You aren’t required to create a block based theme and split everything into blocks, that’s kind of a myth around Guthemberg.
Damn that’s cool, then maybe I should take a second look at Wordpress
There are too many blogs and posts.
I wish there was one about vegan pizza 69 though
there’s no /c/veganpizza yet, but there is /r/veganpizza
Are there? I think they’re super handy for just… Having information. Easily discoverable by search engines, and much more coherent than following a forum thread.
Shouldn’t that X axis really be “percentage” instead of “number” for this to make any sense at all?
Alternatively the y axis could be “blog posts not about …”
I set up my site with Jekyll this year, and I have one blog post about how to set up a Jekyll blog.
I hate how oddly specific “Moved from Jekyll to Hugo people” is, mostly because that’s exactly what I did as well. I don’t use it to write any blog posts though. It’s more a “Here’s a list of things I’ve created”-generator.
I made a static site with Hexo a few years back. I thankfully didn’t make any “Get started with Hexo” posts but I did only really use it for a few months. I think that puts me in the cluster with the “switch from Jekyll to Hugo” people. Now it just sits there, absorbing some money every two years for the “personal website tax”.
Shame too, I constantly think I need to get back to it. Hexo is nice, popular with Chinese users I think. I don’t recall now why I liked it over Jekyll or Hugo, but I’ve always loved an underdog. Once I got the hang of using it, it was very customizable and fun to work with.
I think the “Moved from Jekyll to Hugo” dot has an implicit catchment area around it, which includes people who don’t technically fit that description, but they’re close. I’ve used neither Jekyll nor Hugo, but the fact I understood that archetype meant I felt pulled in by the gravity of that point.
read it as yesterweeb
My blog posts went up 3∞ once I dumped jekyll for a premade blogging site
As the author of an obscure static site generator. I feel called out.
My personal blog currently has one (1) post. It’s about how to get started blogging with my SSG. Oops.