Some terms in technical documentation, for example product proper names, should obviously be capitalized. But there are other terms that are somewhere between a proper name and a generic noun: domain terms more or less specific to a given product, but are not proper names per se.
For example in developer documentation for CMS software these might be: class, controller, repository, etc.
On one hand, capitalizing such terms makes it explicit to the reader that we are referring to the name in the specific context of our application (e.g., the content Repository of our product, not a GitHub repository).
On the other hand, there is no grammatical reason to capitalize them, and overfilling a text with capitalized terms can increase cognitive load and make it harder to understand.
What do I need to consider when creating guidelines for capitalizing such domain terms?