[TASK] remove table of contents

Author: Nils Henning

docs/guides/000-installation/README.md

@@ -2,16 +2,6 @@
 
 This guide shows you how to add matestack-ui-core to an existing rails application.
 
-1. [Installation](#installation)
-   1. [JavaScript Setup](#javascript-setup)
-   2. [Matestack Folder](#matestack-folder)
-   3. [Controller Setup](#controller-setup)
-   4. [Application layout adjustments](#application-layout-adjustments)
-   5. [Websocket Integration](#websocket-integration)
-2. [Usage](#usage)
-   1. [Full matestack](#full-matestack)
-   2. [Integration in existing projects](#integration-in-existing-projects)
-
 ## Installation
 
 Add 'matestack-ui-core' to your Gemfile

docs/guides/1200-devise/README.md

@@ -4,11 +4,6 @@ Devise is one of the most popular gems for authentication. Find out more about D
 
 In order to integrate it fully in matestack apps and pages we need to adjust a few things. This guide explains what exactly needs to be adjusted.
 
-1. [Setting up Devise](#setting-up-devise)
-2. [Devise models](#devise-models)
-3. [Devise helpers](#devise-helpers)
-4. [Devise sign in](#devise-sign-in)
-5. [Devise sign out](#devise-sign-out)
 
 ## Setting up Devise
 

docs/guides/200-basic_building_blocks/README.md

@@ -1,16 +1,5 @@
 # Basic Building Blocks
 
-**Table of contents**
-
-1. [Concept](#concept)
-   1. [Apps](#apps)
-   2. [Pages](#pages)
-   3. [Components](#components)
-      1. [Core Components](#core-components)
-      2. [Creating own components](#creating-own-components)
-      3. [Creating own vue.js components](#creating-own-vuejs-components)
-2. [Event Hub](#event-hub)
-3. [Core Features](#core-features)
 
 ## Concept
 

docs/guides/300-rails_integration/README.md

@@ -118,11 +118,11 @@ class Shop::App < Matestack::Ui::App
 
   def head_section
     header do
-      div class="round-header-background"
+      div class: "round-header-background"
       nav do
-        div class="logo" { plain "RAILS" }
+        div class: "logo" { plain "RAILS" }
       end
-      div class="hero search" do
+      div class: "hero search" do
         heading text: 'Shopping never was easier'
       end
     end

docs/guides/400-transitions/README.md

@@ -4,8 +4,6 @@ Matestack `transition` component enables switching between pages without a websi
 
 The `transition` component is therefore one of the key components for you to use. You should use them instead of a link if the target path of that link belongs to the same app. Given a shopping application with a shop app, links to our root, products index or details page should be transitions, because they belong to the shop app. The use of transitions enables the app to switch between pages without website reloads, instead asynchronously requesting the new page in the background and switching it after a successful response from the server. 
 
-1. [Usage](#usage)
-2. [Styling active transitions and it's parents](#styling-active-transitions-and-its-parents)
 
 ## Usage
 

docs/guides/500-forms/README.md

@@ -2,11 +2,6 @@
 
 Forms are one of the most important components for a lot of applications as they are always needed for user input, like searches, logins, registrations, newsletter subscriptions and much more. Matestack implements a `form` component which could wrap differnt form input components also implemented in matestack like text inputs, number inputs, textareas, selects, checkboxes, radio buttons and more.
 
-1. [Usage](#usage)
-   1. [Form component](#form-component)
-   2. [Form success and failure behavior](#form-success-and-failure-behavior)
-   3. [Input components](#input-components)
-   4. [Submitting forms](#submitting-forms)
 
 ## Usage