Skip to content

docs: update README.md for clearer developer onboarding#39439

Open
Rohit544 wants to merge 1 commit intoRocketChat:developfrom
Rohit544:docs/update-readme
Open

docs: update README.md for clearer developer onboarding#39439
Rohit544 wants to merge 1 commit intoRocketChat:developfrom
Rohit544:docs/update-readme

Conversation

@Rohit544
Copy link

@Rohit544 Rohit544 commented Mar 7, 2026

Proposed changes

Describe the big picture of your changes here.

  • Improved setup instructions for local development.
  • Fixed minor formatting issues in the README.

Motivation and Context

As a software engineer setting up the project, I noticed some areas in the README that could be clarified to improve the Developer Experience (DX) for new contributors.

Type of change

  • Documentation update (non-breaking change which fixes an issue)

Checklist

  • I have signed the CLA (Contributor License Agreement)
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas

Summary by CodeRabbit

  • Documentation
    • Enhanced README accessibility by adding descriptive alt text for all images.
    • Reorganized README structure and formatting, including updated headings and separators for improved clarity.

…idance

- Added project badges (version, build, license, coverage)
- Included Node.js v22.16.0+ and Deno requirements
- Added a 'Beginner contributions' section with tips for newcomers
- Improved accessibility with alt text for all images
- Reformatted sections for better readability and organization
@dionisio-bot
Copy link
Contributor

dionisio-bot bot commented Mar 7, 2026

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is missing the 'stat: QA assured' label
  • This PR is missing the required milestone or project

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

@changeset-bot
Copy link

changeset-bot bot commented Mar 7, 2026

⚠️ No Changeset found

Latest commit: 0d2d2d7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


rohitoo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 7, 2026

Walkthrough

README.md accessibility and structure improvements including addition of alt attributes to image tags, reorganization of headings and separators, reflowing of content sections, and minor markup refinements without altering core content semantics.

Changes

Cohort / File(s) Summary
Documentation and Accessibility Updates
README.md
Added alt attributes to image tags for accessibility, reorganized headings and separators, reflowed platform overview and contributor sections for conciseness, and refined surrounding markup for improved structure.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested labels

type: chore

🚥 Pre-merge checks | ✅ 3
✅ 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 'docs: update README.md for clearer developer onboarding' clearly and specifically describes the main change—a README documentation update aimed at improving developer onboarding. It is concise, directly related to the changeset, and aligns with the core objectives of improving clarity and developer experience.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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

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

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files


Since this is your first cubic review, here's how it works:

  • cubic automatically reviews your code and comments on bugs and improvements
  • Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
  • Add one-off context when rerunning by tagging @cubic-dev-ai with guidance or docs links (including llms.txt)
  • Ask questions if you need clarification on any suggestion

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 10-13: Replace the incorrect workflow badge URL in the README's
build badge image tag: find the img element whose src contains
"build_and_test.yml" and update that segment to "ci.yml" so the src becomes
".../github/actions/workflow/status/RocketChat/Rocket.Chat/ci.yml"; keep the
rest of the badge attributes (alt text and other badges) unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f0e9eb8a-8980-49d1-8371-b9b9d42fc9bc

📥 Commits

Reviewing files that changed from the base of the PR and between 4f43a85 and 0d2d2d7.

📒 Files selected for processing (2)
  • README.md
  • docker-compose.yml
