Skip to content

June product update: React library, Password strength, BAA and more#3080

Open
aishwaripahwa12 wants to merge 2 commits into
mainfrom
june-product-update-react-password-baa-more
Open

June product update: React library, Password strength, BAA and more#3080
aishwaripahwa12 wants to merge 2 commits into
mainfrom
june-product-update-react-password-baa-more

Conversation

@aishwaripahwa12

Copy link
Copy Markdown
Contributor

June product update

@appwrite

appwrite Bot commented Jul 3, 2026

Copy link
Copy Markdown

Appwrite Website

Project ID: 69d7efb00023389e8d27

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

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

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


Tip

Ephemeral API keys are generated automatically for each function execution

@greptile-apps

greptile-apps Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This 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 .avif image assets, and corresponding .optimize-cache.json entries.

  • The Markdoc post content covers four shipping announcements with text, images, and links to individual announcement posts, plus an engineering resources section.
  • The .optimize-cache.json entries use .png/.jpg key extensions for the .avif files, which is the established project convention and not an error.
  • A broken placeholder link ([community.avif](June%20product%20update%20React%20library,%20Password%20streng/community.avif)) and an empty "Community Recognitions" section remain in the post and were flagged in earlier review rounds but have not yet been removed or resolved.

Confidence Score: 4/5

Safe 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

Filename Overview
src/routes/blog/post/june-product-update-react-library-password-strength-baa-and-more/+page.markdoc New June product update blog post; contains a broken placeholder link at line 96 and an empty "Community Recognitions" section that would render broken/incomplete content when published
.optimize-cache.json Adds cache entries for all five new blog post images; all committed assets have a corresponding entry, extension differences (.png/.jpg vs .avif) are intentional per project convention
static/images/blog/june-product-update-react-library-password-strength-baa-and-more/cover.avif New cover image asset for the blog post, committed as .avif

Reviews (2): Last reviewed commit: "Apply suggestion from @greptile-apps[bot..." | Re-trigger Greptile

Comment on lines +96 to +98
* [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)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P1 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>
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