My "project time" this week (when I try to improve something about my business) was spent on investigating how to move from our current blog generating tool, hugo, to @stefano's BSSG.
-
I am writing it as I go along.
I have some bits I need to figure out first (like how best to deal with editing the header template).
-
My "project time" this week (when I try to improve something about my business) was spent on investigating how to move from our current blog generating tool, hugo, to @stefano's BSSG.
So far, so good! I'm not quite ready to switch over just yet, but it has been pretty straightforward so far.
@neil @stefano I went from Wordpress to Github pages w/ Copilot.
I'm dirty but it's free and I can just use an agent to write a post for me as I provide an agents.md file to outline my writing style: https://github.com/JohnMcLear/blog/blob/main/agents.md#writing--engineering-style
-
S stefano@mastodon.bsd.cafe shared this topic
-
My "project time" this week (when I try to improve something about my business) was spent on investigating how to move from our current blog generating tool, hugo, to @stefano's BSSG.
So far, so good! I'm not quite ready to switch over just yet, but it has been pretty straightforward so far.
@neil That's great! Please note that the unreleased master branch includes a very effective RAM-only build mode, which makes things significantly faster. Also, three new BSD-based themes are coming
-
@neil That's great! Please note that the unreleased master branch includes a very effective RAM-only build mode, which makes things significantly faster. Also, three new BSD-based themes are coming
This is an amazing tool - thank you!
"RAM" mode caused quite a lot of errors for me, so I switched to "normal" mode, and that is building fine.
Do you have any plans to add config parameters (to be used in the header template), for
<meta name="fediverse:creator" content="{{fedi-creator}}" />
or
<link rel="me" href="{{fedi_validation_account"/>
?
At the moment, I am adding them to the template without variables, meaning that I'll need multiple instances of BSSG, one per site
-
This is an amazing tool - thank you!
"RAM" mode caused quite a lot of errors for me, so I switched to "normal" mode, and that is building fine.
Do you have any plans to add config parameters (to be used in the header template), for
<meta name="fediverse:creator" content="{{fedi-creator}}" />
or
<link rel="me" href="{{fedi_validation_account"/>
?
At the moment, I am adding them to the template without variables, meaning that I'll need multiple instances of BSSG, one per site
@neil Interesting! Could you please send me the errors you had when using ram mode? So I can debug them.
Those config parameters are a good idea. I'm adding them to the templates, too - consider that the templates can be overridden per-project, in the project directory - so you can use the same BSSG installation as long as it points to different configurations (generated with ./bssg.sh init )
For example, I'm currently building the https://my-notes.dragas.net (my "reference" blog for bssg testing) with: ./bssg.sh build -f --config /home/stefano/sites/my-notes/config.sh.local --build-mode ram
Thank you for your precious feedback!
-
@neil Interesting! Could you please send me the errors you had when using ram mode? So I can debug them.
Those config parameters are a good idea. I'm adding them to the templates, too - consider that the templates can be overridden per-project, in the project directory - so you can use the same BSSG installation as long as it points to different configurations (generated with ./bssg.sh init )
For example, I'm currently building the https://my-notes.dragas.net (my "reference" blog for bssg testing) with: ./bssg.sh build -f --config /home/stefano/sites/my-notes/config.sh.local --build-mode ram
Thank you for your precious feedback!
> consider that the templates can be overridden per-project, in the project directory
Oooh, thank you. I had not identified this from the documentation, so thank you!
-
> consider that the templates can be overridden per-project, in the project directory
Oooh, thank you. I had not identified this from the documentation, so thank you!
@stefano I love the separate of tool from content, so that much I am already doing - but I had not realised that one could use per-project/directory templates too. I will experiment
-
@stefano I love the separate of tool from content, so that much I am already doing - but I had not realised that one could use per-project/directory templates too. I will experiment
@neil great. I love to separate tool from contents, too. It's much easier to keep things clean, this way.
-
@stefano I love the separate of tool from content, so that much I am already doing - but I had not realised that one could use per-project/directory templates too. I will experiment
@neil maybe you need to set the TEMPLATES_DIR="/home/stefano/sites/my-notes/templates" (for example) inside the config.sh.local in the project directory. I can't remember if I implemented it automatically or has to be set manually. Otherwise, you can override it at build time with --templates "dir"
-
@neil maybe you need to set the TEMPLATES_DIR="/home/stefano/sites/my-notes/templates" (for example) inside the config.sh.local in the project directory. I can't remember if I implemented it automatically or has to be set manually. Otherwise, you can override it at build time with --templates "dir"
-
@neil yes, exactly. It can also be specified in the config file. I'm not sure if it will automatically be used if a templates directory is created in the project folder. It was planned, but I can't remember if I already implemented it or not (can't check the code right now)
-
I now have a minimal theme, with dark mode support!
It is on a test URL, but if anyone fancies seeing what I'm doing with #BSSG (Bash Static Site Generator), here's where I am so far:
