Skip to content

Commit 2cbb33d

Browse files
author
Nils Henning
committed
[TASK] finish basic building blocks guide
1 parent 95e735d commit 2cbb33d

File tree

1 file changed

+7
-7
lines changed
  • docs/guides/200-basic_building_blocks

1 file changed

+7
-7
lines changed

docs/guides/200-basic_building_blocks/README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -414,7 +414,7 @@ transition path: products_path, class: 'card-link' do
414414
end
415415
```
416416

417-
Read more about the [transition component](/docs/api/100-components/transition.md).
417+
Read more about the [transition component](/docs/guides/400-transitions/README.md).
418418

419419
**onclick**
420420

@@ -475,7 +475,7 @@ In the example above, clicking the "Delete" button will trigger an asynchronous
475475

476476
We recommend defining the expected hash parameter for `action` components in a method, because they can get quite large.
477477

478-
Read more about the [action component](/docs/api/100-components/action.md).
478+
Read more about the [action component](/docs/guides/600-actions/README.md).
479479

480480
**forms**
481481

@@ -521,7 +521,7 @@ Each form requires a few keys for configuration: `:for`, `:path`, `:method`. Lik
521521

522522
Forms will be submitted asynchronously and in case of errors dynamically extended to show errors belonging to inputs fields, but it is possible to set custom form behavior in success or failure cases. You could transition to another page, follow the redirect from the server as a transition or normal redirect, or emit events to leverage the above mentioned event hub.
523523

524-
To learn more, check out the [complete form documentation](/docs/api/100-components/form.md).
524+
To learn more, check out the [form guide](/docs/guides/500-forms/README.md).
525525

526526
**async**
527527

@@ -541,7 +541,7 @@ end
541541

542542
The above code snippet renders initially a paragraph and the current time followed by a button which emits the "update-time" event. The `async` component triggers an asynchronous request when the event is recieved, requesting it's content from the server. The server will respond with only the contents of the `async` components which is then replaced.
543543

544-
For more details on how to use the [async component](/docs/api/100-components/async.md) read the corresponding api doc.
544+
Read more about the [action component](/docs/guides/700-async/README.md).
545545

546546
**isolated**
547547

@@ -551,10 +551,10 @@ So isolated components are resolved completely indepentendly unlike async for wh
551551

552552
You can of course use every matestack component inside an isolated component, even `async` or another isolated component.
553553

554-
Read more about the [isolated component](/docs/api/100-components/isolated.md).
554+
Read more about the [isolated component](/docs/guides/800-isolated/README.md).
555555

556556
**collection**
557557

558+
With the `collection` component you can display active record model or similar collections and add features like filtering, paginating and ordering with ease. Each of these features requires no page reload to take effect, because the `collection` component leverages a `async` component in combination with the event hub to only reload the effected content of the collection. The `collection` component is a bit more complex as it offers a lot of functionality why we will not explain the rudimentary usage here.
558559

559-
560-
Read more about the [collection component](/docs/api/100-components/collection.md).
560+
Take a look at the [collection component guide](/docs//guides/900-collection/README.md) to learn how it works and how to use it.

0 commit comments

Comments
 (0)