Update 2025-07-30-dev-update-july-2025.md

[Jordy-Baby]

Summary by CodeRabbit

• Style
  • Standardized image paths in the July 2025 dev update blog post by removing unnecessary prefixes and redundant separator lines.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
envio-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 31, 2025 8:32am

[coderabbitai]

Walkthrough

This update standardizes image references in a single blog post by removing the "/blog-assets/" prefix from all image source paths and deletes redundant separator lines. No other content, links, or structure are changed.

Changes

Cohort / File(s)	Change Summary
Blog Image Path and Formatting Update blog/2025-07-30-dev-update-july-2025.md	Removed redundant separator lines and simplified all image source paths by eliminating the "/blog-assets/" prefix.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a skip, the blog is now neat,
Image paths trimmed for a streamlined feat.
No more slashes, no more lines,
Just tidy markdown—how it shines!
With every nibble, clarity grows,
The rabbit approves—onward it goes! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Jordy-Baby-patch-9

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

blog/2025-07-30-dev-update-july-2025.md (2)

7-7: Consider adding loading="lazy" for faster first paint

All inline <img> tags are above-the-fold heavyweight assets. Adding the native loading="lazy" attribute defers off-screen image loading and improves CLS/LCP metrics:

-<img src="./base-support.png" alt="base support" width="100%"/>
+<img src="./base-support.png" alt="base support" width="100%" loading="lazy"/>

A tiny change, but it benefits both Lighthouse scores and real-user experience.

Also applies to: 65-65, 79-79, 90-90, 100-100, 110-110, 131-131, 149-149

---

164-164: Social-links line is inaccessible & difficult to translate

A single pipe-separated paragraph hampers screen-reader navigation and localisation.
Switch to a semantic list for better a11y and maintainability:

-[Website](https://envio.dev/) | [X](https://twitter.com/envio_indexer) | [Discord](https://discord.com/invite/gt7yEUZKeB) | [Telegram](https://t.me/+5mI61oZibEM5OGQ8) | [GitHub](https://github.com/enviodev) | [YouTube](https://www.youtube.com/channel/UCR7nZ2yzEtc5SZNM0dhrkhA) | [Reddit](https://www.reddit.com/user/Envio_indexer)
+
+**Find us:**  
+- [Website](https://envio.dev/)  
+- [X](https://twitter.com/envio_indexer)  
+- [Discord](https://discord.com/invite/gt7yEUZKeB)  
+- [Telegram](https://t.me/+5mI61oZibEM5OGQ8)  
+- [GitHub](https://github.com/enviodev)  
+- [YouTube](https://www.youtube.com/channel/UCR7nZ2yzEtc5SZNM0dhrkhA)  
+- [Reddit](https://www.reddit.com/user/Envio_indexer)

This keeps the visual layout almost identical while making the section far more accessible.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0187bfd and 56ea704.

📒 Files selected for processing (1)

• blog/2025-07-30-dev-update-july-2025.md (1 hunks)

🔇 Additional comments (1)

blog/2025-07-30-dev-update-july-2025.md (1)

7-7: No changes needed—baseUrl is “/”
Verified in docusaurus.config.js (line 238) that baseUrl: "/". All eight <img src="/…"> paths will resolve correctly at the site root.