June product update: React library, Password strength, BAA and more#3080
June product update: React library, Password strength, BAA and more#3080aishwaripahwa12 wants to merge 1 commit into
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Ephemeral API keys are generated automatically for each function execution |
Greptile SummaryThis PR adds the June product update blog post covering the Appwrite React library, Password strength controls, self-serve BAA, and the Claude Code marketplace plugin, along with the associated cover and section images.
Confidence Score: 3/5The post has incomplete placeholder content that would publish visibly broken to readers. The broken community.avif link and the empty Community Recognitions section are leftover export artifacts that will appear verbatim in the rendered blog post, producing a visible broken link and an empty heading for all readers. These need to be removed or completed before the post goes live. The markdoc file needs attention around lines 96–98 where the placeholder link and empty section live. Important Files Changed
Reviews (1): Last reviewed commit: "june product update" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| * [What is CI/CD? A complete guide for developers](https://appwrite.io/blog/post/what-is-cicd-a-complete-guide-for-developers) | ||
| * [Appwrite Arena: June 2026 update](https://appwrite.io/blog/post/arena-june-2026-update) | ||
| * [Best AI productivity stack for developers in 2026](https://appwrite.io/blog/post/best-ai-productivity-stack-for-developers-in-2026) |
There was a problem hiding this comment.
Line 96 contains a broken link — [community.avif](June%20product%20update%20React%20library,%20Password%20streng/community.avif) — that looks like a leftover artifact from a Notion/Figma export. The path is URL-encoded, points to a file that was never committed, and will render as a visible broken link in the published blog post. The "Community Recognitions" section immediately below (line 98) is also completely empty. Both should either be completed with real content or removed before publishing.
|
|
||
| Let's dive in. | ||
|
|
||
|  |
There was a problem hiding this comment.
.jpg, .png) that appear to be copy-paste artifacts from the original filenames. Alt text should be a meaningful description of the image, not a filename.
|  | |
|  |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
|
||
| [Read more](https://appwrite.io/docs/tooling/ai/agents/claude-code) | ||
|
|
||
|  |
There was a problem hiding this comment.
|  | |
|  |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|  | ||
|
|
||
| # Introducing Password strength for Appwrite Auth | ||
|
|
||
| Appwrite Auth now lets you enforce Password strength on every project. | ||
|
|
||
| You can set a minimum password length and require any combination of an uppercase letter, lowercase letter, number, and special character. | ||
|
|
||
| These rules run at sign-up and whenever a user changes their password, so weak passwords are rejected before they land in your project. | ||
|
|
||
| Password strength works alongside existing Appwrite Auth protections like password history and the password dictionary, giving teams more control without custom password validation logic. | ||
|
|
||
| [Read the announcement](https://appwrite.io/blog/post/announcing-password-strength) | ||
|
|
||
|  |
There was a problem hiding this comment.
|  | |
| # Introducing Password strength for Appwrite Auth | |
| Appwrite Auth now lets you enforce Password strength on every project. | |
| You can set a minimum password length and require any combination of an uppercase letter, lowercase letter, number, and special character. | |
| These rules run at sign-up and whenever a user changes their password, so weak passwords are rejected before they land in your project. | |
| Password strength works alongside existing Appwrite Auth protections like password history and the password dictionary, giving teams more control without custom password validation logic. | |
| [Read the announcement](https://appwrite.io/blog/post/announcing-password-strength) | |
|  | |
|  | |
| # Introducing Password strength for Appwrite Auth | |
| Appwrite Auth now lets you enforce Password strength on every project. | |
| You can set a minimum password length and require any combination of an uppercase letter, lowercase letter, number, and special character. | |
| These rules run at sign-up and whenever a user changes their password, so weak passwords are rejected before they land in your project. | |
| Password strength works alongside existing Appwrite Auth protections like password history and the password dictionary, giving teams more control without custom password validation logic. | |
| [Read the announcement](https://appwrite.io/blog/post/announcing-password-strength) | |
|  |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
June product update