Thank you for considering contributing to this project!
- Use the Issues tab to report bugs or request features.
- Include:
- A clear description of the problem or feature.
- Steps to reproduce (if applicable).
- Example code or screenshots where possible.
- Open an Issue labeled
enhancement. - Describe:
- The problem the enhancement solves.
- Possible implementation ideas.
- Expected impact (performance, usability, flexibility).
- Use Option Explicit in all modules/classes.
- Follow consistent naming:
- Prefix private Properties with p_ (e.g., p_Text, p_FontLayout).
- Use PascalCase for public properties and methods.
- Comment tricky logic blocks and external API calls.
A Method only needs a Comment if
- Its logic is complicated
- Some obscure solution gives a big perfomance boost
- Something is not clear from the code itself
Otherwise a Comment for the Code is not needed. However, a Code Documentation is very Important. A simple markdown File describing what the Code does and why it does it in the way it does it should be the minimum.
Provide sample usage in a test module or snippet. If possible try to minimize the dependencies of your Code, as this eases Testing.