Getting Started With Typo

Why do Rails developers like me blog on WordPress, which is written in PHP, instead of Typo, which is written in Ruby on Rails?

The answer is simple, really, maybe even obvious: WordPress works better. WordPress has been in development longer, and it has more of everything, more plugins, more polish, more templates. As of today, for example, WordPress has some 20,244 plugins, while Typo has about 25.

It’s a bit of a landslide, really.

The reason I wanted to take a look at Typo is that it fits in with my professional development goals, which are:

  • To work on some passive income Rails projects to improve my skills.
  • To work on some open source projects to further develop my skills and give something back.
  • To share my experiences here.
  • Finally, as the inevitable result, to land some paid Rails work.

Sure, being early in development, Typo’s not right (yet) for the casual blogger. But at the same time, it’s an ideal project on which a Rails developer can hope to make important contributions.

So…

Getting Typo Up and Running

The Typo blog tells us that we’re supposed to start with something more or less like this:

Trying out the first line, we get a clue as to the sort of development fun we can have with this product:

We’re greeted with the following in nice red letters:

After you get that message, the gem that’s no longer available will be installed.

That’s OK, let’s not let it deter us from doing the right thing according to the warning. Getting the stable release specified in the link and unzipping it, let’s visit the documentation as suggested.

I’ve just worked with the doc and updated the wiki page fix some inaccuracies and omissions, so hopefully it’s current (as of today at least). So you should be able to work your way through that to the point where you’re ready to run “rails server” without trouble.

I was able to get it running, and was able to run edge server pretty easily too. Just get the latest:

Run the instructions above and you should be good to go!