Format all the old docs

Author: lucacasonato

.github/CODE_OF_CONDUCT.md

@@ -2,127 +2,78 @@
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our
-community include:
+Examples of behavior that contributes to a positive environment for our community include:
 
 - Demonstrating empathy and kindness toward other people
 - Being respectful of differing opinions, viewpoints, and experiences
 - Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall
-  community
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
 
 Examples of unacceptable behavior include:
 
-- The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
 - Trolling, insulting or derogatory comments, and personal or political attacks
 - Public or private harassment
-- Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
 
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at hello@lcas.dev.
-All complaints will be reviewed and investigated promptly and fairly.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at hello@lcas.dev. All complaints will be reviewed and investigated promptly and fairly.
 
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
 
 ## Enforcement Guidelines
 
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
 
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series of
-actions.
+**Community Impact**: A violation through a single incident or series of actions.
 
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
 
 ### 3. Temporary Ban
 
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
 
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
 
 ### 4. Permanent Ban
 
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
 
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
+**Consequence**: A permanent ban from any sort of public interaction within the community.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
 
 [homepage]: https://www.contributor-covenant.org
 
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

www/docs/1.x/concepts/ahead-of-time-builds.md

@@ -3,20 +3,11 @@ description: |
   Fresh optimize assets ahead of time, which makes pages load way quicker.
 ---
 
-Fresh enables you to pre-optimize frontend assets before the code is deployed.
-During that process the code for Islands will be compressed and optimized, so
-that Fresh can send as little code as possible to the browser. Depending on the
-amount of code an island needs, this process can take several seconds if done on
-the fly server-side.
+Fresh enables you to pre-optimize frontend assets before the code is deployed. During that process the code for Islands will be compressed and optimized, so that Fresh can send as little code as possible to the browser. Depending on the amount of code an island needs, this process can take several seconds if done on the fly server-side.
 
-Doing those optimizations ahead-of-time and deploying the already optimized
-assets alongside with your code, allows Fresh to treat them as like any other
-static file and can serve it immediately without any further processing. On
-pages with islands, having to do no processing greatly speeds up page load
-times.
+Doing those optimizations ahead-of-time and deploying the already optimized assets alongside with your code, allows Fresh to treat them as like any other static file and can serve it immediately without any further processing. On pages with islands, having to do no processing greatly speeds up page load times.
 
-Plugins can build static assets during ahead-of-time builds. This can be used to
-pre-process or generate CSS files, for example.
+Plugins can build static assets during ahead-of-time builds. This can be used to pre-process or generate CSS files, for example.
 
 ## Creating an optimized build
 
@@ -29,17 +20,11 @@ deno task build
 deno run -A dev.ts build
 ```
 
-This will create a `_fresh` folder in the project directory. That folder
-contains the optimized assets and a `snapshot.json` file which includes some
-metadata for Fresh.
+This will create a `_fresh` folder in the project directory. That folder contains the optimized assets and a `snapshot.json` file which includes some metadata for Fresh.
 
-Any other static files generated by plugins will be stored in the
-`_fresh/static` subfolder. They will be served the same as other
-[static files](/docs/1.x/concepts/static-files.md).
+Any other static files generated by plugins will be stored in the `_fresh/static` subfolder. They will be served the same as other [static files](/docs/1.x/concepts/static-files.md).
 
-> [info]: The `_fresh` folder should not be committed to the repository. Add an
-> entry in the `.gitignore` file to ensure that it is not committed. Create that
-> file at the root of your git repository if not present.
+> [info]: The `_fresh` folder should not be committed to the repository. Add an entry in the `.gitignore` file to ensure that it is not committed. Create that file at the root of your git repository if not present.
 >
 > ```gitignore .gitignore
 > # Ignore fresh build directory
@@ -48,29 +33,21 @@ Any other static files generated by plugins will be stored in the
 
 ## Running Fresh with optimized assets
 
-When Fresh is started in non-development mode (usually via `main.ts`), Fresh
-will automatically pick up optimized assets when a `_fresh` folder exists. If
-found, Fresh will print the following message to the terminal:
+When Fresh is started in non-development mode (usually via `main.ts`), Fresh will automatically pick up optimized assets when a `_fresh` folder exists. If found, Fresh will print the following message to the terminal:
 
 ```sh Terminal output
 Using snapshot found at /path/to/project/_fresh
 ```
 
 ## Deploying an optimized Fresh project
 
-If you are deploying a Fresh project to Deno Deploy, you can use ahead-of-time
-builds to optimize the assets before deploying them. This will make your
-application load quicker.
+If you are deploying a Fresh project to Deno Deploy, you can use ahead-of-time builds to optimize the assets before deploying them. This will make your application load quicker.
 
-Open the Deno Deploy dashboard for your project and head to the "Git
-Integration" section in the project settings. Enter `deno task build` in the
-"Build command" field and save. This will switch your Deno Deploy project to use
-ahead-of-time builds.
+Open the Deno Deploy dashboard for your project and head to the "Git Integration" section in the project settings. Enter `deno task build` in the "Build command" field and save. This will switch your Deno Deploy project to use ahead-of-time builds.
 
 ## Migrating existing projects with Plugins
 
