Reformatting + links fixed.

Author: haringsrob

CONTRIBUTING.md

@@ -15,12 +15,12 @@ If you discover a security vulnerability within Twill, please email us at [secur
 
 Twill follows [Semantic Versioning](https://semver.org/). Major releases are released only when breaking changes are necessary, while minor and patch releases may be released as often as every week. Minor and patch releases should never contain breaking changes.
 
-When referencing Twill from your application, you should always use a version constraint such as `^2.0`, since major releases of Twill do include breaking changes.
+When referencing Twill from your application, you should always use a version constraint such as `^3.0`, since major releases of Twill do include breaking changes.
 
 # Which branch?
-All bug fixes should be sent to the latest stable branch (`2.x`). Bug fixes should never be sent to the `main` branch unless they fix features that exist only in the upcoming release.
+All bug fixes should be sent to the latest stable branch (`3.x`). Bug fixes should never be sent to the `main` branch unless they fix features that exist only in the upcoming release.
 
-Minor features that are fully backwards compatible with the current Twill release may be sent to the latest stable branch (`2.x`).
+Minor features that are fully backwards compatible with the current Twill release may be sent to the latest stable branch (`3.x`).
 
 Major new features should always be sent to the `main` branch, which contains the upcoming Twill release.
 

docs/content/1_documentation/10_buckets/1_index.md

@@ -50,7 +50,7 @@ Then, define your buckets configuration:
 
 You can allow mixing modules in a single bucket by adding more modules to the `bucketables` array.
 Each `bucketable` should have
-its [model morph map](https://laravel.com/docs/5.5/eloquent-relationships#polymorphic-relations) defined because
+its [model morph map](https://laravel.com/docs/9.x/eloquent-relationships#polymorphic-relationships) defined because
 features are stored in a polymorphic table.
 In your AppServiceProvider, you can do it like the following:
 

docs/content/1_documentation/11_settings-sections/2_legacy.md

@@ -11,7 +11,7 @@ Settings sections are standalone forms that you can add to your Twill's navigati
 manage simple key/value records for you to then use anywhere in your application codebase.
 
 Start by enabling the `settings` feature in your `config/twill.php` configuration file `enabled` array.
-See [Twill's configuration documentation](/enabled-features/) for more information.
+See [Twill's configuration documentation](../2_getting-started/3_configuration.md) for more information.
 
 If you did not enable this feature before running the `twill:install` command, you need to copy the migration
 in `vendor/area17/twill/migrations/create_settings_table.php` to your own `database/migrations` directory and migrate

docs/content/1_documentation/13_user-management/1_index.md

@@ -141,9 +141,9 @@ You can use your new permission and existing ones in many places like the `twill
 ```
 
 Also in forms blade files using `@can`, as well as in middleware definitions in routes or controllers,
-see [Laravel's documentation](https://laravel.com/docs/5.7/authorization#via-middleware) for more info.
+see [Laravel's documentation](https://laravel.com/docs/9.x/authorization#via-middleware) for more info.
 
-You should follow the Laravel documentation regarding [authorization](https://laravel.com/docs/5.3/authorization). It's
+You should follow the Laravel documentation regarding [authorization](https://laravel.com/docs/9.x/authorization). It's
 pretty good. Also if you would like to bring administration of roles and permissions to the admin
 application, [spatie/laravel-permission](https://github.com/spatie/laravel-permission) would probably be your best
 friend.
@@ -152,7 +152,7 @@ friend.
 
 **DANGER**: don't use this feature in `production` as your CMS will be open for public.
 
-Developers can configure Twill to do auto login using a pre-defined username and password and skip the login form. 
+Developers can configure Twill to do auto login using a pre-defined username and password and skip the login form.
 
 To enable it you have to:
 

docs/content/1_documentation/15_packages/1_index.md

@@ -10,4 +10,4 @@ Packages are composer installable.
 
 In the following section we will explain how you can create your own package.
 
-- [Creating a package](./creating-a-package.md)
+- [Creating a package](./1_creating-a-package.md)

docs/content/1_documentation/18_api-documentation/1_index.md

@@ -1,6 +1,8 @@
 # API Documentation
 
-[Doctum](https://github.com/code-lts/doctum) generated API documentation of the framework is available [here](https://twill.io/docs/api/2.x) for `2.x` and previous versions.
+[Doctum](https://github.com/code-lts/doctum) generated API documentation of the framework is
+available [here](https://twill.io/docs/api/3.x) for `3.x` and previous versions.
 
+- [`3.x`](https://twill.io/docs/api/3.x)
 - [`2.x`](https://twill.io/docs/api/2.x)
 - [`main`](https://twill.io/docs/api/main)

docs/content/1_documentation/1_preface/3_architecture-concepts.md

@@ -2,7 +2,7 @@
 
 ## CRUD modules
 
-A Twill [CRUD module](/crud-modules/) is a set of classes and configurations in your Laravel application that enable
+A Twill [CRUD module](../3_modules/) is a set of classes and configurations in your Laravel application that enable
 your publishers to manage a certain type of content. The structure of a CRUD module is completely up to you.
 
 Another way to think of a CRUD module is as a feature rich Laravel resource. In other words (and for the non-Laravel
@@ -19,7 +19,7 @@ migrations and Eloquent model conventions.
 
 Twill's CRUD modules features are enabled using PHP traits you include in your Eloquent models and Twill repositories,
 as well as various configuration variables, and a bunch of conventions to follow. Further guidance is documented in
-the [CRUD modules](/crud-modules/) section.
+the [CRUD modules](../3_modules/) section.
 
 A Twill module can be modified however you like – you can include countless types of content fields, and change the
 organization and structure according to the needs of the module and your product. Setup is simple: you just need to
@@ -57,7 +57,7 @@ show and make parent/child relationships manageable on a module's records.
 
 Elements are modules or snippets of content that are added to an entity, page, or screen. Examples include the ability
 to manage footer text or create a global alert that can be turned on/off, etc. Twill offers developers the ability to
-quickly create [settings sections](/settings-sections/) to manage elements. A Twill module could also be configured to
+quickly create [settings sections](../11_settings-sections) to manage elements. A Twill module could also be configured to
 manage any sort of standalone element or content composition. There's nothing wrong with having a database table with a
 single record if that is what your product require, so you should feel free to create a Twill module to have a custom
 form for a single record. You can use a Laravel seeder or migration to initialize your admin console with those records.

docs/content/1_documentation/1_preface/5_contribution-guide.md

@@ -29,16 +29,16 @@ Twill follows [Semantic Versioning](https://semver.org/). Major releases are rel
 necessary, while minor and patch releases may be released as often as every week. Minor and patch releases should never
 contain breaking changes.
 
-When referencing Twill from your application, you should always use a version constraint such as `^2.0`, since major
+When referencing Twill from your application, you should always use a version constraint such as `^3.0`, since major
 releases of Twill do include breaking changes.
 
 ## Which branch?
 
-All bug fixes should be sent to the latest stable branch (`2.x`). Bug fixes should never be sent to the `main` branch
+All bug fixes should be sent to the latest stable branch (`3.x`). Bug fixes should never be sent to the `main` branch
 unless they fix features that exist only in the upcoming release.
 
 Minor features that are fully backwards compatible with the current Twill release may be sent to the latest stable
-branch (`2.x`).
+branch (`3.x`).
 
 Major new features should always be sent to the `main` branch, which contains the upcoming Twill release.
 
@@ -49,6 +49,6 @@ before submitting.
 
 ## Coding style
 
--
-PHP: [PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md).
+- PHP: [PSR-12 Coding Standard with small changes](https://github.com/area17/twill/blob/3.x/phpcs.xml).
+
 - Javascript: [Standard](https://standardjs.com/), [Vue ESLint Essentials](https://github.com/vuejs/eslint-plugin-vue).

docs/content/1_documentation/2_getting-started/1_index.md

@@ -2,7 +2,7 @@
 
 ## Environment requirements
 
-Twill `3.x` is compatible with Laravel versions `8.x` to `9.x`, running on PHP 8.0 and above. As a dependency to your
+Twill `3.x` is compatible with Laravel version `9.x`, running on PHP 8.0 and above. As a dependency to your
 own application, Twill shares Laravel's
 [server requirements](https://laravel.com/docs/9.x/deployment#server-requirements).
 
@@ -39,9 +39,9 @@ developed and tested against MySQL (`>=5.7`) and PostgreSQL(`>=9.3`).
 
 |            | Supported versions | Recommended version |
 |:-----------|:------------------:|:-------------------:|
-| PHP        |       >= 8.0       | 8.1                 |
-| Laravel    |       >= 8.0       | 9.x                 |
-| npm        |       >= 5.7       | 6.13                |
-| MySQL      |       >= 5.7       | 5.7                 |
-| PostgreSQL |       >= 9.3       | 10                  |
+| PHP        |       >= 8.0       |         8.1         |
+| Laravel    |       >= 9.0       |         9.x         |
+| npm        |       >= 5.7       |        6.13         |
+| MySQL      |       >= 5.7       |         5.7         |
+| PostgreSQL |       >= 9.3       |         10          |
 

docs/content/1_documentation/2_getting-started/2_installation.md

@@ -138,7 +138,7 @@ From there, you might want to configure Twill's media library's storage provider
 By default Twill uses local storage and local image rendering using [Glide](https://glide.thephpleague.com/), if you
 have more advanced image storage needs you can setup AWS as instructed below.
 
-See the [media library's configuration documentation](/media-library/) for more information.
+See the [media library's configuration documentation](../6_media-library) for more information.
 
 ### AWS