Finish first draft of landing/documentation website

[ernestoresende]

Draft the initial documentation content for the documentation website. Initially planned structure:

Overview

• Introduction: Briefly introduce the project, core principles and point towads support and contribution guidelines.
• Why Cardinal: Explain the rationale behind why a developer could choose Cardinal over other create-***-app solutions, and bring a overview of the included tech. (9e32603)
• Recommendations: This is aimed at users who are still choosing their stack. Provide recommendations based on project type, budget, and developer experience level. (6f6b221)

Usage

• New Project: Instructions on how to setup a new project with Cardinal.
• First steps: Post scaffolding setup instructions. Some scaffolded projects will still require the user to perform post-install tasks, like configuring and supplying correct environment variables for parts of the stack. Most things here will backlink to the specific "stack part" page.

Frameworks

• Next.js: Next.js specific instructions, mostly pointing to their docs.

Backend

• REST: Describe how REST API's are authored depending on the combination of deployment provider and framework.
• GraphQL: Describe how GraphQL API's are authored, and how to use the GraphQL client on server and client components/runtimes.
• tRPC: Describe how tRPC API's are authored, and how to call procedures from both server and client runtimes.

Authentication

• Lucia: Reinforce core things about the authentication layer in Cardinal (Lucia, server-only, abstractions for low-level primitives)
• Security considerations: A refresher on auth security topics.
• Add new authentication methods: A top level overview of how to implement some other authentication methods (tokens, magic link, OAuth).
• Session handling: Describe how Lucia creates sessions by default, and cases in which you may want to override it's behavior. Advise caution when doing so.

Database

• Database connection: Per-platform instructions of where to get the credentials needed to stabilish the database connection
• Prototyping and migrations: Some general recommendations on how you can prototype database schemas with either drizzle-kit push (when applicable), or database migrations.

Configuration

• Environment variables: Describe how environment variables should be declared, managed, and how they are checked during runtime.
• Prettier & ESLint: Describe how Cardinal scaffolds and pre-configures Prettier and ESLint, and where/how you might want to extend them