📜 Review details
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ahmed-n-abdeltwab
Repo: RocketChat/Rocket.Chat PR: 38974
File: apps/meteor/app/api/server/v1/im.ts:220-221
Timestamp: 2026-02-24T19:09:09.561Z
Learning: In RocketChat/Rocket.Chat OpenAPI migration PRs for apps/meteor/app/api/server/v1 endpoints, maintainers prefer to avoid any logic changes; style-only cleanups (like removing inline comments) may be deferred to follow-ups to keep scope tight.
Learnt from: MartinSchoeler
Repo: RocketChat/Rocket.Chat PR: 37408
File: apps/meteor/client/views/admin/ABAC/useRoomAttributeOptions.tsx:53-69
Timestamp: 2025-11-10T19:06:20.146Z
Learning: In the Rocket.Chat repository, do not provide suggestions or recommendations about code sections marked with TODO comments. The maintainers have already identified these as future work and external reviewers lack the full context about implementation plans and timing.
Learnt from: ggazzo
Repo: RocketChat/Rocket.Chat PR: 35995
File: apps/meteor/app/api/server/v1/rooms.ts:1107-1112
Timestamp: 2026-02-23T17:53:18.785Z
Learning: In Rocket.Chat PR reviews, maintain strict scope boundaries—when a PR is focused on a specific endpoint (e.g., rooms.favorite), avoid reviewing or suggesting changes to other endpoints that were incidentally refactored (e.g., rooms.invite) unless explicitly requested by maintainers.
📚 Learning: 2025-11-10T19:06:20.146Z
Learnt from: MartinSchoeler
Repo: RocketChat/Rocket.Chat PR: 37408
File: apps/meteor/client/views/admin/ABAC/useRoomAttributeOptions.tsx:53-69
Timestamp: 2025-11-10T19:06:20.146Z
Learning: In the Rocket.Chat repository, do not provide suggestions or recommendations about code sections marked with TODO comments. The maintainers have already identified these as future work and external reviewers lack the full context about implementation plans and timing.

Applied to files:

  • README.md
🔇 Additional comments (6)
README.md (6)

2-2: Excellent accessibility improvement!

Adding descriptive alt text to the logo image improves accessibility for screen reader users.


22-33: Well-structured platform overview section.

The addition of the emoji heading, introductory text, reformatted feature list, and hero image with proper alt text significantly improves readability and accessibility.


47-56: Excellent addition for new contributors!

This "Beginner Contributions" section directly addresses the PR objective of improving developer onboarding. The specific, actionable suggestions (fix typos, update setup instructions, improve guides) combined with the link to "good first issue" labels provide a clear pathway for newcomers to get started.


60-114: Consistent formatting improvements throughout.

The addition of horizontal rules, emoji-enhanced headings, and improved section organization significantly enhances document readability and scannability. The explicit mention of support channels (line 103) is particularly helpful for new users seeking assistance.


42-42: No action needed—Deno is actually required.

Deno is legitimately used in the packages/apps-engine/deno-runtime component, which provides a Deno-based runtime for executing Rocket.Chat Apps. The codebase includes a deno.jsonc configuration, multiple modules importing from https://deno.land/ (Deno standard library), and application code using Deno APIs (Deno.args, Deno.stdin, Deno.pid, etc.). The README requirement for "Latest stable version" is correct.

			> Likely an incorrect or invalid review comment.

41-41: The README accurately reflects the package.json configuration, which specifies Node.js 22.16.0. While this is not the current LTS version (v24.14.0 is as of March 2026), the README correctly documents the actual requirement. No changes needed.

Comment on lines +10 to +13
<img src="https://img.shields.io/github/v/release/RocketChat/Rocket.Chat?label=version" alt="GitHub release version">
<img src="https://img.shields.io/github/actions/workflow/status/RocketChat/Rocket.Chat/build_and_test.yml" alt="Build Status">
<img src="https://img.shields.io/badge/license-MIT-green" alt="MIT License">
<img src="https://img.shields.io/codecov/c/github/RocketChat/Rocket.Chat/develop" alt="Code Coverage">
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify the build_and_test.yml workflow file exists

fd -t f "build_and_test.yml" .github/workflows/

Repository: RocketChat/Rocket.Chat

Length of output: 48


🏁 Script executed:

fd -t f . .github/workflows/

Repository: RocketChat/Rocket.Chat

Length of output: 692


🏁 Script executed:

head -20 .github/workflows/ci.yml

Repository: RocketChat/Rocket.Chat

Length of output: 383


Correct the build workflow badge URL — it references a non-existent workflow.

The badge currently points to build_and_test.yml, which doesn't exist in .github/workflows/. The main CI workflow is ci.yml. Update the badge URL to:

https://img.shields.io/github/actions/workflow/status/RocketChat/Rocket.Chat/ci.yml

The other badges (version, license, coverage) appear correct. The alt text is also appropriate across all badges.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 10 - 13, Replace the incorrect workflow badge URL in
the README's build badge image tag: find the img element whose src contains
"build_and_test.yml" and update that segment to "ci.yml" so the src becomes
".../github/actions/workflow/status/RocketChat/Rocket.Chat/ci.yml"; keep the
rest of the badge attributes (alt text and other badges) unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants