Commit 36709562 authored by Nate Graham's avatar Nate Graham

Delete Static Text page and collapse relevant content into Labels page

parent 4669485a
......@@ -9,7 +9,6 @@ Writing
......@@ -19,6 +18,5 @@ Text includes all the written, language-based elements of the interface. This in
* :doc:`capitalization`
* :doc:`contraction`
* :doc:`labels`
* :doc:`static`
* :doc:`localization`
* :doc:`placeholder`
......@@ -25,6 +25,9 @@ Guidelines
be sure to set the the line edit as the
`buddy <>`_ of
the label.
- Avoid *static text*: long instructions or explanations within the user
interface. Being tempted to add static text is a good sign that the
software's user interface is too complex and should be simplified.
Labels in Dialogs
Static Text
Users tend to read only interactive control labels, especially those
that appear relevant to completing the task at hand. By contrast, users
read static text when they think they need to.
- Use the inverted pyramid for text. Start with the the conclusion and
the fundamental "takeaway" that readers must have. Then fill in
progressively more detail that readers may be interested in - perhaps
just to scan.
- Remove redundant text. Leave full text in main instructions and
interactive controls, and remove any redundancy from the other
- Avoid large blocks of UI text by chunking text into shorter sentences
and paragraphs or providing help links to useful, but not essential,
- Use bold font sparingly to draw attention to text users must read. A
different font, e.g. bold or italic, can be used to attract attention
when changes to UI design are not applicable or not efficient enough.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment