Exciting update: I've switched to a #Mastodon-powered commenting system. You can now engage with my blog (#jekyll) by replying to corresponding posts right here on Mastodon. I believe, it offers a more conducive platform for constructive dialogues.
📝 Blog post: I have published post about my migration to #Codeberg, features guide on setting up redirect from GitHub and extended guide on setting up Codeberg pages with #jekyll
And its friends, CVE-2023-0667 and CVE-2023-0668, can be found nearby. All three are already fixed by the fine folks at @wireshark, because they're lickety-split quick.
We're also now publishing our reserved CVEs, and an explicitly CC-BY template if you also want to release public advisories like a bawss.
(Forgive the crummy table layout, it's ancient #Jekyll defaults. Patches accepted!)
is there any DRY way to indicate that a post has a previous or next chapter, and include prev/next links in the post?
I want to be able to post stories on my blog separated into chapters (one post per chapter) and have a set of prev/next links auto-generate. I was thinking of having prevPost and nextPost variables in the front matter, and then getting the URLs like this:
{% post_url page.prevPost %}
I've also tried this:
{% post_url {{ page.prevPost }} %}
unfortunately I'm pretty sure Liquid is trying to tell me that this won't work, and that post_url only takes a bare string - not a variable
My personal website has been using #jekyll for years, but I update it very infrequently, and every time I need to, some jekyll/ruby dependency or another has somehow broken or gotten out of date, and I have to dig around in docs to remember how to fix it.
It's getting real old.
Is there a better, simpler, lighter weight #webdev solution for #markdown based static sites these days?
I made a suuuuuper ez mode tutorial on deploying and maintaining a custom site for my friend that’s about to look for a job. I’m curious if y’all know of a better method than this that’s also free. Let me know 😊 https://jeffreylikeswebsites.com/posts/how-to-do-this/#jekyll#ruby
A response to @kev sharing my workflow, using #jekyll, #vim, #rofi and other tools to achieve the same thing. Plus some extra stuff people using any #ssg would find useful! Day 41 of #100DaysToOffload
If an actor provides an outbox URL, but not an inbox URL, it means that it cannot receive Follow activities and it can not push content to the followers. In such cases, the follower's server should switch to periodic polling like RSS.
This will enable statically-built blogs ( #jekyll#hugo etc) to appear in Mastodon network.