This PR attempts to address all issues mentioned in the above ticket by rewriting large parts of the chapter "Creating Themes" and rearranging the parts that remain into a more natural flow.
It now starts with a new section "Common Use Cases" which I believe is necessary since developers tend to use very different terminology for specific tasks. For example, many call it "creating a theme" when they technically only create new set of styling defaults for the existing Helium theme. For only 2 of the 5 listed use cases the content of this chapter is even relevant, and starting with the disambiguation allows us to point users elsewhere for the other use cases.
The section "Implementing Themes" has been rearranged to first show a minimal example of a working theme, and then delve into the lower level details.
Closes #576
This PR attempts to address all issues mentioned in the above ticket by rewriting large parts of the chapter "Creating Themes" and rearranging the parts that remain into a more natural flow.
It now starts with a new section "Common Use Cases" which I believe is necessary since developers tend to use very different terminology for specific tasks. For example, many call it "creating a theme" when they technically only create new set of styling defaults for the existing Helium theme. For only 2 of the 5 listed use cases the content of this chapter is even relevant, and starting with the disambiguation allows us to point users elsewhere for the other use cases.
The section "Implementing Themes" has been rearranged to first show a minimal example of a working theme, and then delve into the lower level details.