Section A.4 Contributing
As a project that is licensed openly, we welcome contributions. And this does not necessarily mean you need to learn our primary language, XSL. For ideas, find the issues on GitHub that have the label .
contributor project. As one example, it would be very helpful if a member of the community would create and maintain a Wikipedia page. That is a skill that is very distinct from the other skills used to create and maintain other parts of the project. See Issue #2071
github.com/PreTeXtBook/pretext/issues/207The documentation is authored in PreTeXt, so you know how to create additions, clean-up obsolete parts, and fix typos. If you know
git and GitHub, then a pull request (on a new branch!) is a very economical way for us to manage contributions. Even if you do not know GitHub, we can easily accept files written in PreTeXt that contain changes to the documentation. For example, files supporting localization to new languages (see Section 4.38) are ideal for simply submitting an entire file. (Send files to us by email, or post as attachments on one of the Google groups.)Conversions are written in XSL, a declarative language. It has a steep learning curve, but is very powerful for an application like this. Start small, and we do not mind helping you along with suggestions and critiques. Do not, do not, begin an ambitious task unless your skills are up to it.
When you have gained significant experience as an author, and have a good feel for the questions asked by other authors due to your material participation in the
pretext-support group, then it may be time to apply to be part of the pretext-dev group. This where design discussions are held and nasty bugs are squashed collectively.
