I update release.txt file (which is also displayed on website) when introduce changes.

I manage my images using "dev" branch, by the way noticing bugs and introducing new features.
It is generally not a good idea to work on the same directory the images are stored,
so I have yet another place to test very new ideas.

There is no rule when "dev" is merged into "master", it happens occasionally when I think
everything is fine and stable.

There are no plans to abandon the project, nor it will be actively developed.
Contributions are generally welcome, but I would more happily accept issues and ideas.

Static code analysis:
Python scripts are checked with pylint and pycodestyle for clarity.
Core functions additionally include type hints and checked with mypy.
Texts are checked against typos with aspell.

How the website is deployed:
Quite the same documents are used for both website and included documentation
which decision may result pain in conversion between formats.
Hence, two scripts are included, one for website generation and one for deployment.
*.txt files should generally exclude characters like html formatting and comply basic markdown.

Mastodon contact& newsletter: phibrajry@techtoots.com
Direct webmail (~1 month cooldown): hellovsnits@tutanota.com