Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Improve README structure and clarity for new contributors#3629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
robbyrussell wants to merge1 commit intoruby:master
base:master
Choose a base branch
Loading
fromrobbyrussell:readme-refresh

Conversation

@robbyrussell
Copy link
Contributor

Summary

While making my own contributions to this project, I found myself jumping around the README to confirm setup details and contribution steps. This PR reorganizes the content to create a clearer flow for anyone wanting to pull down the repo and run it locally.

Key Changes

  • Streamlined Quick Start: Clear prerequisites and numbered setup steps
  • Organized contribution workflow: Step-by-step process with testing requirements upfront
  • Better structure: Logical sections that flow from setup → contributing → advanced topics
  • Removed duplicates: Eliminated repeated sections for cleaner reading
  • Added emojis: Visual headers for easier scanning

Goals

Make it easier for developers to:

  • Get the site running locally on first try
  • Understand the contribution process clearly
  • Know testing expectations before submitting PRs

Thanks for maintaining such a welcoming project! Hope this helps more people contribute to Ruby's website. 🎉

Note: No functional changes - purely documentation improvements.

- Add quick start guide with clear prerequisites and setup steps- Reorganize content with better structure and visual hierarchy- Emphasize testing requirements before PR submission- Move advanced Heroku deployment section to end- Clarify language guidelines for global developer audience- Remove duplicate sections and improve flow
@robbyrussellrobbyrussell requested a review froma team as acode ownerSeptember 27, 2025 00:54
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@robbyrussell

[8]ページ先頭

©2009-2025 Movatter.jp