Thank you! My current idea is to upload the project as an obsidian vault to GitHub. That would contain markdown files that can be used as-is, and vault configuration files. Obsidian has a variety of plugins for manipulating files and their data.
I am a non-technical technical person in that I understand a lot of random technical concepts, but not necessarily how they work in practice.
I'm not too worried about creating content right away. I am more concerned with designing the system correctly and then working on converting my project to that system.
Then i think it comes down to who is the end user and how you plan to integrate into their current workflows. For example, are you after the good-samaritans or the smaller vet clinics? Are there any differences between how the two would use this information? What is more important? Ease of use or maintenance of knowledge? Etc
The first phase of the project is identifying, collecting, and documenting kitten issues and solutions. The goal is to create a central repository for academic purposes, because kitten information is fragmented among nonprofits and cat breeders.
The repository is a first step in answering the question "What can I do to help kittens?" for any skill level). It's the technical information that the rest of the project is based on.
I think maintenance is more important for this first phase. Being human- and machine-readable is important. Ease of use is more important in later stages.
I am a non-technical technical person in that I understand a lot of random technical concepts, but not necessarily how they work in practice.
I'm not too worried about creating content right away. I am more concerned with designing the system correctly and then working on converting my project to that system.