Skip to content

Commit 6ad5477

Browse files
committed
ajdusted install guide path
1 parent 27171b1 commit 6ad5477

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed

docs/reactive_apps/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Apps need to inherit from `Matestack::Ui::App` and implement a `response` method
5959

6060
How the call of `heading text: "Matestack Shop"` works will be explained later in this guide.
6161

62-
As you might have read in the [installation](/docs/start/000-installation/) guide you need to have a rails layout containing a html element with "matestack-ui" as class name. This is required because matestack uses Vue.js and we mount to this class name. Because we do not yet support writing "html, head, meta" and other tags that are used outside the body in matestack you need at least one layout file. But we recommend using one layout file for each app.
62+
As you might have read in the [installation](/docs/start/100-installation/) guide you need to have a rails layout containing a html element with "matestack-ui" as class name. This is required because matestack uses Vue.js and we mount to this class name. Because we do not yet support writing "html, head, meta" and other tags that are used outside the body in matestack you need at least one layout file. But we recommend using one layout file for each app.
6363

6464
**Accessing data in apps**
6565

File renamed without changes.

docs/ui_components/100-rails_integration/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The easiest way to integrate Matestack is by creating custom components and usin
1414

1515
This is a perfect place to start refactoring our application to use matestack. It's easy to start from the inside out, first replacing parts of your UI with components. As partials already are used to structure your UI in smaller reusable parts they are a perfect starting point. So let's refactor our product teaser into a custom component.
1616

17-
After successfully following the [installation guide](/docs/start/000-installation/README.md) we can start. Remember to set the id "matestack-ui" in your corresponding layout.
17+
After successfully following the [installation guide](/docs/start/100-installation/README.md) we can start. Remember to set the id "matestack-ui" in your corresponding layout.
1818

1919
Start by creating a file called `teaser.rb` in `app/matestack/components/products/teaser.rb`. Placement of this file is as you see similar to our partial. In this file we implement our component in pure ruby as follows:
2020

0 commit comments

Comments
 (0)