Create a new guide for Outline, team knowledge base and wiki

[LostInBrittany]

This PR introduces a deployment guide for Outline, anopen-source team knowledge base and wiki platform that enables organizations to create, organize, and collaborate on documentation.

The guide walks users through the complete deployment process on Clever Cloud, including setting up the necessary infrastructure (Node.js application, PostgreSQL database, Redis cache, and Cellar S3 storage), configuring S3 bucket policies and CORS settings, and establishing OAuth authentication with popular providers like Google, Slack, Discord, and Microsoft.

This addition expands our platform's documentation coverage for modern collaborative tools and provides users with a clear path to deploy their own knowledge management system.

[github-actions]

✅ Review app deployed

Check how your changes look like!

ℹ️ Name	🔗 Infos & links
🌱 Latest deployed commit	9ced034
👁️ Preview	https://documentation-PR-766.cleverapps.io/developers

[Copilot]

Pull request overview

Adds a new deployment guide for Outline on Clever Cloud, plus the supporting navigation entry and icon.

Changes:

• Add an Outline deployment guide covering app/add-ons setup, S3 (Cellar) configuration, and OAuth providers.
• Register a new outline icon in data/icons.yaml for use in cards.
• Add Outline to the guides index cards list.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 14 comments.

File	Description
data/icons.yaml	Adds an outline SVG icon for use in guide cards.
content/guides/outline.md	Introduces a full Outline deployment guide (Node.js + Postgres + Redis + Cellar + OAuth).
content/guides/_index.md	Adds Outline to the guides landing page cards.

Comments suppressed due to low confidence (1)

content/guides/outline.md:235

• In the “Further Help” cards, the PostgreSQL card uses icon="mysql", which will render the wrong icon. Use the PostgreSQL icon key (e.g. pg) to match the title/link.

[Copilot]

In Markdown headings, <secret_key> / <utils_secret> can be interpreted as HTML tags and may not render as intended. Use backticks (e.g. SECRET_KEY / UTILS_SECRET) or plain text instead of angle brackets.

[Copilot]

The S3 region guidance is inconsistent: this section suggests us-east-1, but earlier the env example sets AWS_REGION="us". Align the region values (and the wording) so users don’t end up with mismatched configuration.

[Copilot]

The s3cmd setpolicy command is missing the closing > in s3://<bucket_name>, which makes the placeholder unclear/incorrect. Fix to a consistent placeholder form (e.g. s3://<bucket-name>).

[Copilot]

The CORS example allows PUT/POST/DELETE from any origin (<AllowedOrigin>*</AllowedOrigin>). This is much more permissive than the Cellar docs example and can enable unwanted cross-origin writes. Restrict AllowedOrigin for write methods to the Outline domain (and keep * only if you intentionally want public cross-origin access).

[Copilot]

Grammar: use "a URL" (not "an URL").

[Copilot]

The s3cmd setcors command is missing the closing > in s3://<bucket_name>. Fix the placeholder so the command can be copied reliably (e.g. s3://<bucket-name>).

[Copilot]

The new outline icon SVG path doesn’t set fill="currentColor" (unlike neighbouring icons such as meteor/moodle), so it may render with a default fill and not follow theme colours. Add fill="currentColor" (or equivalent) to keep icon rendering consistent.

[Copilot]

The page front matter still uses "Moodle" for both linkTitle and title, so this guide will be listed/rendered as Moodle instead of Outline. Update these fields to "Outline" (and ensure they match the file’s purpose).

[Copilot]

The Markdown link is reversed: the visible text is the URL and the link target is "GitHub". Swap them so the link text is "GitHub" (or "Outline releases") and the href is https://github.com/outline/outline/releases.

[Copilot]

Configuring the S3 bucket policy with Principal: "*", Effect: "Allow", and Action: ["s3:GetObject"] on arn:aws:s3:::$BUCKET/* makes every object in the Outline storage bucket world-readable. For a private team knowledge base, this bypasses application-level access controls and allows anyone who learns or intercepts an object URL to retrieve potentially sensitive documents without authentication. Instead, keep the bucket private and grant access only to the Outline service identity (or use pre-signed URLs) so that S3 enforces the same access boundaries as the application.

[davlgd]

Thanks for this!

I've updated title (it was Moodle), icon color, remove some extra lines. Here are some comments & nitpicks, I let you update and check copilot comments. I'll rebase and merge after that.

[davlgd]

Suggested change

	As explained in the [Cellar S3 doc](https://www.clever.cloud/developers/doc/addons/cellar/), Buckets' names are global for every region. You can’t give the same name to two different buckets in the same region, because the URL already exists in the Cellar cluster on this region.
	As explained in the [Cellar Object Storage documentation](https://www.clever.cloud/developers/doc/addons/cellar/), Buckets' names are global for every region. You can’t give the same name to two different buckets in the same region, because the URL already exists in the Cellar cluster on this region.

Maybe too much "region" and we can make this sentence simpler/less repetitive

[davlgd]

Suggested change

	Outline needs an URL declared in variables to work properly. You can set it up in **Domains names**, from your application menu. If you don't have a domain name yet, you can use a `cleverapp.io` subdomain provided by Clever Cloud for test purposes.
	Outline needs its public URL to be declared in an environment variables to work properly. You can set it up in **Domains names**, from your application menu. If you don't have a domain name yet, you can use a `cleverapps.io` subdomain provided by Clever Cloud for test purposes.

[davlgd]

Suggested change

	In a Linux/Mac shell:
	In a Linux/macOS shell:

[davlgd]

Maybe this needs more explanations

[davlgd]

unnecessary (all apps have this env var by default)

[davlgd]

NODE_ENV="production" is already set?

Suggested change

	CC_POST_BUILD_HOOK="NODE_ENV=production && yarn build"
	CC_POST_BUILD_HOOK="yarn build"

[davlgd]

You use yarn build, but not yarn berry to install dependencies ? (see https://www.clever.cloud/developers/doc/applications/nodejs/#supported-package-managers)

[davlgd]

Better to link add-ons and to have a pre-run binding script for that (see oTree guide example). If credentials change, there is nothing to do. With fixed env var, you need to update them.

Maybe add comments to last three AWS_ env vars to explain why these values.

[davlgd]

Policy allows only read, not write?

[davlgd]

why not just git clone ?

[davlgd]

Maybe clever deploy is a better option here and it will work great with git clone. We can also talk about GitHub fork if GitHub account is linked to Clever Cloud account. A push on the fork and its deployed.