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 2 commits 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 2026 product update blog post covering the Appwrite React library, Password Strength controls for Auth, self-serve BAA, and the Claude Code marketplace plugin. It includes the post's Markdoc content, five
Confidence Score: 4/5Safe to merge once the broken placeholder link and empty Community Recognitions section in the Markdoc are resolved; images and cache entries are correct. The Markdoc post still contains a broken URL-encoded placeholder link at line 96 and a completely empty "Community Recognitions" section — both would render as visible broken or blank content in the published blog post. These were flagged in earlier review rounds and remain unaddressed. src/routes/blog/post/june-product-update-react-library-password-strength-baa-and-more/+page.markdoc — the broken placeholder link and empty section near the end of the file need to be removed or replaced before publishing. Important Files Changed
Reviews (2): Last reviewed commit: "Apply suggestion from @greptile-apps[bot..." | Re-trigger Greptile |
| * [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.
Broken placeholder link and empty section
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.
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>


June product update