This new release[1] brings a lot of stability improvements and inner refactoring. Even if the visible changes list might look a bit poor, this release is a big step forward and will help a lot to develop new features in the future. Some parts of the software were poorly designed and I worked hard to improve the coding.
I gave a code of conduct[2] to the project to ease any newcomer to feel at home when participating in it. I invented nothing and adopted the contributor covenant code of conduct[3].
After the update, you will need to update your installations and force a full publication of your websites (because the way templates are inserted inside published files changed). Actually, this will become the new standard routine after any fronde upgrade.
fronde update fronde build -f
Here is the list of the most visible changes:
As tags and feeds are now published under their related source public path and no more directly at the root of the publication folder, you might want to setup some redirections in your web server configuration.
For the following example configuration:
--- sources: - path: src/news is_blog: true
Feeds and tags will now be published under `public_html/news/feeds/' and `public_html/news/tags/' instead of `public_html/feeds/' and `public_html/tags/'. Thus you might want to setup some redirections like the following for nginx:
location ~ ^/tags/(?<slug>.*)$ {
return 301 /news/tags/$slug;
}
location ~ ^/feeds/(?<slug>.*)$ {
return 301 /news/feeds/$slug;
}
All changes are visible in the git log[4].
[3] contributor covenant code of conduct (HTTPS)
--
📅 jeudi 23 novembre 2023 à 08:55
📝 Étienne Pflieger with GNU/Emacs 29.4 (Org mode 9.7.11)