Replace the "official" text of the footer ("Proudly powered by Pelican,
which takes great advantage of Python.") with the simpler "Static site
generated by Pelican".

In all project descriptions, remove the unnecessary comma before the
last item of "installation, usage, and support".

In the screenshot of Unaltered, after the commands, display the content
of the directories (with "tree") to show the new checksums.sha256 file,
and display the content of the checksum file itself, to show its
standard format.

Replace "yellow" colour with "orange" for the removed file. This is the
way it is expected to look like in the terminal (although, of course,
this can depend on the terminal settings). I already had to change it
manually for Ondine, in the previous commit.

Add "screenshots" (terminal captures) for My Painted Shell and
Unaltered projects.

Mention that the captures taken with aha were always "slightly reworked
manually".

Change the colour of the track numbers in Ondine screenshot.

Keep the introduction simplified, yet try to give more details about
the motivation, just by using a few adjectives.

Use colourful (UK) instead of colorful (US), also in the description of
My Painted Shell.

Don't use a line block (| ) to describe the use of Pelican.

In the header, increase the font size from 0.9em to 1em (default).

Try to be more concise when explaining the motivations for creating
these projects.

Change the Gitlab user account URL to go directly to the "Personal
projects" page, instead of the "Activity" page.
The "Activity" page used to clearly list all personal projects as well,
but this is no longer the case.

Increase the size of the text in the header and footer, from 0.75em to
0.9em, and the height of the banners themselves, from 1.5em to 2em.

In page.html template:
* Replace the <h1> tag in the <header> block with a <p> (it makes more
  sense, and it helps simplify the CSS, since there is also a <h1> tag
  at the beginning of the <article> block).
* Add a <p> tag in the <footer> block, so that it is similar to the
  <header> block, and the style can be defined the same way for both
  banners (with margin, not padding).

Move the article margin-top into style.css, to avoid duplication in
index-style.css and project-style.css.

Use 3em for the top and bottom margins of the article, instead of the
values that were calculated as described in the comments.

Remove "whose content may evolve" at the end of the description of
Unaltered. It has already been modified in the project itself, just
before the 1.0.0 version.

In pelicanconf.py, declare the time zone (Europe/Paris) to fix the
following warning: "No timezone information specified in the settings.
Assuming your timezone is UTC for feed generation."

Rewrite the page.html template by copying and simplifying the "simple"
theme, instead of extending it.

With this method, we become independent of any unexpected evolution of
Pelican "simple" theme, which can change the structure of the HTML
document, and require the CSS to be adapted. This is what happened with
Pelican 4.9.1.

Remove DISPLAY_PAGES_ON_MENU option from pelicanconf.py, because it was
used only in the "simple" template, but I have removed it from mine,
when simplifying.

This new project, written in Rust, is a rewrite of "mychecksum" script
from My Painted Shell.

In spite of some corrections, the script still has issues with
filenames containing some special characters. This is clearly uneasy to
handle with shell scripting. The script will be removed later.

With Pelican 4.9.1, the structure of the HTML document has changed, so
the CSS rules must be adapted accordingly.

Pelican (installed with pip) fails to build the website with the CI
image version python:3.8-alpine.
Upgrade to the latest version (python:3.12-alpine).

Drop the Raindrop project, because I'm not going to use it anymore.
I've switched back to a paper agenda, which is the most convenient
solution for my personal usage.

Setting max-width was a good idea, but 80em is still a little bit too
large, and 60em looks better and improves readability.

The drawback is that Emacs-IDE screenshot needs to be resized,
otherwise it overflows on the right side.
NB: It could be centered (i.e. overflow on both the left and the right
sides) by applying the max-width property on body subnodes with
exceptions, instead of body itself, but it would become too complex,
and would depend on the way Pelican builds the HTML output.

Remove the left and right margins of the terminal capture (for Ondine),
so that it also fits the whole width.

Move the description of the purposes of my projects after the list,
because it makes more sense to first see what these projects do, before
discovering the motivation behind.

Also provide more details about the reasons for writing these projects.

The maximum width of 100 characters is appropriate for source code with
indentation, but in the end it looks better to keep the value of 80 for
.rst files (as well as any text file).

Cancel one of the previous commits changing the limit to 100
characters, and also fix some lines that were not complying with the 80
character rule in the first place.

NB: Lines starting with | (for new lines without starting a new paragraph)
cannot be split. They cannot comply with this rule.

Add an introduction to explain the reasons for these projects.

In all .rst files, change the maximum width of a line from 80 to 100
characters (inspired by Rust style guide).

Use CSS max-width property to prevent the text from spreading across
the whole width of the screen, because it makes it uneasy to read.

Update the description with the modifications made in the README.md
file of the project. Cscope can now be used with more languages than
just C and C++.

Ondine now displays the volume and provides related key controls. Add
them in the terminal capture.

Ondine now displays a progress bar for the current track. Add it in the
terminal capture.

The playback time information (position and duration) is mistakenly
shown on a separate line below.

When using aha to capture the terminal output, the cursor movements are
not taken into account, and some manual rework is necessary. Obviously
the rework was not done correctly for that part.

Move aha credit for the terminal capture to the "About this page"
section, and replace it with a real description of the screenshot
("Ondine playing Nick Drake" with UTF-8 musical notes around it).

Insert a screenshot for Emacs-IDE project.
Add CSS rules to display centered images and descriptions.

Use the same CSS rule for the descriptions of terminal captures and
screenshots (replace italic with smaller size and grey color).

Change the title of the website displayed in the header ("hjuvi's
free/libre and minimalist software", inspired by FLOSS with Open Source
replaced).

Insert a "screenshot" (HTML capture of terminal output) for Ondine
project.
Add CSS rules to display the capture and its description with margins.

- Change the description of GitLab links.
- Mention the CC0-1.0 license on every page.
- Change some font sizes in projects (increase for the title and
  decrease for the headers).

The links in the root page are currently targeting project/index.html,
while project/ is enough, and matches the URL that is intended to be
provided in the README file of each project.

This is the first version of software.hjuvi.fr.eu.org website.
It is a static website generated by Pelican.

The purpose of this website is to provide stable URLs for my projects,
that don't depend on the Git hosting service.

In the past, I used to build a static website for each project
(eide.hjuvi.fr.eu.org and ondine.hjuvi.fr.eu.org), but managing a
single repository is more convenient.

The main page is not so important, and just provides links to the
different projects.

Each project homepage is based on the same model, which is very simple.
It is composed of a single page, so there's no need to handle multiple
Pelican websites. A project "website" is just a page inside the global
website.

The URL of a project is just https://software.hjuvi.fr.eu.org/project.