-
Notifications
You must be signed in to change notification settings - Fork 29.9k
Add Appwrite Sites to supported adapters #85830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feedthejim
approved these changes
Nov 8, 2025
huozhi
pushed a commit
that referenced
this pull request
Nov 12, 2025
<!-- 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
huozhi
pushed a commit
that referenced
this pull request
Nov 12, 2025
<!-- 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
Moroshima
pushed a commit
to Moroshima/next.js
that referenced
this pull request
Nov 20, 2025
<!-- 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
CI approved
Approve running CI for fork
Documentation
Related to Next.js' official documentation.
locked
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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