Re-add db ai suggestions blog + changelog

[adityaoberai]

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
  • Published announcement of Database AI suggestions feature for intelligent schema generation.
  • Feature provides AI-powered column and index suggestions based on table context.
  • Users can review, modify, or skip suggestions before applying to their database schema.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request adds two new content files announcing Database AI suggestions for Appwrite Databases. The first file is a blog post page located at src/routes/blog/post/announcing-database-ai-suggestions/+page.markdoc with metadata and comprehensive content describing the AI-powered schema generation feature, including user workflows, UI elements, benefits, and resource links. The second file is a changelog entry at src/routes/changelog/(entries)/2025-10-01-2.markdoc documenting the same feature announcement with front matter and feature overview content. Both files use Markdoc format and follow existing content patterns.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Both additions are pure content files (Markdoc) with no code logic
• Changes follow established patterns in the repository
• Review focus should be on content accuracy and consistency:
  • Verify feature descriptions align between blog post and changelog entry
  • Confirm all hyperlinks and resource references are valid
  • Check front matter metadata (dates, authors, categories) are correctly formatted
  • Ensure cover image paths resolve correctly

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Re-add db ai suggestions blog + changelog' directly and accurately summarizes the main changes: re-adding a blog post and changelog entry about database AI suggestions.
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 ai-suggestions-blog

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

src/routes/blog/post/announcing-database-ai-suggestions/+page.markdoc (1)

12-55: Minor copy/style nits and resource alignment (optional)

Nothing blocking here, but a few tweaks could tighten things up:

• The feature name appears both as “Database AI suggestions” and “Database AI Suggestions” — consider standardizing capitalization across the post and with the changelog.
• “Alongside Database AI Suggestions, we have also added…” could be simplified to “we’ve also added” or similar, but that’s purely stylistic.
• The More resources section is MCP‑heavy; if you have docs or guides specifically about Database AI suggestions or database schema design, it might be worth swapping or adding one of those for more direct follow‑up.

These are all editorial, so feel free to ignore if they don’t match your content guidelines.

src/routes/changelog/(entries)/2025-10-01-2.markdoc (1)

17-23: Align "Benefits" heading with "What's new" for consistency within this entry

In this file, ## What's new (line 11) uses no colon, while ## Benefits: (line 17) includes one. For visual consistency within the same entry, consider removing the trailing colon:

-## Benefits:
+## Benefits

This aligns with the style in other recent changelog entries like 2025-09-17.markdoc.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 622ec0c and a523517.

⛔ Files ignored due to path filters (1)

• static/images/blog/announcing-database-ai-suggestions/cover.png is excluded by !**/*.png

📒 Files selected for processing (2)

• src/routes/blog/post/announcing-database-ai-suggestions/+page.markdoc (1 hunks)
• src/routes/changelog/(entries)/2025-10-01-2.markdoc (1 hunks)

⏰ 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: assets
• GitHub Check: tests
• GitHub Check: build

🔇 Additional comments (2)

src/routes/changelog/(entries)/2025-10-01-2.markdoc (1)

1-28: Changelog entry structure and linking look solid

Front matter matches the blog (title, date, cover), the “What’s new” and “Benefits” sections mirror the feature description well, and the arrow_link path /blog/post/announcing-database-ai-suggestions correctly matches the blog slug added in this PR. This should slot cleanly into the existing changelog flow.

src/routes/blog/post/announcing-database-ai-suggestions/+page.markdoc (1)

1-11: No action required—front-matter key is correct and consistent.

The verification confirms that timeToRead is the standard key used across all blog posts in the codebase. The new post follows the established pattern without deviation, so there is no risk of breaking listing pages or reading-time badges.

[ItzNotABug]

needs to be changed.

[ItzNotABug]

not sure if modal and side-sheet are something to mention, pretty standard across console.

[ItzNotABug]

might need changes since the designs have changed.

[ItzNotABug]

same here.