On your point with the steep learning curve: Yes, Rails has a steep learning curve if you want to master the framework and build applications with it. But you should not have any problems if you want to contribute to parts of the docs. Maybe knowing meta programming would be an advantage if you want to dig into the code. Rails is pretty heavy on this.
However if Rails itself is too overwhelming, you can also start with other gems. Here are a few examples:
As you can see plenty of stuff to do in terms of docs here.
I think somebody with your qualifications would be a great win for the community and the docs.
Started out teaching English at Embry-Riddle.
Graded 10,000 essays.
Lesson learned.
Became a mathematics teacher.
Discovered computing.
Never looked back.
Location
Houston TX
Education
Stetson University: B.A., M.A. in English; M.S. in mathematics
Rails itself even has a section for docs in its contribution guide. You can contribute to the Rails Guides or to the Rails API if you want to get into code. Rails has currently 46 open issues open labelled with docs. So plenty of stuff to get into.
On your point with the steep learning curve: Yes, Rails has a steep learning curve if you want to master the framework and build applications with it. But you should not have any problems if you want to contribute to parts of the docs. Maybe knowing meta programming would be an advantage if you want to dig into the code. Rails is pretty heavy on this.
However if Rails itself is too overwhelming, you can also start with other gems. Here are a few examples:
As you can see plenty of stuff to do in terms of docs here.
I think somebody with your qualifications would be a great win for the community and the docs.
Thanks, Tobias. I will study these.