Add info about standalone output mode and benefits

[atharvadeosthale]

Summary by CodeRabbit

• Documentation
  • Clarified Next.js SSR guidance for the output configuration, replacing prior terse guidance with a clear description of supported output modes.
  • Added explicit explanation of Default vs Standalone modes and recommended Standalone for smaller builds and faster cold-starts.
  • Included a configuration example and practical recommendations for choosing an output mode.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request updates a single Markdoc file (src/routes/docs/products/sites/rendering/ssr/+page.markdoc). In the Next.js section it replaces the brief prohibition about setting output with a multi-line explanation of supported output modes: default (no output config required) and standalone (set output: 'standalone' for smaller builds and faster cold starts). A short next.config.js example and notes about build characteristics were added. No other framework sections or code logic were changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single documentation file changed.
• Changes are textual: descriptive additions and a short config snippet.
• Review focus:
  • Confirm wording accurately reflects Next.js output behavior.
  • Verify the next.config.js example is syntactically correct and matches repo style.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding documentation about Next.js standalone output mode and its benefits (smaller builds and faster cold starts).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch standalone-docs

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c29b92 and 4019130.

📒 Files selected for processing (1)

• src/routes/docs/products/sites/rendering/ssr/+page.markdoc

🚧 Files skipped from review as they are similar to previous changes (1)

• src/routes/docs/products/sites/rendering/ssr/+page.markdoc

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build
• GitHub Check: assets
• GitHub Check: tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/partials/next-standalone-note.md (1)

1-5: Tighten wording for benefits sentence

The message is clear, but the benefits sentence reads a bit awkwardly; a small copy edit improves flow.

-For Next.js builds, you may use the standalone output mode to get smaller build sizes, lesser build times and cold start times.
+For Next.js builds, you can use the standalone output mode to get smaller build sizes, shorter build times, and faster cold starts.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 987b016 and a4d5c41.

📒 Files selected for processing (3)

• src/partials/next-standalone-note.md (1 hunks)
• src/routes/docs/products/sites/quick-start/nextjs/+page.markdoc (1 hunks)
• src/routes/docs/products/sites/rendering/ssr/+page.markdoc (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-11-18T21:53:20.905Z

Learnt from: atharvadeosthale
Repo: appwrite/website PR: 2614
File: src/routes/docs/products/sites/one-click-deployment/+page.markdoc:74-122
Timestamp: 2025-11-18T21:53:20.905Z
Learning: Appwrite Sites one-click deployment supports the following framework presets: Analog (analog), Angular (angular), Next.js (nextjs), React (react), Nuxt (nuxt), Vue (vue), SvelteKit (sveltekit), Astro (astro), TanStack Start (tanstack-start), Remix (remix), Lynx (lynx), Flutter (flutter), React Native (react-native), Vite (vite), and Other (other).

Applied to files:

• src/partials/next-standalone-note.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: diagnostics
• GitHub Check: assets

🔇 Additional comments (1)

src/routes/docs/products/sites/quick-start/nextjs/+page.markdoc (1)

51-52: Partial inclusion and placement look good

Reusing the shared Next.js standalone note here keeps the quick start DRY and surfaces the optimization tip at the right moment. No changes needed.

[adityaoberai]

@atharvadeosthale, our docs must not rely on blogs; it should be the other way around.

I wouldn't create a partial for now. Also, instead of linking the blog, let's add how to set the mode on the SSR page within the Next.js tabsitem component.

Additionally, let's not include this in the quickstart. We want it to be a very quick hello world and not add any extra configuration steps.

[adityaoberai]

We need ensure it follows a consistent style for both kinds of setup

What I would do here is mention what kind of modes can be setup as points and give a one line definition of how they can be setup, which is how all SSR docs are listed