💾 Archived View for alltext.umaneti.net › fronde › NEWS.gmi captured on 2024-07-08 at 23:40:41. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Fronde

Mar. 2024 - v0.5 release

This new release continues the stability work. However, it also comes with two new features, which should open new ways of improvement in the future:

Add support for packaged themes. This release comes with one original theme named "umaneti". More theme may be packaged in the future.
Add support for publishing website on Neocities[1]. This comes with a full rewrite of the publishing code. You can now use either the rsync backend or this new Neocities backend if you want to benefit from their nice and cheap static website hosting solution. You can read more about publication options in the documentation[2].

After a second thought, this release remove the support of Liquid tags while rendering custom org-options settings. This is to stay homogeneous with other org placeholders. Liquid tags are only expected to render internal/private templates.

[1] Neocities (HTTPS)

[2] the documentation

Nov. 2023 - v0.4 release

This new release 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 we worked hard to improve the coding.

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:

Improve Gemini support
Translate all console messages
Introduce a new onboarding command (`new' instead of `init') to follow other static website generator habbits
Rework tags and Atom feeds publication
Output full article body in Atom feeds
Announce each Atom feed in its related tag page
Move tag pages and Atom feeds /inside/ the related blog source. They are not shared anymore but specific to their source.

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;
}

📅

📝 Étienne Deparis with GNU/Emacs 29.4 (Org mode 9.7.6)

propelled by fronde