-If you're using Fresh plugins, extract them into a `fresh.config.ts` file, so
-that both the `dev.ts` and `main.ts` script have access to them.
+If you're using Fresh plugins, extract them into a `fresh.config.ts` file, so that both the `dev.ts` and `main.ts` script have access to them.
 
 ```ts fresh.config.ts
 import { defineConfig } from "$fresh/server.ts";

www/docs/1.x/concepts/app-wrapper.md

@@ -3,15 +3,9 @@ description: |
   Add a global app wrapper to provide common meta tags or context for application routes.
 ---
 
-An app wrapper is defined in an `_app.tsx` file in `routes/` folder and is
-typically used to create the outer structure of an HTML document. It must
-contain a default export that is a regular Preact component. Only one such
-wrapper is allowed per application.
+An app wrapper is defined in an `_app.tsx` file in `routes/` folder and is typically used to create the outer structure of an HTML document. It must contain a default export that is a regular Preact component. Only one such wrapper is allowed per application.
 
-The component to be wrapped is received via props, in addition to a few other
-things. This allows for the introduction of a global container functioning as a
-template which can be conditioned based on state and params. Note that any state
-set by middleware is available via `props.state`.
+The component to be wrapped is received via props, in addition to a few other things. This allows for the introduction of a global container functioning as a template which can be conditioned based on state and params. Note that any state set by middleware is available via `props.state`.
 
 ```tsx routes/_app.tsx
 import { PageProps } from "$fresh/server.ts";
@@ -35,9 +29,7 @@ export default function App({ Component, state }: PageProps) {
 
 ## Async app wrapper
 
-Similar to routes and layouts, the app wrapper can be made asynchronous. This
-changes the function signature so that the first argument is the `Request`
-instance and the second one is the `FreshContext`.
+Similar to routes and layouts, the app wrapper can be made asynchronous. This changes the function signature so that the first argument is the `Request` instance and the second one is the `FreshContext`.
 
 ```tsx routes/_app.tsx
 import { FreshContext } from "$fresh/server.ts";
@@ -63,8 +55,7 @@ export default async function App(req: Request, ctx: FreshContext) {
 
 ### Define helper
 
-To make it quicker to type the async app wrapper, Fresh includes a `defineApp`
-helper which already infers the correct types for you.
+To make it quicker to type the async app wrapper, Fresh includes a `defineApp` helper which already infers the correct types for you.
 
 ```tsx routes/_app.tsx
 import { defineApp } from "$fresh/server.ts";
@@ -90,8 +81,7 @@ export default defineApp(async (req, ctx) => {
 
 ## Disabling the app wrapper
 
-Rendering the app wrapper can be skipped on a route or layout basis. To do that,
-set `skipAppWrapper: true` to the layout or route config.
+Rendering the app wrapper can be skipped on a route or layout basis. To do that, set `skipAppWrapper: true` to the layout or route config.
 
 ```tsx routes/my-special-route.tsx
 import { RouteConfig } from "$fresh/server.ts";

www/docs/1.x/concepts/architecture.md

@@ -3,23 +3,13 @@ description: |
   Fresh's architecture is designed to make it easy to build fast, scalable, and reliable applications.
 ---
 
-Fresh is designed to make it easy to build fast, scalable, and reliable
-applications. To do this, it makes opinionated decisions about how one should
-build web applications. These decisions are backed by strong empirical data
-gathered from experts in the field. Some examples of these principles are:
+Fresh is designed to make it easy to build fast, scalable, and reliable applications. To do this, it makes opinionated decisions about how one should build web applications. These decisions are backed by strong empirical data gathered from experts in the field. Some examples of these principles are:
 
 - Page load times should be reduced to a minimum.
 - The work performed on the client should be minimized.
 - Errors should have a small blast radius - stuff should gracefully degrade.
 
-The single biggest architecture decision that Fresh makes is its usage of the
-[islands architecture][islands] pattern. This means that Fresh applications ship
-pure HTML to the client by default. Parts of a server-rendered page can then be
-independently re-hydrated with interactive widgets (islands). This means that
-the client is only responsible for rendering parts of the page that are
-interactive enough to warrant the extra effort. Any content that is purely
-static does not have related client-side JavaScript and is thus very
-lightweight.
+The single biggest architecture decision that Fresh makes is its usage of the [islands architecture][islands] pattern. This means that Fresh applications ship pure HTML to the client by default. Parts of a server-rendered page can then be independently re-hydrated with interactive widgets (islands). This means that the client is only responsible for rendering parts of the page that are interactive enough to warrant the extra effort. Any content that is purely static does not have related client-side JavaScript and is thus very lightweight.
 
 <!-- TODO(lucacasonato): elaborate on request handling, form actions, etc. -->