๐Ÿ’พ Archived View for alltext.umaneti.net โ€บ fronde โ€บ NEWS.gmi captured on 2024-08-31 at 11:54:55. Gemini links have been rewritten to link to archived content

View Raw

More Information

โฌ…๏ธ Previous capture (2024-08-18)

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

News from Fronde

Jul. 2024 - v0.5 release

This new release continues the stability work.

The biggest improvement has been in the Gemini protocol handling, now allowing you to publish Gemlog with the same features as for the HTML blogs.

It also comes with two new features, which should open new ways of improvement in the future:

This release changes the way `i18n:' links are parsed by our private Org extension. Previously, they were stored as `i18n:https://example.com|en', but must now be stored as `i18n:https://example.com::en' (`::' replacing `|' to separate the URI from the lang tag). This is to be more homogeneous with `file:', `attachment:', and `id:' links, which also accept a suffix separated with `::'.

This release removes 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:

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.7)

๐Ÿก Back to home

๐Ÿš€ Propelled by fronde