fixed links

developer-basics/application.md

@@ -1,5 +1,5 @@
 # Application
-<p class="uk-article-lead">The *Application* functions as Pagekit's dependency container. The application makes Pagekit's functionality and services configurable, extendable, interchangeable and accessible throughout the [modules](developer-basics/modules.md).</p>
+<p class="uk-article-lead">The *Application* functions as Pagekit's dependency container. The application makes Pagekit's functionality and services configurable, extendable, interchangeable and accessible throughout the [modules](modules.md).</p>
 
 All services you have available in Pagekit are set as dependency-injected properties on the `Application` instance. `$app['db']` for example will give you access to the database service.
 

developer-basics/modules.md

@@ -55,7 +55,7 @@ Pass a list of namespaces and paths to be auto loaded by Pagekit. The contained
 ```
 
 ### **routes**: Mount controllers
-Use the `routes` property to mount controllers to a route. Learn more about [Routing and Controllers](eveloper-basics/routing.md).
+Use the `routes` property to mount controllers to a route. Learn more about [Routing and Controllers](routing.md).
 
 ```php
 'routes' => [
@@ -213,7 +213,7 @@ Link to a route that renders your settings screen. Setting this property makes P
 ```
 
 ### **widgets**: Register Widgets
-A Widget is also a module. With the `widgets` property you can register all widget module definition files. Each of those files is expected to return a PHP array in the form of a valid module definition. Learn more about [Widgets](developer-guides/widgets.md).
+A Widget is also a module. With the `widgets` property you can register all widget module definition files. Each of those files is expected to return a PHP array in the form of a valid module definition. Learn more about [Widgets](../developer-guides/widgets.md).
 
 ```php
 'widgets' => [

developer-basics/packages.md

@@ -11,7 +11,7 @@ The vendor name is a unique representation of a developer or organization. In th
 ## Package content
 A package contains at least two files.
 1. The `composer.json` contains the metadata for your package and therefore acts as the package definition.
-2. The `index.php` is a so called [Module definition](developer-basics/modules.md) and adds actual functionality to Pagekit.
+2. The `index.php` is a so called [Module definition](modules.md) and adds actual functionality to Pagekit.
 
 The rest of the package content depends on the package's `type`. To learn more about the actual content of a package, check out the [Theme Guide](../developer-guides/themes.md) or the [Extension Guide](../developer-guides/extensions.md).
 

developer-basics/response.md

@@ -14,7 +14,7 @@ public function indexAction()
 ## Rendered View
 Pagekit can render the view and return the response for you. Simply return an array, with a key `$view` set to an array containing a _title_ and a view _name_.
 
-All other parameters in the array, will be accessible in the view. Learn more about [Views and Templating](developer-basics/views-templating.md).
+All other parameters in the array, will be accessible in the view. Learn more about [Views and Templating](views-templating.md).
 
 ```php
 public function indexAction($name = '')

developer-basics/routing.md

@@ -5,7 +5,7 @@
 The most common way in Pagekit for creating routes is to define a _Controller_. A _Controller_ is responsible for handling requests, setting routes and rendering views.
 
 ### Register a Controller
-You can register a _Controller_ inside your [module configuration](developer-basics/modules.md). Use the `routes` property to mount controllers to a route.
+You can register a _Controller_ inside your [module configuration](modules.md). Use the `routes` property to mount controllers to a route.
 
 ```php
 'routes' => [

developer-basics/views-templating.md

@@ -2,7 +2,7 @@
 <p class="uk-article-lead">While the controller is handling the incoming request, the view is responsible for rendering the response. To achieve this, it utilizes a templating engine. Currently Pagekit supports a PHP engine only.</p>
 
 ## Render a view
-There are two ways of rendering a view. The most common would be to return a [Rendered View](developer-basics/response.md#rendered-view) from your controller action.
+There are two ways of rendering a view. The most common would be to return a [Rendered View](response.md#rendered-view) from your controller action.
 
 You can also manually access the View service to render a template file. This may come in handy when you dynamically determine which view to load.
 

developer-guides/dashboard-widgets.md

@@ -2,7 +2,7 @@
 <p class="uk-article-lead">Use Dashboard Widgets to render small chunks of content at the admin panel's dashboard.</p>
 
 ## Create a Dashboard Widget
-A Dashboard Widget is created as a Vue component. You should therefore make sure to read the section on [Data Reactive Interface Design](developer/data-reactive-ui.md) and setup [Webpack](../tools/webpack-gulp.md) before continuing with the following steps.
+A Dashboard Widget is created as a [Vue](http://vuejs.org) component.
 1. Create a Vue component for your Widget, save it under your extension: `app/components/widget-hello.vue`
 
 ```vue

troubleshooting/server-error.md

@@ -2,10 +2,10 @@
 <p class="uk-article-lead">No matter the cause of the error this article will try explain how to isolate it and solve the most common ones.</p>
 
 ## Request Errors
-If you are able to access your Pagekit installation but are getting an error when trying to perform a task, it's usually related to a Request error. Its response should reveal to us what is going on. In order to see the response you must check the browser console and make sure the [Debug Mode](troubleshooting/debug.md) is on.
+If you are able to access your Pagekit installation but are getting an error when trying to perform a task, it's usually related to a Request error. Its response should reveal to us what is going on. In order to see the response you must check the browser console and make sure the [Debug Mode](debug-mode.md) is on.
 
 ## Pagekit Errors
-If the error is braking the page and a message **Whoops! Something went wrong** is displaying instead, it means Pagekit is being executed but an PHP error ocurred. In order to see the actual error enable the [Debug](troubleshooting/debug.md) mode and refresh the view.
+If the error is braking the page and a message **Whoops! Something went wrong** is displaying instead, it means Pagekit is being executed but an PHP error ocurred. In order to see the actual error enable the [Debug](debug-mode.md) mode and refresh the view.
 
 ## Internal Server Errors
 If the error is breaking the page and a message **The server encountered an internal error or misconfiguration and was unable to complete your request** is displaying instead, it means the error is happening before Pagekit execution and to get the actual error to be displayed would require modifying the `php.ini` file.