Blog eldad highlight

[LauraDuRy]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Documentation
  • Updated metadata for blog posts to reflect current content organization.

[coderabbitai]

Walkthrough

The pull request modifies blog post metadata in two Markdoc files. The first file changes its featured flag from true to false, while the second file adds a new featured: true flag to its frontmatter. These are purely metadata updates with no impact on content, rendering logic, or control flow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Metadata-only changes to frontmatter in static Markdoc files
• No logic, rendering, or structural modifications
• Consistent and simple pattern across both files
• Straightforward verification of flag values

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Blog eldad highlight' is vague and lacks specificity about what changes are being made; it doesn't clearly convey the primary modification (toggling featured flags on blog posts).	Clarify the title to specifically describe the changes, such as 'Update featured flags for blog posts: disable Appwrite Databases UI post, enable Developers Cloud post' or similar.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch blog-eldad-highlight

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c4b8169 and d539b7a.

📒 Files selected for processing (2)

• src/routes/blog/post/announcing-appwrite-databases-new-ui/+page.markdoc (1 hunks)
• src/routes/blog/post/the-developers-cloud/+page.markdoc (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📚 Learning: 2025-09-05T19:35:04.162Z

Learnt from: ebenezerdon
Repo: appwrite/website PR: 2372
File: src/routes/docs/tutorials/nuxt/step-6/+page.markdoc:79-83
Timestamp: 2025-09-05T19:35:04.162Z
Learning: In Nuxt tutorial files, the correct Appwrite database instance to use is `tablesDB` (imported from "~/appwrite"), not `database`. All tablesDB method calls should use the object parameter format: listRows({ databaseId, tableId, queries }), createRow({ databaseId, tableId, rowId, data }), and deleteRow({ databaseId, tableId, rowId }).

Applied to files:

• src/routes/blog/post/announcing-appwrite-databases-new-ui/+page.markdoc

📚 Learning: 2025-09-05T19:35:53.943Z

Learnt from: ebenezerdon
Repo: appwrite/website PR: 2372
File: src/routes/docs/tutorials/react/step-6/+page.markdoc:70-75
Timestamp: 2025-09-05T19:35:53.943Z
Learning: In React tutorial files, the correct Appwrite database instance to import is `tablesDB` from "../appwrite", not `databases`. The import statement should be `import { tablesDB } from "../appwrite"` to match the usage throughout the React tutorial code.

Applied to files:

• src/routes/blog/post/announcing-appwrite-databases-new-ui/+page.markdoc

📚 Learning: 2025-09-05T19:35:59.449Z

Learnt from: ebenezerdon
Repo: appwrite/website PR: 2372
File: src/routes/docs/tutorials/react-native/step-6/+page.markdoc:67-73
Timestamp: 2025-09-05T19:35:59.449Z
Learning: In React Native tutorials, the lib/appwrite.js file exports `tablesDB` (not `databases`), so imports should use `import { tablesDB } from "../lib/appwrite"` to match the export pattern established in step-3.

Applied to files:

• src/routes/blog/post/announcing-appwrite-databases-new-ui/+page.markdoc

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build
• GitHub Check: assets
• GitHub Check: tests

🔇 Additional comments (2)

src/routes/blog/post/the-developers-cloud/+page.markdoc (1)

10-10: LGTM!

The addition of featured: true correctly highlights this new blog post by Eldad Fux, aligning with the PR objective.

src/routes/blog/post/announcing-appwrite-databases-new-ui/+page.markdoc (1)

10-10: Metadata change is correct and properly integrated.

The featured flag is properly consumed in the blog rendering logic. The blog page retrieves the first post with featured: true via posts.find((post) => post.featured) and displays it prominently. Changing this post's flag from true to false removes it from the featured section, allowing another post to become featured instead. This aligns with the PR's goal of highlighting a newer post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}