Recent commits to derivepassphrase.git (0247f35121d3472b79dfd18a76569fbe07ceccc7)

Fix minor oversights in the documentation

2025-06-21T15:04:12+02:00

The interal "Future ideas" page now also includes the same icons as the
changelog uses for referring to bugs and wishlist entries.

The wishlist path is slightly different, depending on whether MkDocs
builds in "online" or "offline" mode.  The CSS needs to accomodate both
paths.

The main API documentation should not attempt to refer to internals by
hyperlink.
</pre>

Merge topic branch 'changelog-v0.5' into master

2025-06-21T15:01:41+02:00

* changelog-v0.5:
  Update the "view source" link in the documentation as well
</pre>

Update the "view source" link in the documentation as well

2025-06-21T15:00:45+02:00

</pre>

Merge topic branch 'changelog-v0.5' into master

2025-06-17T23:21:04+02:00

* changelog-v0.5:
  Add changelog entry for the recent documentation formatting updates
  Update declared URLs (issues, source) and wishlist (priorities, versions)
  Use icons, not wishlist entry names, to link to the wishlist
  Link the commands, API classes, bugs and wishlist items in the changelog
  Rewrite v0.5 changelog: imperative form, developer commentary
  Compile changelog for v0.5
</pre>

Add changelog entry for the recent documentation formatting updates

2025-06-17T23:19:40+02:00

</pre>

Update declared URLs (issues, source) and wishlist (priorities, versions)

2025-06-17T23:09:10+02:00

</pre>

Use icons, not wishlist entry names, to link to the wishlist

2025-06-17T22:27:50+02:00

The entry names are very verbose, and cannot be shortened to a number.
So use a generic symbol instead: a bug for bugs, a giftbox for wishes.

Also add a legend, and slightly adjust the vertical positioning of these
icons.
</pre>

Link the commands, API classes, bugs and wishlist items in the changelog

2025-06-17T20:20:31+02:00

Turn all mentions of a command or subcommand name, or of an API member,
into a link to that command's manpage or API member's API documentation.

Furthermore, if a changelog entry refers to a bug or wishlist item, link
to the respective item as well.

Finally, collect and deduplicate all Markdown references at the bottom
of the page.
</pre>

Rewrite v0.5 changelog: imperative form, developer commentary

2025-06-15T13:22:32+02:00

Rewrite the changelog (and some parts of the v0.4.0 changelog too) in
imperative form, because that's what Keep a Changelog themselves use.
Mark commentary for developers specifically as such, and sort it to the
bottom of the section.
</pre>

Compile changelog for v0.5

2025-06-15T09:30:13+02:00

(Oops.)
</pre>