VSinerva/freesewing
1
0
Fork 0
Code Activity

chore(markdown): Linting of dev docs

Browse source
This commit is contained in:
Joost De Cock 2022-02-19 08:04:25 +01:00
parent 1d8beedd44
commit 265ad404da
317 changed files with 1281 additions and 1503 deletions
Download patch file Download diff file Expand all files Collapse all files

24
markdown/dev/tutorials/pattern-design/adding-options/en.md
View file

@ -6,9 +6,9 @@ order: 140
You know what your bib should look like, and you have the *head* measurement
to work with. But there's still a number of choices you have to make:
- How large should the neck opening be?
- How wide should the bib be?
- How long should the bib be?
- How large should the neck opening be?
- How wide should the bib be?
- How long should the bib be?
You can make all of these choices for the user and set them in stone, so to speak.
@ -17,7 +17,7 @@ flexible and let the user decide. All you have to do is add options to your patt
## Add the neckRatio option
The first option we're going to add controls the ratio between the neck opening
The first option we're going to add controls the ratio between the neck opening
and the head circumference. Let's call it `neckRatio`.
Open the config file at `config/index.js` and add this to the options:
@ -33,10 +33,10 @@ Open the config file at `config/index.js` and add this to the options:
Can you guess what it means?
- We've added a option of type percentage
- Its minimum value is 70%
- Its maximum value is 90%
- Its default value is 80%
- We've added a option of type percentage
- Its minimum value is 70%
- Its maximum value is 90%
- Its default value is 80%
<Note>
@ -55,9 +55,9 @@ options: {
}
```
- You've added `widthRatio` and `lengthRatio` options
- You've given all options sensible defaults
- You've given all options sensible maximum and minimum boundaries
- You've added `widthRatio` and `lengthRatio` options
- You've given all options sensible defaults
- You've given all options sensible maximum and minimum boundaries
<Note>
@ -76,7 +76,7 @@ optionGroups: {
<Note>
The `optionGroups` entry does not do anything for your pattern as such.
The `optionGroups` entry does not do anything for your pattern as such.
Instead it signals to the frontend that this is how options should be grouped together and presented to the user.
</Note>