Skip to content

docs: update legacy blog and discord links to official vanity URLs#11760

Open
Curbe6 wants to merge 4 commits intoappwrite:1.9.xfrom
Curbe6:patch-1
Open

docs: update legacy blog and discord links to official vanity URLs#11760
Curbe6 wants to merge 4 commits intoappwrite:1.9.xfrom
Curbe6:patch-1

Conversation

@Curbe6
Copy link
Copy Markdown

@Curbe6 Curbe6 commented Apr 2, 2026

Update legacy blog and Discord links

What does this PR do?

This PR updates outdated documentation links in the README. Specifically, it replaces the legacy Medium blog link with the official https://appwrite.io/blog and updates the Discord invite link to the official vanity URL https://appwrite.io/discord. This ensures a consistent brand experience and directs users to the most current community resources.

Test Plan

I manually verified that the updated URLs (https://appwrite.io/blog and https://appwrite.io/discord) are active and redirecting to the correct destinations. No code changes were made, only documentation.

Related PRs and Issues

  • Internal cleanup of legacy documentation links.

Checklist

  • Have you read the Contributing Guidelines on issues?
  • If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?

Switched Medium blog link to appwrite.io/blog and updated Discord invite to the official vanity URL for better consistency and branding.
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 2, 2026

Greptile Summary

This PR makes two changes to README.md: it removes the Appwrite Cloud public-beta disclaimer in the "Installation & Setup" section and replaces it with a generic managed-experience description, and it modifies the API-documentation paragraph in the "Products" section. The stated goal — replacing the legacy Medium blog URL and the old Discord invite with the official vanity URLs — has not been achieved; the entire community-resources sentence was deleted rather than updated, leaving readers with no path to the blog or Discord from that section of the README.

  • The Installation & Setup beta messaging was removed and replaced with neutral copy — a reasonable update if Appwrite Cloud is now GA.
  • The sentence referencing the blog (https://medium.com/appwrite-io) and Discord (https://discord.gg/GSeTUeA) was deleted rather than updated to https://appwrite.io/blog and https://appwrite.io/discord as described in the PR.

Confidence Score: 3/5

  • Not safe to merge — the PR's stated goal is unmet and community-resource links have been removed rather than updated.
  • The PR deletes the community-resources sentence instead of replacing the legacy URLs with the official vanity URLs. This means users lose access to the blog and Discord links from the README entirely, which is worse than the original state. The beta-messaging removal on line 63 is a reasonable standalone change, but it doesn't offset the missing link updates that are the entire purpose of this PR.
  • README.md — line 186 needs the blog and Discord links restored and updated to the official vanity URLs.

Important Files Changed

Filename Overview
README.md Two changes: (1) Installation & Setup beta messaging replaced with a generic managed-experience description; (2) the blog and Discord link sentence was deleted entirely rather than updated to the official vanity URLs as stated in the PR description.

Reviews (4): Last reviewed commit: "Revise installation setup and remove dou..." | Re-trigger Greptile

Comment thread README.md Outdated
Comment thread README.md Outdated
Curbe6 added 2 commits April 2, 2026 09:48
Updated installation instructions and added links to official resources.
Updated Discord link to official vanity URL and corrected punctuation.
Comment thread README.md Outdated
Updated installation instructions and removed double self-hosting section information.
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.

1 participant