Skip to content

Bifurcate Advanced > Platform docs into other relevant sections#3038

Open
adityaoberai wants to merge 3 commits into
mainfrom
bifurcate-platforms-docs
Open

Bifurcate Advanced > Platform docs into other relevant sections#3038
adityaoberai wants to merge 3 commits into
mainfrom
bifurcate-platforms-docs

Conversation

@adityaoberai
Copy link
Copy Markdown
Contributor

What does this PR do?

Breaks up the catch-all Advanced → Platform docs section, which had grown into an unrelated mix of billing, API integration, security, and product-specific pages. Its contents are redistributed into three focused homes plus the relevant product sections, so each page now lives where users actually look for it. Every moved URL is covered by a redirect, and all internal doc links, navigation, and overview pages are updated to match.

New sections

  • /docs/advanced/billing — new landing page + layout, covering plans, add-ons, SLAs, and billing policies.
  • /docs/advanced/api-integration — new landing page + layout (also absorbs the old /docs/advanced/integration stub), covering events, webhooks, and the API error reference.

Pages moved

From …/advanced/platform/… To
events, webhooks, response-codes, error-handling, release-policy …/advanced/api-integration/…
billingpayments, free, pro, scale, enterprise, oss, compute, phone-otp, image-transformations, database-reads-and-writes, support-sla, uptime-sla, fair-use-policy, abuse, refund-policy …/advanced/billing/…
roles, permissions, rate-limits, api-keys, dev-keys, environment-variables …/advanced/security/…
message-templates …/products/auth/…
custom-domains …/products/network/custom-domains
shortcuts …/tooling/command-center/shortcuts

Supporting updates

  • Redirects: added redirects from every old /docs/advanced/platform/* path (and /docs/advanced/platform/docs, /docs/advanced/integration/docs/advanced/api-integration) to its new home; repointed existing redirects (/docs/keys, /docs/permissions, /docs/events, /docs/webhooks, etc.).
  • Navigation: updated the docs sidebar and the Billing / API Integration / Security / Auth / Network / Command Center layouts to reflect the new structure.
  • Internal links: rewrote all /docs/** content links, partials, components, the init page, llms.txt generators, and STYLE.md to the new paths.
  • Overview pages: Security overview now surfaces the relocated Access control (Permissions, Rate limits, API keys, Dev keys) and Configuration (Environment variables) pages as cards.
  • Incidental fixes on the touched Security overview: corrected the TLS card (was pointing at the HTTPS page) and added a missing MFA card so the card grid matches the sidebar.

Test Plan

Visit all relevant sections in /docs

Related PRs and Issues

N/A

Have you read the Contributing Guidelines on issues?

Yes

@appwrite
Copy link
Copy Markdown

appwrite Bot commented Jun 3, 2026

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Building Building View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Building Building View Logs Preview URL QR Code


Tip

Silent mode disables those chatty PR comments if you prefer peace and quiet

@adityaoberai adityaoberai requested review from atharvadeosthale and eldadfux and removed request for eldadfux June 3, 2026 20:11
---

{% info title="Deprecation notice" %}
Dev keys are going to be deprecated soon. We recommend planning your migration away from dev keys ahead of time.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's add a date

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

We can do that once we have the Init dates finalised.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think we can do it regardless of Init, even if removed from console, they will still work on the API side

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'll confirm with Matej on this, update it

@@ -0,0 +1,61 @@
<script lang="ts">
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I feel like this page could be a container for simply just APIs and we can drop the integration part. Maybe have some overview of the different APIs types Appwrite support and why we offer different types. We can still link to the different API types directly from the main navigation like we do now.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We can even use the existing /docs/apis path.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I had thought about that but right now the APIs section is structured to contain info on the different protocols.

This broadens the scope of the section. If that is alright, I can directly shift these there.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think we can, it really make sense the more I look at the content. We can have a sub category for protocols and around them all the common things like response models or events, links structure will also work really well this way.

href: '/docs/advanced/billing/pro'
},
{
label: 'Scale',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Scale was deprecated

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Oh yes, I'll fix this

Learn which plan best suits your organization and how to manage billing.

{% cards %}
{% cards_item href="/docs/advanced/billing/payments" title="Billing" %}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Having a billing page inside the billing section doesn't work well it is also nested under the title Plans we can break it or/and have some of its information on the overview

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

My mistake, I forgot this change. Will fix

href: '/docs/advanced/security/rate-limits'
},
{
label: 'API keys',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We will soon need to refactor this to explain project keys vs account keys vs org keys.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

That will happen as soon as the Projects API section is ready for release. I will coordinate with Atharva on this.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

cool

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants