Skip to content

docs(cloud): Rewrite Introduction, refresh Install scloud, relabel Get started#578

Open
developerjamiu wants to merge 2 commits into
mainfrom
docs/cloud-introduction-rewrite
Open

docs(cloud): Rewrite Introduction, refresh Install scloud, relabel Get started#578
developerjamiu wants to merge 2 commits into
mainfrom
docs/cloud-introduction-rewrite

Conversation

@developerjamiu
Copy link
Copy Markdown
Contributor

@developerjamiu developerjamiu commented Jun 4, 2026

First PR of the Cloud IA rollout (#568).

Changes

  • cloud_docs/index.md: Introduction rewritten from a feature tour into a conceptual overview. Drops the 8 H2 sections in favour of a short pitch, a small code sample, a "What Cloud manages" bullet list, and "Where to go next" links. Every capability the old page surfaced is preserved in bullet form (Flutter web hosting, Insights' database requirement, PubSub/caching/file storage roadmap).
  • cloud_docs/01-getting-started/01-installation.md: added title: Install scloud, retitled the page, swapped dart pub global activatedart install (the Dart 3.10+ install command), small wording cleanups.
  • cloud_docs/01-getting-started/_category_.json: sidebar label "Getting started" → "Get started".

I believe humans and LLMs will now find these pages easier to scan, understand and expand on through checking other pages (to be added or improved).

Verification

  • dart install --help and scloud launch --help confirm the commands.
  • npm run build passes.

What's next

PR 2: Deployments concept (NEW). PR 3: Deploy your first app rewrite (uses PR 2). Full rollout sequence in the #568 tracking comment.

New Intro:

image

New Installation:

image

@developerjamiu developerjamiu self-assigned this Jun 4, 2026
@developerjamiu developerjamiu requested review from Swiftaxe and Zfinix June 4, 2026 10:46
@developerjamiu developerjamiu added documentation Improvements or additions to documentation enhancement New feature or request labels Jun 4, 2026
Copy link
Copy Markdown
Contributor

@Zfinix Zfinix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, nice quality reduction, its easier to follow and more effcient

---

# Installation
# Install scloud
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a nice scloud banner immage would really upsell this page

Copy link
Copy Markdown
Collaborator

@Swiftaxe Swiftaxe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A really clean intro page! I added a few comments. I think of the user who may hesitate by "what do I commit to" when just launching my project to the cloud. Do we answer all the questions a user has before they are ready to move on to installation?

Comment thread cloud_docs/index.md
## Zero-configuration deployments

Deploy your Serverpod server directly from your project directory using the command line or integrate it into your CI/CD pipeline. No manual VM setup, container configuration, or infrastructure orchestration is needed.
Deploy is two commands. No Dockerfile, no container config, no infrastructure setup:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This first sentence "Deploy is two commands" is a bit fuzzy and confusing.
The actual deploy command after the launch is just scloud deploy.
Also, following this is the install command.

Does it mean something like "Your first deploy is two commands away"?

Comment thread cloud_docs/index.md
## What Cloud manages

The Serverpod framework has built-in support for sending messages between your servers, and caching objects works out of the box. We are working on building a service native to Serverpod Cloud; in the meantime, it's easy to configure a 3rd party service.
- **Runtime and scaling.** Your app runs on a production runtime that scales automatically.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new lightweight list is great. However, a user considering Serverpod Cloud for a serious production app might want to delve deeper into each section, or a specific section. Perhaps link out to a page containing more details on each feature (ie preserve the lengthier explanations on an in-depth page).

Comment thread cloud_docs/index.md
Serverpod Cloud comes with Serverpod Insights, our visual log viewer, preconfigured (requires a database). This gives you access to our world-class logging and server monitoring.

## PubSub and caching
## What Cloud manages
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better to use the Service's full name here.

Suggested change
## What Cloud manages
## What Serverpod Cloud manages

Comment thread cloud_docs/index.md

# Introduction

**Serverpod Cloud** is a fully managed hosting platform for Serverpod apps. It lets you deploy and run your Serverpod backend from the command line or via CI/CD. The platform manages all infrastructure needed to run your service in production. It can seamlessly scale to any size, and pricing is predictable. Serverpod Cloud handles networking, load balancing, custom domain names, and your database.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a decision page. We are dropping some important keywords for the user here, like 'predictable pricing,' which is not listed below.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants