VSinerva/freesewing
1
0
Fork 0
Code Activity

chore: Linting for markdown and js

Browse source
This commit is contained in:
joostdecock 2021-10-17 17:34:55 +02:00
parent eca8199ed8
commit 1c92e0f655
6677 changed files with 24391 additions and 25987 deletions
Download patch file Download diff file Expand all files Collapse all files

20
markdown/dev/tutorials/pattern-design/completing-your-pattern/en.md
View file

@ -1,7 +1,8 @@
---
***
title: Completing your pattern
order: 260
---
----------
When we started out, we said a good part boilerplate looks like this:
@ -22,8 +23,8 @@ export default function(part) {
}
```
So far, we've kept to the *// Design pattern here* area, but now we're going to work on
the area under *// Complete?*
So far, we've kept to the *// Design pattern here* area, but now we're going to work on
the area under *// Complete?*
<Note>
@ -99,8 +100,8 @@ snippets.logo = new Snippet("logo", points.logo)
<Note>
You can find all possible snippets in [our documentation](/reference/snippets/).
You can find all possible snippets in [our documentation](/reference/snippets/).
</Note>
## Seam allowance
@ -120,7 +121,7 @@ So you can simply remove that condition.
However, for future refefence, `sa` is a variable that you can get from `part.shorthand()`
just like `complete`. But instead of `true` or `false` it will hold the amount of seam allowance
in mm.
in mm.
Note that you can still do `if (sa)` because zero is *falsy*.
@ -144,12 +145,12 @@ as explained in [Adding text](/concepts/adding-text).
## Scalebox and title
Two more macros and we're done.
Two more macros and we're done.
The `title` macro adds a title to our part.
It's not that big a deal here since we only have one part in our pattern.
But patterns typically have many different parts, some of them which might look rather similar.
That's why you should number your parts and give them a name.
That's why you should number your parts and give them a name.
The `title` macro can help you with that:
@ -175,4 +176,3 @@ And with that, our pattern is now *complete*:
<Example pattern="tutorial" part="step11" caption="We used attributes to add color, dashes, text on a path and even opacity" />
We're not done yet though. There's one more thing the user can ask for: a *paperless* pattern.