Repository: vercel/next.js
Pull request: Add Appwrite Sites to supported adapters

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change

### What?

Added Appwrite Sites to the list of deployment adapters in the deploying documentation.

### Why?

Appwrite Sites is a deployment platform that uses an adapter to run Next.js applications on their infrastructure, similar to other platforms listed in the Adapters section (Cloudflare, Netlify, AWS Amplify, etc.). This addition helps developers discover Appwrite Sites as a deployment option for their Next.js applications.

### How?

Added a link to Appwrite Sites documentation (https://appwrite.io/docs/products/sites/quick-start/nextjs in the Adapters section of 17-deploying.mdx

Closes NEXT-
Fixes #

-->

### What?

Added Appwrite Sites to the list of deployment adapters in the deploying documentation.

### Why?

Appwrite Sites is a deployment platform that uses an adapter to run Next.js applications on their infrastructure, similar to other platforms listed in the Adapters section (Cloudflare, Netlify, AWS Amplify, etc.). This addition helps developers discover Appwrite Sites as a deployment option for their Next.js applications.

### How?

Added a link to Appwrite Sites documentation (https://appwrite.io/docs/products/sites/quick-start/nextjs in the Adapters section of 17-deploying.mdx

Changed files:
filename: docs/01-app/01-getting-started/17-deploying.mdx
patch: @@ -72,6 +72,7 @@ Next.js can be adapted to run on different platforms to support their infrastruc
 
 Refer to each provider's documentation for information on supported Next.js features:
 
+- [Appwrite Sites](https://appwrite.io/docs/products/sites/quick-start/nextjs)
 - [AWS Amplify Hosting](https://docs.amplify.aws/nextjs/start/quickstart/nextjs-app-router-client-components)
 - [Cloudflare](https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs)
 - [Deno Deploy](https://docs.deno.com/examples/next_tutorial)