Skip to content

Commit a50d947

Browse files
authored
Merge fbcc089 into 0f9c0da
2 parents 0f9c0da + fbcc089 commit a50d947

3 files changed

Lines changed: 72 additions & 0 deletions

File tree

devDocs/featureFlags.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,3 +142,6 @@ self.loadChromeVbufWhenBusyCombo.resetToConfigSpecDefault()
142142
# save GUI value to config:
143143
self.loadChromeVbufWhenBusyCombo.saveCurrentValueToConf()
144144
```
145+
146+
## User Guide Documentation
147+
Refer to [User Guide Standards](./userGuideStandards.md#feature-settings)

devDocs/userGuideStandards.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# User Guide Standards
2+
This document aims to create a standard style guide for writing documentation in the User Guide.
3+
4+
The principles outlined in ["The Documentation System" guide for reference materials](https://documentation.divio.com/reference/) are encouraged when working on the User Guide and this document.
5+
6+
## General standards
7+
- Key commands (e.g. ` ``NVDA+control+upArrow`` `):
8+
- should be written in lowerCamelCase
9+
- encapsulated in monospace code-block formatting
10+
- NVDA should be capitalized
11+
- When referring to Windows terminology, follow the [Windows style guide](https://docs.microsoft.com/en-us/style-guide/welcome/).
12+
- For instance, instead of "system tray" refer to "notification area"
13+
14+
## Feature settings
15+
16+
Feature flags should be included using the following format.
17+
18+
`FeatureDescriptionAnchor` should not include the settings category.
19+
Once the anchor is set it cannot be updated, while settings may move categories.
20+
21+
```text2tags
22+
==== The name of a feature ====[FeatureDescriptionAnchor]
23+
: Default
24+
Enabled
25+
: Options
26+
Default (Enabled), Enabled, Disabled
27+
: ``NVDA+o``
28+
Toggle this feature
29+
:
30+
31+
This setting allows the feature of using functionality in a certain situation to be controlled in some way.
32+
If necessary, a description of a common use case that is supported by each option.
33+
```

user_docs/styles.css

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,3 +55,39 @@ pre {
5555
padding: 1em;
5656
border-left: 2px solid #69c;
5757
}
58+
59+
/*
60+
Definition styling.
61+
https://txt2tags.org/markup.html
62+
In t2t, definition lists are defined as follows:
63+
64+
: Definition list
65+
A list with terms
66+
: Start term with colon
67+
And its definition follows
68+
:
69+
*/
70+
71+
/* Definition list */
72+
dl {
73+
display: grid;
74+
grid-template-columns: max-content auto;
75+
}
76+
77+
/* Term of a definition */
78+
dl > dt {
79+
display: inherit;
80+
grid-column-start: 1;
81+
font-style: italic;
82+
font-weight: bold;
83+
font-size: small;
84+
}
85+
86+
/* Definition of a term */
87+
dl > dd {
88+
display: inherit;
89+
grid-column-start: 2;
90+
margin-inline-start: 1em;
91+
font-size: small;
92+
font-style: italic;
93+
}

0 commit comments

Comments
 (0)