It would be a lot easier to work with if it were broken up into sections and hosted with our other docs. The main arguments against are:
-
Translations. This may be able to be solved, but in reality: our UX team is only ever writing and editing in English; it's hard to assume the nuance of the HIG is going to be properly translated into other languages, especially when nobody working on the HIG itself is able to proof those other languages.
-
Non-image diagrams, e.g. the CSS-based dialogs. Honestly, these were cool and clever but an image is going to cause fewer problems in the long run—and is more easily swapped out when styles change instead of needing to rewrite the web CSS to match the GTK CSS.
It would be a lot easier to work with if it were broken up into sections and hosted with our other docs. The main arguments against are:
Translations. This may be able to be solved, but in reality: our UX team is only ever writing and editing in English; it's hard to assume the nuance of the HIG is going to be properly translated into other languages, especially when nobody working on the HIG itself is able to proof those other languages.
Non-image diagrams, e.g. the CSS-based dialogs. Honestly, these were cool and clever but an image is going to cause fewer problems in the long run—and is more easily swapped out when styles change instead of needing to rewrite the web CSS to match the GTK CSS.