fixed docs links

Author: jonasjabari

docs/api/README.md renamed to docs/api/100-components/README.md

@@ -2,7 +2,7 @@
 
 The `cable` component enables us to update the DOM based on events and data pushed via ActionCable without a browser reload.
 
-Please read the [ActionCable Guide](/docs/guides/1000-action_cable/README.md) if you need help setting up ActionCable for your project, and make sure you have set up ActionCable correctly. The following code snippet is crucial to make the `cable` component work correctly:
+Please read the [ActionCable Guide](/docs/reactive_components/1000-action_cable/README.md) if you need help setting up ActionCable for your project, and make sure you have set up ActionCable correctly. The following code snippet is crucial to make the `cable` component work correctly:
 
 `app/javascript/channels/matestack_ui_core_channel.js`
 

docs/api/100-components/cable.md

@@ -45,4 +45,4 @@ VueJsComponents are more complex components. These always have a Vue.js counterp
 We introduced you to the apps, pages and components concepts of matestack. In order to unterstand better how matestack works, we create an application from the ground up using matestack and enhancing it step by step while leveraging more and more features of matestack.
 Read the following guides to get started with matestack and get a better understanding about how apps, pages, components work.
 
-Let's setup a rails app with matestack by following the [next guide](/docs/guides/100-tutorial/01_setup.md)
+Let's setup a rails app with matestack by following the [next guide](/docs/reactive_apps/1000-tutorial/01_setup.md)

docs/reactive_apps/100-rails-integration/README.md renamed to docs/reactive_apps/100-rails_integration/README.md

@@ -346,4 +346,4 @@ We now have a working Rails app using `matestack`.
 
 In this guide we learned how matestack pages work, how we can use matestacks components to create html and how we can use an app as a layout for pages and what benefits we get through using an app.
 
-After taking a well deserved rest, make sure to continue exploring the features `matestack` offers you by checking out the [next part of the series](/docs/guides/100-tutorial/02_active_record.md).
+After taking a well deserved rest, make sure to continue exploring the features `matestack` offers you by checking out the [next part of the series](/docs/reactive_apps/1000-tutorial/02_active_record.md).

docs/reactive_apps/1000-tutorial/00_introduction.md

@@ -7,15 +7,15 @@ Welcome to the second part of our tutorial about building a web application with
 
 ## Introduction
 
-In the [previous guide](/docs/guides/100-tutorial/01_setup.md), we created a new project, installed the necessary libraries, added a demo `matestack` app featuring two `matestack` pages, and deployed it using Heroku.
+In the [previous guide](/docs/reactive_apps/1000-tutorial/01_setup.md), we created a new project, installed the necessary libraries, added a demo `matestack` app featuring two `matestack` pages, and deployed it using Heroku.
 
 In this guide, we will
 - create an ActiveRecord model to work with throughout this series
 - add some seeded data and migrate the database
 
 ## Prerequisites
 
-We expect you to have successfully finished the [previous guide](/docs/guides/100-tutorial/01_setup.md).
+We expect you to have successfully finished the [previous guide](/docs/reactive_apps/1000-tutorial/01_setup.md).
 
 ## Adding the ActiveRecord model
 
@@ -138,4 +138,4 @@ git add . && git commit -m "Introduce person model including seeds, add it to ma
 
 We have updated the app to use a working database model, added some records and displayed them on an index page.
 
-Let's continue and build even cooler stuff by heading directly to the [next part of the series](/docs/guides/100-tutorial/03_index_show.md).
+Let's continue and build even cooler stuff by heading directly to the [next part of the series](/docs/reactive_apps/1000-tutorial/03_index_show.md).

docs/reactive_apps/1000-tutorial/01_setup.md

@@ -7,15 +7,15 @@ Welcome to the third part of our tutorial about building a web application with
 
 ## Introduction
 
-In the [previous guide](/docs/guides/100-tutorial/02_active_record.md), we added an ActiveRecord model to our project, added some fake persons to our database and displayed them on an index page.
+In the [previous guide](/docs/reactive_apps/1000-tutorial/02_active_record.md), we added an ActiveRecord model to our project, added some fake persons to our database and displayed them on an index page.
 
 In this guide, we will
 - a detail page for every person
 - dive more into the concept of page transitions
 
 ## Prerequisites
 
-We expect you to have successfully finished the [previous guide](/docs/guides/100-tutorial/02_active_record.md).
+We expect you to have successfully finished the [previous guide](/docs/reactive_apps/1000-tutorial/02_active_record.md).
 
 ## Update person controller and routes
 
