Fixed links in dev markdown
This commit is contained in:
parent
428507c668
commit
9f111e1a9b
16 changed files with 24 additions and 24 deletions
|
@ -50,7 +50,7 @@ paths.flb.attr('data-text', 'facingLiningBoundary')
|
|||
|
||||
<Tip>
|
||||
|
||||
Refer to [the sprinkle macro documentation](/reference/macros/sprinkle/) for details on how
|
||||
Refer to [the sprinkle macro documentation](/reference/api/macros/sprinkle/) for details on how
|
||||
to use this macro
|
||||
|
||||
</Tip>
|
||||
|
|
|
@ -5,7 +5,7 @@ about: Shows you how to add new parts to your pattern
|
|||
---
|
||||
|
||||
Since the patterns parts are listed
|
||||
in [the configuration file](/reference/config/), freesewing knows about
|
||||
in [the configuration file](/reference/api/config/), freesewing knows about
|
||||
all the parts that belong to your pattern.
|
||||
|
||||
It expects that each pattern has its own draft method, that is called `draft`
|
||||
|
|
|
@ -27,7 +27,7 @@ points.message = new Point(0,0)
|
|||
<Note>
|
||||
|
||||
In this example, we're using attributes to add text to our pattern.
|
||||
The [adding-text](/concepts/adding-text) documentation explains this in detail.
|
||||
The [adding-text](/howtos/code/adding-text) documentation explains this in detail.
|
||||
|
||||
</Note>
|
||||
|
||||
|
|
|
@ -4,7 +4,7 @@ for: developers
|
|||
about: Shows you how to create dependencies between pattern parts
|
||||
---
|
||||
|
||||
Part dependencies are set in the [pattern configuration](/reference/config), and
|
||||
Part dependencies are set in the [pattern configuration](/reference/api/config), and
|
||||
control the order in which parts are drawn. FreeSewing will make sure
|
||||
that before drafting a part, it will first draft all its dependencies.
|
||||
|
||||
|
|
|
@ -5,7 +5,7 @@ about: Shows how you can use one part of your pattern as the basis for another
|
|||
---
|
||||
|
||||
Part inheritance within your own pattern is handled via the `inject` settings in
|
||||
the [pattern configuration](/reference/config/). Here is a simple example:
|
||||
the [pattern configuration](/reference/api/config/). Here is a simple example:
|
||||
|
||||
```js
|
||||
inject: {
|
||||
|
|
|
@ -30,4 +30,4 @@ export default function(part) {
|
|||
```
|
||||
|
||||
In a case like this, the order in which parts are drafted becomes important, so you
|
||||
should reflect that in the [pattern configuration](/reference/config/).
|
||||
should reflect that in the [pattern configuration](/reference/api/config/).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue