})
;
+
+Looking at the network stack, you can see two redirects happening:
+
+})
;
+
+The first redirect from `http://127.0.0.1:4445/dashboard` to
+`http://127.0.0.1:4455/.ory/kratos/public/auth/browser/login` is initiated by
+the Reverse Proxy ([ORY Oathkeeper](https://github.com/ory/oathkeeper)) because
+the browser does not have a valid authentication (login) session yet. The
+redirect points to one of ORY Krato's APIs used for logging in browser-based
+applications. ORY Kratos does some security checks and prepares form data and
+redirects the browser to `http://127.0.0.1:4445/auth/login`, appending a
+`?request=...` query parameter. The endpoint at `/auth/login` (which belongs to
+our SecureApp) then fetches data important for rendering the forms from ORY
+Krato's Admin API:
+
+```shell script
+$ curl http://127.0.0.1:4434/self-service/browser/flows/requests/login?request=})
;
+
+The network trace looks familiar by now:
+
+})
;
+
+If we try to sign up using a password like `123456`, ORY Krato's password policy
+will complain:
+
+})
;
+
+The error message is coming directly from ORY Krato's API:
+
+```shell script
+$ curl http://127.0.0.1:4434/self-service/browser/flows/requests/registration?request=})
;
+
+By using "logout" you will be redirected to the log in screen again an will be
+able to use the credentials just set up to log in!
+
+### Understanding how Login and Registration works
+
+Head over to the [Self-Service Flows Chapter](./self-service/flows/index.md) for
+a in-depth explanation of how the individual flows work.
+
+### Email Verification
+
+As you've signed up, an email was sent to the email address you used. Because
+the quickstart uses a fake SMTP server, the email did not arrive in your inbox.
+You can retrieve the email however by opening the MailSlurper UI at
+[127.0.0.1:4436](http://127.0.0.1:4436).
+
+You should see something like this:
+
+})
;
+
+If not, hard refresh the tab or click on the home icon in the menu bar.
+
+Next, click the verification link. You will end up at the dashboard, with a
+verified E-Mail Address (check the `verified` and `verified_at` field in the
+JSON Payload):
+
+})
;
+
+To re-request the verification email, fill out the form at
+[127.0.0.1:4455/verify](http://127.0.0.1:4455/verify).
+
+#### Configuration Used
+
+You can find all configuration files for this quickstart guide in
+`./contrib/quickstart` and `./quickstart.yml`. To understand what each of those
+individual configuration files are doing, you must consult the other chapters of
+this documentation.
+
+In the future, this guide will support more use cases such as:
+
+- Use GitHub to login in and sign up
+- Use PostgreSQL / MySQL instead of SQLite
+
+## Cleaning up Docker
+
+To clean everything up, you need to bring down the Docker Compose environment
+and remove all mounted volumes.
+
+```shell script
+docker-compose -f quickstart.yml down -v
+docker-compose -f quickstart.yml rm -f -s -v
+```
diff --git a/docs/docs/reference/api.md b/docs/docs/reference/api.md
new file mode 100644
index 00000000000..ca5f316a8c7
--- /dev/null
+++ b/docs/docs/reference/api.md
@@ -0,0 +1,5719 @@
+---
+title: Ory Kratos
+language_tabs: []
+toc_footers: []
+includes: []
+search: false
+highlight_theme: darkula
+headingLevel: 2
+---
+
+Welcome to the ORY Kratos HTTP API documentation!
+
+> You are viewing REST API documentation. This documentation is auto-generated
+> from a swagger specification which itself is generated from annotations in the
+> source code of the project. It is possible that this documentation includes
+> bugs and that code samples are incomplete or wrong.
+>
+> If you find issues in the respective documentation, please do not edit the
+> Markdown files directly (as they are generated) but raise an issue on the
+> project's GitHub presence instead. This documentation will improve over time
+> with your help! If you have ideas how to improve this part of the
+> documentation, feel free to share them in a
+> [GitHub issue](https://github.com/ory/docs/issues/new) any time.
+
+
+
+## health
+
+
+
+### Check alive status
+
+```
+GET /health/alive HTTP/1.1
+Accept: application/json
+
+```
+
+This endpoint returns a 200 status code when the HTTP server is up running. This
+status does currently not include checks whether the database connection is
+working.
+
+If the service supports TLS Edge Termination, this endpoint does not require the
+`X-Forwarded-Proto` header to be set.
+
+Be aware that if you are running multiple nodes of this service, the health
+status will never refer to the cluster state, only to a single instance.
+
+#### Responses
+
+
+
+##### Overview
+
+| Status | Meaning | Description | Schema |
+| ------ | -------------------------------------------------------------------------- | ------------ | ----------------------------------- |
+| 200 | [OK](https://tools.ietf.org/html/rfc7231#section-6.3.1) | healthStatus | [healthStatus](#schemahealthstatus) |
+| 500 | [Internal Server Error](https://tools.ietf.org/html/rfc7231#section-6.6.1) | genericError | [genericError](#schemagenericerror) |
+
+##### Examples
+
+> 200 Response
+
+```json
+{
+ "status": "string"
+}
+```
+
+
+
+#### Code samples
+
+