First step toward more ShortRuby

Welcoming rubyandrails.info to ShortRuby

I am excited to announce that rubyandrails.info is now part of ShortRuby.

Leonid was kind enough to transfer my ownership of rubyandrails.info in exchange for only supporting the expenses he has made for the website so far. So I think I put some part the money that I received so far from people that decided to upgrade to paid to good use.

The reason why I wanted to get that website is that I anyhow was thinking of building somewhere a collection of resources that I encountered every time I do a new edition of the newsletter: books, courses, videos, newsletters, and, more important the people that are sharing all those fantastic stuff.

Vision and some plans

Please take the following ideas more as a current draft. I am open to ideas and will refine how rubyandrails.info fit into Short Ruby.

  1. For the next period, rubyandrails.info will remain as it is. I will probably refactor the code (now open source here) while thinking about how to integrate it with the newsletter automatically.

  2. Medium-term, I want to integrate rubyandrails.info to ShortRuby. There are two options that I think now about this:

    1. Transform the rubyandrails.info → shortruby.com - currently, shortruby.com redirects to newsletter.shortruby.com, but I am thinking more and more that ShortRuby should be more of a central place to find out resources and news about the Ruby community. Thus it can include more than a newsletter.

    2. Move rubyandrails.info to resources.shortruby.com or community.shortruby.com (the name is yet to be decided)

  3. Medium-term: integrate the rubyandrails.info (or the new place where it might be) into the newsletter. Thus every time I publish a new edition of the newsletter, all new resources discovered should be organized in the rubyandrails.info

  4. Long(ish)-term: I plan to transform the newsletter's content into an organized, tagged, and searchable archive. Maybe what is now at rubyandrails.info/learn could be a good starting point.

I see Short Ruby as a place where someone new to Ruby might come and discover how they can immerse themselves more into Ruby's world.

Timeline

I am not sure how long this vision might take. I also cannot promise that what I wrote here is what I will implement for sure.

What I can say is that I am grateful for all of you that decided to read the newsletter and for all of you that decided to put money via subscriptions in the newsletter, thus enabling me to think that ShortRuby can be more than just the newsletter.

Still, I want to make small steps while keeping the weekly newsletter publication as the primary goal.

If you have any feedback or ideas about what I shared here, please write to me at [email protected] or in the comments here.

 

Reply

or to participate.