Making HPS work directly from catalog software to Hugo

[sebastiaan-lampo]

Thanks for the great work you've done on HPS and for considering my PR's Gertjan! I'm using it to migrate a 1000+ photo website from piwigo to hugo.

My vision is to use HPS as part of a continuous integration workflow where it gets triggered after exporting photos from DigiKam (photo catalog). Thus, the goal is to have as much information be used from the photo files as possible. Then I can avoid having to edit the album yml files. To that end, my roadmap includes the following features as well as the two PR's I've already submitted. If you are interested in including any of those as well then I'll gladly make a PR including those changes you like.

Feature / change list

• Allow for photos_dir to be "" or None. -- done
• Allow for albums to be nested -- done
• Allow for "non-photo directory" in _load_albums to be automatically added as an album
• Allow for tags to have priority over album.yml file (or to drop items such as caption / alt from the yml template so that it falls back on the tags)

To solve: integrating album-level content. I rarely do this but sometimes it's nice to add context to an album with text or links. I haven't figured out yet if the album.yml or the markdown output would be the right spot to add it. Either way, it would require some way of integrating that information without HPS overriding it in the next update.