Style Guide for Dnn / 2sxc Solutions

Provide a clear, common guideline for Dnn and 2sxc development.

The current version is the Style Guide 2020 - beta

Style Vocabulary

Each guideline describes either a good or bad practice, and all have a consistent presentation.

The wording of each guideline indicates how strong the recommendation is.

+ Do

is one that should always be followed. Always might be a bit too strong of a word. Guidelines that literally should always be followed are extremely rare. On the other hand, you need a really unusual case for breaking a Do guideline. testing

+ Consider

Consider guidelines should generally be followed. If you fully understand the meaning behind the guideline and have a good reason to deviate, then do so. Please strive to be consistent.

- Avoid

indicates something you should almost never do. Code examples to avoid have an unmistakeable red header

? Why