fix code blocks after formatting

Author: LadyBluenotes

.prettierrc

@@ -3,5 +3,14 @@
 	"tabWidth": 2,
 	"semi": true,
 	"singleQuote": false,
-	"useTabs": true
+	"useTabs": true,
+	"overrides": [
+		{
+			"files": "*.mdx",
+			"options": {
+				"proseWrap": "never",
+				"parser": "mdx"
+			}
+		}
+	]
 }

CONTRIBUTING.md

@@ -2,27 +2,21 @@
 
 Thank you for helping us make this project great and being a part of the Solid community!
 
-We welcome contributions from anyone, regardless of your skill level.
-We are happy to help with guidance on PRs, technical writing, and turning features into realities.
+We welcome contributions from anyone, regardless of your skill level. We are happy to help with guidance on PRs, technical writing, and turning features into realities.
 
-> **New to contributing?**
-> Take a look at [this GitHub guide](https://docs.github.com/en/get-started/start-your-journey/hello-world) to learn how to use Git and GitHub to contribute to open-source.
+> **New to contributing?** Take a look at [this GitHub guide](https://docs.github.com/en/get-started/start-your-journey/hello-world) to learn how to use Git and GitHub to contribute to open-source.
 
 If you're new to Solid, we ask that you check out our [Writing Guide](https://github.com/solidjs/solid-docs-next/blob/main/WRITING.md).
 
 ## Types of contributions
 
 There are many ways to contribute to the Solid's documentation!
 
-The Solid Docs website is built on Solid!
-Maintaining it requires not only written content and Solid code maintenance, but it also needs to address accessibility (a11y), CSS, UI, and UX concerns.
-We also aim to make our documentation available in several languages, so we need help translating the entire site.
+The Solid Docs website is built on Solid! Maintaining it requires not only written content and Solid code maintenance, but it also needs to address accessibility (a11y), CSS, UI, and UX concerns. We also aim to make our documentation available in several languages, so we need help translating the entire site.
 
 You can help out by leaving review comments on [PRs](https://github.com/solidjs/solid-docs-next/pulls) and adding ideas in existing GitHub [issues ](https://github.com/solidjs/solid-docs-next/issues) and [discussions](https://github.com/solidjs/solid-docs-next/discussions).
 
-Every PR, especially translation PRs, will need reviewers.
-Reviewing PRs and leaving comments, suggestions, or even saying "Looks good!" can be a great way to get started on contributing alongside our Docs team.
-It's also a great way to learn more about Solid!
+Every PR, especially translation PRs, will need reviewers. Reviewing PRs and leaving comments, suggestions, or even saying "Looks good!" can be a great way to get started on contributing alongside our Docs team. It's also a great way to learn more about Solid!
 
 We encourage you to:
 
@@ -71,8 +65,7 @@ We use labels as a way to organize and categorize our issues. Here are some comm
 
 ## Start a discussion
 
-Discussions are a place within this repository where we can have open-ended conversations.
-It's the perfect place for Q&A, sharing ideas, community engagement, and connecting with other members.
+Discussions are a place within this repository where we can have open-ended conversations. It's the perfect place for Q&A, sharing ideas, community engagement, and connecting with other members.
 
 Feel free to start a [new discussion](https://github.com/solidjs/solid-docs-next/discussions) on any topic related to our docs!
 
@@ -87,25 +80,22 @@ Feel free to start a [new discussion](https://github.com/solidjs/solid-docs-n
 
 > If you've never submitted a pull request on GitHub before, check out [this overview on how to open a PR](https://opensource.guide/how-to-contribute/#opening-a-pull-request).
 
-PRs are the heart of collaboration on GitHub.
-When you open a pull request, you are putting forward your suggested changes, inviting us to review it, and requesting for these changes to be merged into our main branch.
+PRs are the heart of collaboration on GitHub. When you open a pull request, you are putting forward your suggested changes, inviting us to review it, and requesting for these changes to be merged into our main branch.
 
 Here's how to effectively contribute via a PR:
 
 - **Understand the Scope**: Before creating a PR, ensure it addresses an existing issue. Remember to link your PR to the issue it solves for easy tracking and understanding.
 - **Singular Focus**: Each PR should address a single issue or enhancement. Want to propose a larger change? Reach out to us on [Discord](https://discord.com/invite/solidjs) and let's discuss the best way forward!
 - **Drafts for Early Feedback**: If you're seeking early feedback but aren't quite finished with your changes, consider creating a draft PR. Simply prefix your PR title with `**[Draft]**`. This way, you can get input on your work-in-progress.
-- **Quality over Quantity**: Strive for the quality of your contribution rather than the quantity. A well-thought-out, cleanly coded, and thoroughly tested PR is much more valuable than a hastily done large one.
-  Contributing via PRs not only enhances the project, but also allows you to be a part of the active community, sharing ideas, learning, and growing with the project.
+- **Quality over Quantity**: Strive for the quality of your contribution rather than the quantity. A well-thought-out, cleanly coded, and thoroughly tested PR is much more valuable than a hastily done large one. Contributing via PRs not only enhances the project, but also allows you to be a part of the active community, sharing ideas, learning, and growing with the project.
 
 > Existing PRs and Issues need reviewing, triaging, and feedback, too! You can make valuable contributions by commenting, suggesting, testing, researching, brainstorming and generally helping in all areas!
 
 ### Writing a PR
 
 > Need help making a PR? [Join us on Discord](https://discord.com/invite/solidjs), we'll be more than happy to help you out!
 
-Contributions to the documentation site are made by editing the docs repository.
-You can do this directly on GitHub.com or by creating a copy of the repository locally, making your changes there, and contributing back to our repository.
+Contributions to the documentation site are made by editing the docs repository. You can do this directly on GitHub.com or by creating a copy of the repository locally, making your changes there, and contributing back to our repository.
 
 #### Examples of helpful PRs
 
@@ -115,11 +105,9 @@ You can do this directly on GitHub.com or by creating a copy of the repository l
 
 ### Edit this page via GitHub
 
-Every page on [docs.solidjs.com](https://docs.solidjs.com/) has an **Edit this page** link at the bottom.
-You can click on that button to edit the source code for that page in **GitHub**.
+Every page on [docs.solidjs.com](https://docs.solidjs.com/) has an **Edit this page** link at the bottom. You can click on that button to edit the source code for that page in **GitHub**.
 
-After you make your changes, click **Commit changes**.
-This will automatically create a [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) of the docs in your GitHub account with the changes.
+After you make your changes, click **Commit changes**. This will automatically create a [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) of the docs in your GitHub account with the changes.
 
 Once you have committed your edits within your fork, follow the prompts to create a **pull request** and submit your changes for review.
 
@@ -153,13 +141,11 @@ To translate a new entry to an existing language, go to `src/routes/{locale}` an
 
 Once you have made your changes using your preferred method, you're ready to create a 'pull request'.
 
-This will let the Solid docs team know you have some changes you would like to propose.
-At this point, we can give you feedback and possibly request changes.
+This will let the Solid docs team know you have some changes you would like to propose. At this point, we can give you feedback and possibly request changes.
 
 [Read more about making a pull request in GitHub's docs.](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project#making-a-pull-request)
 
-Please include a clear title.
-The description will have some pre-filled questions that we would like you to answer.
+Please include a clear title. The description will have some pre-filled questions that we would like you to answer.
 
 Every pull request generates a preview of the site, including your proposed changes, using **Netlify** for anyone to see.
 
@@ -171,21 +157,17 @@ The docs site will be automatically updated whenever pull requests are merged.
 
 ### Forks
 
-On GitHub, you will need a 'fork' of this repository to work on.
-This is your own copy of the code base where you can make changes. You can read more about forks in [GitHub's documentation](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project).
+On GitHub, you will need a 'fork' of this repository to work on. This is your own copy of the code base where you can make changes. You can read more about forks in [GitHub's documentation](https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project).
 
-Not sure how to get started with GitHub, forks, pull requests, or want a refresher?
-You can watch this video series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
+Not sure how to get started with GitHub, forks, pull requests, or want a refresher? You can watch this video series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
 
 #### Creating a fork
 
 To create your copy, click the `Fork` button at the top right of any page in this repository.
 
 #### Maintaining a fork
 
-When you first create your fork, it will be an exact copy of this repository.
-Over time, our docs will change as they are updated, but your fork won’t automatically stay up-to-date.
-Here are some ways to keep your fork in sync with this repo:
+When you first create your fork, it will be an exact copy of this repository. Over time, our docs will change as they are updated, but your fork won’t automatically stay up-to-date. Here are some ways to keep your fork in sync with this repo:
 
 ##### Update through GitHub UI
 

README.md

@@ -2,75 +2,49 @@
 
 Welcome to Solid's documentation!
 
-This is the repo for [docs.solidjs.com](https://docs.solidjs.com/). This repo
-contains all the source code that we use to build our docs.
+This is the repo for [docs.solidjs.com](https://docs.solidjs.com/). This repo contains all the source code that we use to build our docs.
 
-[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/solidjs/solid-docs-next)
-[![Open with CodeSandbox](https://assets.codesandbox.io/github/button-edit-lime.svg)](https://codesandbox.io/p/github/solidjs/solid-docs-next/)
-[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/solidjs/solid-docs-next)
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/solidjs/solid-docs-next) [![Open with CodeSandbox](https://assets.codesandbox.io/github/button-edit-lime.svg)](https://codesandbox.io/p/github/solidjs/solid-docs-next/) [![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/solidjs/solid-docs-next)
 
 ## What is Solid?
 
-Solid is a JavaScript framework used for building high-performance
-user-interfaces. Using a reactive approach and component-based architecture, we
-want to empower developers in creating efficient and scalable web applications.
+Solid is a JavaScript framework used for building high-performance user-interfaces. Using a reactive approach and component-based architecture, we want to empower developers in creating efficient and scalable web applications.
 
 ## Thank you for being here!
 
-You can help make our docs better for the community! Your feedback is welcomed.
-In addition, any editing, translating, designing, and developing skills are
-welcomed. We are grateful to welcome you into our community!
+You can help make our docs better for the community! Your feedback is welcomed. In addition, any editing, translating, designing, and developing skills are welcomed. We are grateful to welcome you into our community!
 
-If you want to see how you can contribute, check out our
-[How You Can Help](#how-you-can-help) section.
+If you want to see how you can contribute, check out our [How You Can Help](#how-you-can-help) section.
 
 ## Chat with us
 
-You can learn more about Solid, get support, and meet other devs and
-contributors in our [Discord community](https://discord.com/invite/solidjs).
+You can learn more about Solid, get support, and meet other devs and contributors in our [Discord community](https://discord.com/invite/solidjs).
 
 ## Raise an issue
 
-Have you noticed something is missing, confusing, or is wrong in our
-documentation?
+Have you noticed something is missing, confusing, or is wrong in our documentation?
 
-Check to see if it has
-[already been mentioned ](https://github.com/solidjs/solid-docs-next/issues)
-and, if not,
-[create an issue](https://github.com/solidjs/solid-docs-next/issues/new/choose)
-to bring it to our attention!
+Check to see if it has [already been mentioned ](https://github.com/solidjs/solid-docs-next/issues) and, if not, [create an issue](https://github.com/solidjs/solid-docs-next/issues/new/choose) to bring it to our attention!
 
 ## Share an idea
 
-Do you think something could be better? Have an idea you feel could make the
-docs better?
+Do you think something could be better? Have an idea you feel could make the docs better?
 
-Discussion threads are where you can offer feedback on things that might not be
-problems that need addressing, but are ideas to be explored.
+Discussion threads are where you can offer feedback on things that might not be problems that need addressing, but are ideas to be explored.
 
-Join us in the
-[Discussions section](https://github.com/solidjs/solid-docs-next/discussions/280)
-where we can brainstorm these ideas, ask questions, and share goals!
+Join us in the [Discussions section](https://github.com/solidjs/solid-docs-next/discussions/280) where we can brainstorm these ideas, ask questions, and share goals!
 
 ## Suggest a fix or contribute
 
 Have you found a typo, broken link, or another item with an obvious quick fix?
 
-If you can see what the problem is, and you know how to fix it, you can make a
-PR (pull request) with the change and contribute to the docs repo yourself.
+If you can see what the problem is, and you know how to fix it, you can make a PR (pull request) with the change and contribute to the docs repo yourself.
 
-If you're looking to make a larger contribution, please see our
-[CONTRIBUTING.md](https://github.com/solidjs/solid-docs-next/blob/main/CONTRIBUTING.md)
-first!
+If you're looking to make a larger contribution, please see our [CONTRIBUTING.md](https://github.com/solidjs/solid-docs-next/blob/main/CONTRIBUTING.md) first!
 
 ## Running the Site Locally
 
-At the moment, we recommend running the site locally through either
-[CodeSandbox](https://codesandbox.io/p/github/solidjs/solid-docs-next/),
-[Gitpod](https://gitpod.io/#https://github.com/solidjs/solid-docs-next), or
-[StackBlitz](https://stackblitz.com/github/solidjs/solid-docs-next). These are
-the quickest and easiest way to browse and edit the project files and run the
-site locally.
+At the moment, we recommend running the site locally through either [CodeSandbox](https://codesandbox.io/p/github/solidjs/solid-docs-next/), [Gitpod](https://gitpod.io/#https://github.com/solidjs/solid-docs-next), or [StackBlitz](https://stackblitz.com/github/solidjs/solid-docs-next). These are the quickest and easiest way to browse and edit the project files and run the site locally.
 
 The app uses [pnpm](https://pnpm.io) as the package manager and it runs on Node.js `v18+`.
 
@@ -90,7 +64,6 @@ This will start your the app at [localhost:3000](http://localhost:3000) or the n
 
 ### Collections and virtual modules
 
-The builds an [Astro](https://docs.astro.build/en/guides/content-collections/) inspired collection navigation, it will bring all routes and generate a couple of files at `/.solid`.
-These files are exposed to your app via [Vite virtual modules](https://vitejs.dev/guide/api-plugin#virtual-modules-convention). This task is perform via our `sync` script (`pnpm sync`), ran before every build.
+The builds an [Astro](https://docs.astro.build/en/guides/content-collections/) inspired collection navigation, it will bring all routes and generate a couple of files at `/.solid`. These files are exposed to your app via [Vite virtual modules](https://vitejs.dev/guide/api-plugin#virtual-modules-convention). This task is perform via our `sync` script (`pnpm sync`), ran before every build.
 
 If changes are made to the navigation (new entry, or repositioning entry), it is necessary to restart the server for changes to take effect.