Tagging @csteele as an "interested party" 
The up-shot is that if you have found the documentation or info hard to follow, then it would be good to share more details about where/how you tried to work out what to do, so it can be improved for other new users.
For those considering including their creations in HPM, see the main HPM topic on the Community:
My general understanding is:
- You setup a repository JSON file that lists out each of your drivers / apps with links to their manifests
- In GitHub you create a fork of the HPM repository and update the HPM setup to include your repository, creating a Pull Request as a way of requesting inclusion of your repository in HPM
- Your package manifest(s) (one for each driver or app you create) includes key info like the version number, release notes and list of files included
If you want a ( questionable ) example, you can look at my repository and linked package manifests, but others may be more aligned to the... better practices.... that should be followed.
Repository - hubitat/repository.json at master · sburke781/hubitat · GitHub
Simple Driver Examples:
- Mitsubishi (Unified) Thermostat Driver - hubitat/UnifiedThermostat/packageManifest.json at master · sburke781/hubitat · GitHub
- EcoWitt Manifest - ecowitt/packageManifest.json at main · sburke781/ecowitt · GitHub
Bundle and Non-Code File Example
- Mobile Controller - MobileController/hubitat/packageManifest.json at master · sburke781/MobileController · GitHub
There are utilities for simplifying the process, but early on I opted just to take an example and tweak the id's a bit each time, plus other relevant information.