@@ -146,4 +146,4 @@ git add . && git commit -m "Add index/show matestack pages for person model (inc
 
 Our **person** model now has a dedicated index and show page. The pages within our `matestack` app are properly linked to each other. We learned how we can access data and use rails helpers inside of pages, apps and components and how transitions in more detail work.
 
-Let's continue and add the necessary functionality for adding new persons and editing existing ones in the [next part of the series](/docs/guides/100-tutorial/04_forms_edit_new_create_update_delete.md).
+Let's continue and add the necessary functionality for adding new persons and editing existing ones in the [next part of the series](/docs/reactive_apps/1000-tutorial/04_forms_edit_new_create_update_delete.md).

docs/reactive_apps/1000-tutorial/02_active_record.md

@@ -7,7 +7,7 @@ Welcome to the fourth part of our tutorial about building a web application with
 
 ## Introduction
 
-In the [previous guide](/docs/guides/100-tutorial/03_index_show_transition.md), we added index and show pages for the **person** model. In this part, we will implement the create, update and delete part of our CRUD application. For this we will introduce the matestack `forms`.
+In the [previous guide](/docs/reactive_apps/1000-tutorial/03_index_show_transition.md), we added index and show pages for the **person** model. In this part, we will implement the create, update and delete part of our CRUD application. For this we will introduce the matestack `forms`.
 
 In this guide, we will
 - add a new page and action action to create new persons
@@ -17,7 +17,7 @@ In this guide, we will
 - introduce the concept of matestack actions
 
 ## Prerequisites
-We expect you to have successfully finished the [previous guide](/docs/guides/100-tutorial/03_index_show_transition.md).
+We expect you to have successfully finished the [previous guide](/docs/reactive_apps/1000-tutorial/03_index_show_transition.md).
 
 ## Updating the person model
 
@@ -315,4 +315,4 @@ We got a brief introduction of the `form` and `action` components and know how t
 
 But there's still more guides coming - so what's left? In the upcoming chapters, we will dive deeper into some `matestack` concepts to further enhance both user experience and developer happiness!
 
-Take a well deserved rest and make sure to come back to the next part of this series, introducing the powerful [`toggle component`](/docs/guides/100-tutorial/05_toggle_component.md).
+Take a well deserved rest and make sure to come back to the next part of this series, introducing the powerful [`toggle component`](/docs/reactive_apps/1000-tutorial/05_toggle_component.md).

docs/reactive_apps/1000-tutorial/03_index_show_transition.md

@@ -13,7 +13,7 @@ In this guide, we will introduce matestacks `toggle` and `onclick` components. F
 
 ## Prerequisites
 
-We expect you to have successfully finished the [previous guide](/docs/guides/100-tutorial/04_forms_edit_new_create_update_delete.md).
+We expect you to have successfully finished the [previous guide](/docs/reactive_apps/1000-tutorial/04_forms_edit_new_create_update_delete.md).
 
 ## Adding a show more button with onclick
 
@@ -96,4 +96,4 @@ git add . && git commit -m "add show more toggle to person show page"
 
 We added a show more button to our persons show page and learned how to use the `onclick` and `toggle` components and what they can be used for.  
 
-Take a well deserved rest and make sure to come back to the next part of this series, introducing the powerful [`async` component](/docs/guides/100-tutorial/06_async_component.md).
+Take a well deserved rest and make sure to come back to the next part of this series, introducing the powerful [`async` component](/docs/reactive_apps/1000-tutorial/06_async_component.md).

docs/reactive_apps/1000-tutorial/04_forms_edit_new_create_update_delete.md

@@ -13,7 +13,7 @@ In this guide, we will introduce matestacks `async` component. For this we will
 
 ## Prerequisites
 
-We expect you to have successfully finished the [previous guide](/docs/guides/100-tutorial/05_toggle_component.md).
+We expect you to have successfully finished the [previous guide](/docs/reactive_apps/1000-tutorial/05_toggle_component.md).
 
 ## Add a delete button
 
@@ -127,4 +127,4 @@ git add . && git commit -m "add delete button to person list and update it dynam
 
 We added a delete button to our person list on the index page. When a person is deleted our list gets automatically updated without even reloading the page, just by updating the part that is needed. And all of that with a few lines of code and without writing any JavaScript.
 
-Take a well deserved rest and make sure to come back to the next part of this series, introducing [partials and custom components](/docs/guides/100-tutorial/07_partials_and_custom_components.md).
+Take a well deserved rest and make sure to come back to the next part of this series, introducing [partials and custom components](/docs/reactive_apps/1000-tutorial/07_partials_and_custom_components.md).