This is the home of the volunteer Holder community.

Holder is free software, open-source, new, under active and rapid development, and looking for people interested in helping shape it.

So HolderTeam is optimistic. At the moment it is just one person, but I have a dream.

Looking for the Holder app itself rather than the community?

Visit the Holder website for downloads, installation and getting started.

The Holder mono repository contains small components that each does one thing well.

The main heroes:

• Core - The main data formats and shared logic.
• Desktop App - The cross-platform desktop GTK GUI application frontend.
• Daemon - local-first backend that provides asynchronous real-time access to Holder data.

The trusty sidekicks:

• Release - The CI/CD setup for staging and releasing Holder to users.
• holder-website - the public homepage.
• Python APIs - allows users to script or automate their Holder projects and cards.

The most useful contribution at this stage is to install Holder and actually use it.

Try organising something real with it. Use it for a project, your research, your writing, your paperwork, or whatever information you need to keep under control.

Then tell us what happened.

What worked? What was annoying? What was confusing? What did you expect to be possible but couldn't do?

Open an issue. Don't worry about the solution. Identifying the problem is vastly more useful. Once we have a complete understanding of the problem, the solutions present themselves!

• Use and test Holder - probably the highest-value contribution right now.
• Report bugs - including rough edges and confusing behaviour.
• Suggest improvements - particularly things discovered through real use.
• Documentation and writing - the website, usage guides, in-app help.
• Design and artwork - look and feel of the app and the website.
• Packaging - Linux distributions, Windows, macOS, BSD and other platforms.
• Automated Testing - making it robust while rapidly developing.
• Development - C++, GTK/Vala, platform integration and eventually mobile.

You don't need permission to start looking around.

For big changes, it's worth opening an issue or starting a discussion first. That way we can work out where the idea fits, share any relevant plans, and make sure your time and effort are well spent.