Skip to content

Commit 9f2f199

Browse files
committed
Fix rendering of nested lists in docs
1 parent 066f7c9 commit 9f2f199

File tree

3 files changed

+40
-39
lines changed

3 files changed

+40
-39
lines changed

RELEASING.md

Lines changed: 24 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ In order for the automation to work properly, contributors must follow the
1212
1. Pull requests are automatically labelled by branch name. Labels are then used
1313
for:
1414

15-
1. resolving next [semantic version number][semver]
16-
(BREAKING.FEATURE.PATCH),
17-
2. grouping changes in changelog.
15+
1. resolving next [semantic version number][semver]
16+
(BREAKING.FEATURE.PATCH),
17+
2. grouping changes in changelog.
1818

1919
2. Release draft with changelog is generated as pull requests are merged into
2020
the `master` branch. Invididual PR names are listed and grouped by type based
@@ -30,35 +30,36 @@ See the source of `.github/workflows` for details.
3030
[GitHub releases page][gh-releases] to see what the changelog looks like and
3131
what will be the next version number.
3232

33-
**Don't edit manually until you are ready to publish the release.** Release
34-
draft is automatically overwritten everytime a change is merged to `master`.
33+
**Don't edit manually until you are ready to publish the release.** Release
34+
draft is automatically overwritten everytime a change is merged to `master`.
3535

3636
2. **Manual:** once you are ready to publish a release:
3737

38-
1. **Bump the version number** in `package.json` and `package-lock.json`.
39-
Make sure it matches the intended version number in the release draft.
40-
**Don't combine this step with any other changes,** they wouldn't be
41-
reflected in the changelog.
38+
1. **Bump the version number** in `package.json` and `package-lock.json`.
39+
Make sure it matches the intended version number in the release draft.
40+
**Don't combine this step with any other changes,** they wouldn't be
41+
reflected in the changelog.
4242

43-
2. Now is also your **chance to review and adjust (if necessary) the intended
44-
version and actual changelog before the release is published.**
45-
Automatic release drafting is skipped when a version change in
46-
`package.json` is detected so this time your changes will not be
47-
overwritten. Save your changes in release draft with the _Save draft_
48-
button, **do not publish** yet!
43+
2. Now is also your **chance to review and adjust (if necessary) the
44+
intended
45+
version and actual changelog before the release is published.**
46+
Automatic release drafting is skipped when a version change in
47+
`package.json` is detected so this time your changes will not be
48+
overwritten. Save your changes in release draft with the _Save draft_
49+
button, **do not publish** yet!
4950

50-
3. Get back to the repository, commit both files as
51-
`Bump version to <VERSION_NUMBER>` in `release/<VERSION_NUMBER>` branch,
52-
create a pull request, hold your breath, and—merge it.
51+
3. Get back to the repository, commit both files as
52+
`Bump version to <VERSION_NUMBER>` in `release/<VERSION_NUMBER>` branch,
53+
create a pull request, hold your breath, and—merge it.
5354

5455
3. **Automatic:** once the release pull request from step 2.3 is merged, the
5556
following actions are triggered automatically:
5657

57-
1. GitHub release draft with name corresponding to the version number from
58-
step 2 is published.
59-
2. Git tag with the version number from step 2 is added to `master` branch.
60-
3. Package is built and published to npm package registry.
61-
4. Documentation is built and deployed to production.
58+
1. GitHub release draft with name corresponding to the version number from
59+
step 2 is published.
60+
2. Git tag with the version number from step 2 is added to `master` branch.
61+
3. Package is built and published to npm package registry.
62+
4. Documentation is built and deployed to production.
6263

6364
**Note:** prefix version number with `v` everywhere except in `package.json` and
6465
`package-lock.json`.

src/docs/contribute/composition.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,16 +8,16 @@ There are several types of composition approaches.
88
2. **Components with subcomponents:** subcomponents cannot exist on their own
99
outside their parent components.
1010

11-
- **Mandatory subcomponents:** subcomponent must be used at least once in
12-
order for the composition to work. E.g. `Tabs` + `TabsItem`.
11+
- **Mandatory subcomponents:** subcomponent must be used at least once in
12+
order for the composition to work. E.g. `Tabs` + `TabsItem`.
1313

14-
- **Optional subcomponents:** optional subcomponents may be used to achieve
15-
special results. E.g. `FormLayout` + `FormLayoutCustomField` or `Grid` +
16-
`GridSpan`.
14+
- **Optional subcomponents:** optional subcomponents may be used to achieve
15+
special results. E.g. `FormLayout` + `FormLayoutCustomField` or `Grid` +
16+
`GridSpan`.
1717

18-
- **Both mandatory and optional subcomponents:** e.g. `Card` + `CardBody`
19-
(mandatory) + `CardFooter` (optional), `Toolbar` + `ToolbarItem`
20-
(mandatory) + `ToolbarGroup` (optional), etc.
18+
- **Both mandatory and optional subcomponents:** e.g. `Card` + `CardBody`
19+
(mandatory) + `CardFooter` (optional), `Toolbar` + `ToolbarItem`
20+
(mandatory) + `ToolbarGroup` (optional), etc.
2121

2222
3. **Wrappers for other components:** component is designed to wrap other
2323
self-contained components. E.g. `FormLayout` + form fields (`CheckboxField`,

src/docs/contribute/css.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -183,14 +183,14 @@ class.
183183
3. **Component's top-level HTML element must have `root` class name.**
184184
However, this rule has a few exceptions:
185185

186-
1. When the component is a subcomponent, it's usually better to use
187-
subcomponent's name, e.g. `item` or `group`. This enables us to keep
188-
related CSS of both the main component and its subcomponents in a single
189-
file and see the big picture during development.
190-
191-
2. When no CSS on the root element is necessary and styling only takes place
192-
once a visual modification is invoked by component props, `root` class
193-
name can be omitted entirely.
186+
1. When the component is a subcomponent, it's usually better to use
187+
subcomponent's name, e.g. `item` or `group`. This enables us to keep
188+
related CSS of both the main component and its subcomponents in a single
189+
file and see the big picture during development.
190+
191+
2. When no CSS on the root element is necessary and styling only takes place
192+
once a visual modification is invoked by component props, `root` class
193+
name can be omitted entirely.
194194

195195
4. **Modifier class names related to the current HTML element must start with
196196
`is`** and contain the name of the target element, e.g. `isRootLoading`

0 commit comments

Comments
 (0)