Does anyone have recommendation for a fairly basic blog system with (some of) these characteristics:
=> More informations about this toot | More toots from justvanrossum@typo.social
I came across this jekyll-based tutorial, and it seems to check all my boxes:
=> More informations about this toot | More toots from justvanrossum@typo.social
Another workable example/tutorial, using 11ty:
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum Eleventy reminds me of Robofont in that it doesn’t force you to do things a certain way or make a lot of assumptions. Very easily extensible and lots of great plugins. I just added RSS to my site and it was very simple.
My site is connected to a git repo and it’s hosted by Netlify on their free tier, works great
=> More informations about this toot | More toots from cjtype@mastodon.social
@cjtype I went through the 11ty "base blog" demo and I got it working in a few minutes, with a new blog post. I like it very much so far.
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum @cjtype Zach computered a great thing with 11ty!
=> More informations about this toot | More toots from pixelambacht@typo.social
@pixelambacht @justvanrossum @cjtype 🥰
=> More informations about this toot | More toots from zachleat@zachleat.com
@justvanrossum @cjtype Please post a link to your new blog when it’s stable! I will instantly susbscribe via RSS.
=> More informations about this toot | More toots from nicksherman@typo.social
@cjtype Getting it to run and adding some content was easy enough. Customizing the layout... not so much. For example I have so far completely failed to add an icon to the page header.
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum Hmm, I started by building everything in html and css and then copy/pasting things into template pages as needed. My templating was based on this boilerplate site: https://github.com/danurbanowicz/eleventy-netlify-boilerplate/
Most of my site templating happens in base.njk (from _includes/layouts/) and the is included like this: {% include "components/head.njk" %}
which references head.njk (from _includes/components/) where I copy/pasted the from my html file. Hope that helps!
=> View attached media | View attached media
=> More informations about this toot | More toots from cjtype@mastodon.social
@cjtype I have located the main template, and know where to store images, but the html way to reference the (svg) image doesn’t work. Googling njk img src does not give helpful results. I went from “easy to set up blog system” to “having to learn this huge system” and I already hate it.
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum If it's an SVG it could in theory be pasted inline, right?
Or for the normal way of linking to an image, I have this code in my eleventy config file: eleventyConfig.addPassthroughCopy("images");
(It might need to be"./images" depending on your setup). Then whatever I put in the "images" folder in my base directory will get copied into my "_site/images/" folder when the site is built.
Config file:
https://github.com/11ty/eleventy-base-blog/blob/main/eleventy.config.js
addPassthroughCopy info:
https://www.11ty.dev/docs/copy/
=> More informations about this toot | More toots from cjtype@mastodon.social
@justvanrossum ah wait, I just re-read your text and I may have misunderstood the issue. I'm far from an expert but if you want I could take a look at the repo and see if anything obvious jumps out
=> More informations about this toot | More toots from cjtype@mastodon.social
@cjtype Thanks!
In that config file /public/ is already pass through, and when I place an image in /public/img/ I do see that it gets included the output tree (https://blog.fontra.xyz/img/fontra-icon.svg), however, I can't seem to find how to reference that image correctly in _includes/layouts
/base.njk. https://github.com/11ty/eleventy-base-blog/issues/200
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum @cjtype That is the right way to include it, maybe it’s being served with an incorrect MIME type? otherwise there’s little that could get in the way...
=> More informations about this toot | More toots from db@typo.social
@justvanrossum @cjtype Ah, the eleventy blog starter has the image transform plugin set up, that’s doing a bit of magic under the hood, reprocessing tags.
=> More informations about this toot | More toots from db@typo.social
@db @cjtype so what should I do instead?
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum @cjtype the starter repo tries to be immediately useful, but automatically processing images across the board like that is too overreaching for my tastes and the magic can be confusing, so probably I would remove the image processing plugin for now, but that might require adjusting the images in your posts. As a quick fix, should do it: https://www.11ty.dev/docs/plugins/image/#eleventy-transform
=> More informations about this toot | More toots from db@typo.social
@db @cjtype Awesome, that workaround works!
(But... whyyyyyyyyyy)
=> More informations about this toot | More toots from justvanrossum@typo.social
@justvanrossum @cjtype (I’ll add a longer answer to your GH issue from the office)
=> More informations about this toot | More toots from db@typo.social
@db @cjtype When I do as described in the issue, the img src becomes http://localhost:8080/content/img/fontra-icon.svg
instead of
http://localhost:8080/img/fontra-icon.svg
This obviously does not work.
=> More informations about this toot | More toots from justvanrossum@typo.social This content has been proxied by September (3851b).Proxy Information
text/gemini
