Consolidate ruby version manager info in single source of truth
Why is this change being made?
Closes: https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/1288
The scope of this MR is only to consolidate Ruby version manager information in a single source of truth.
This does not answer the question of whether we should have an opinionated setup. I also think docs/development.md needs to be cleaned up a little more, but that is also out of scope.
I updated the how to edit this website locally handbook page with top-level installation instructions for asdf, rbenv, and rvm. The instructions mostly link out to each tool's documentation, to keep our docs from getting out of sync. I'm open to adding more details if we think that's warranted for a broader audience - but I would suggest we take that to a separate issue. I mostly wanted to get this information in one single place.
I updated the docs/development.md file to point to that handbook page, and did the same with the README.
Since this impacts a broad set of teams and people, I am requesting reviews from a few folks:
- @laurenbarker to represent the digital experience team
-
@cwoolley-gitlab to represent the handbook (and to let me know if I missed any steps for
asdf, haha) - @pcalder to represent the folks making release posts. I didn't change your handbook page at all, but it points to this page and I want to confirm the updated content is still useful.
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI