This page contains information about contributing to the digiKam website.
There are two URLs in use for the website:
The main digiKam website.
The test/staging website. This should normally mirror the main website for the most part. This is where new content is tested before pushing to the main site.
Other meta pages:
- Design - Colors, typography, layout ideas for the migration.
- Writing - How to write content for the new site.
- Markdown Reference - A reference for markdown formatting.
The site is now being served as a statically built website.
This means that the website is now being pre-compiled from various source files ahead of time. These files are then made available through the web server as static assets (nothing needs to be dynamically created on the server). This significantly reduces the server requirements (no in-between scripting language or database required) as well as reduces the possible attack vectors for malicious actors.
The website will now be managed in a git repository. Pushes to the git repo will be reflected on the server for the branch that was pushed (see below).
The digiKam website is now being version controlled in a git repository.
If you have a developer account (you have been granted push access) you can get the website by cloning it with this address:
git clone email@example.com:websites/digikam-org
If you want to view the website or write content and create a patch to publish (that you’ll submit to someone with push access) you can get the website by cloning it with this address:
git clone https://anongit.kde.org/websites/digikam-org
Note: If you just need to write new content for the website, you can do this step and send a patch to the developers (or you can zip up your markdown file + assets and send that along as well).
There are two main branches that will be visible publicly,
They map to live websites like this:
Changes should always first be tested against the
If they work (and don’t implode the website) then they can be merged into the
The two branches should be maintained roughly in-sync with each other, and may occasionally need to be merged or rebased to make sure of this.
The site now uses Hugo to precompile everything into the final output.
There are binaries available for all major OS’s.
You can also build it from source if you want.