Good bye Typo, welcome Publify!

It’s been scratching us for a while now, and we finally did it: Typo is no more, long live Publify! There are many reasons why we changed your favorite blogware name, leaving behind us a 7 years old brand and not always glorious history.

Typo is a stupid name for a publishing tool

Typo took its name from a Typo Tobias made into his agenda, giving him a few hours to start coding the blogware that once powered Rails official blog, but let’s be honest, it’s a stupid name for a blogging engine, a really stupid one.

Making typos is not something you would expect when writing quality content, and we indeed expect our users to produce quality content. Typos make content look dumb and their producer look careless if not illiterate.

On the other hand, even though Publify may not be the best, most original name, it means what it should mean: something meant to publish, which is not so bad after all.

Typo is unsearchable

Open your favorite search engine, and look for typo. My bet is you won’t find many things related to Typo. If you’re lucky, our main site will come on first page, but I’m not even sure it will happen.

Google brings 65,300,000 results for Typo, most of them being related to typography, Publify has only 3460 entries. I’m sure you see the point, but finding resources for Publify will become easier as time goes.

There’s already a Typo3 publishing tool

There was a CMS called Typo3 long before Typo appeared. Typo3 is an enterprise CMS developed in PHP, and many people would make the confusion. Typo3 has been around for more than 10 years, and we did not mean to overlap on that name. It actually caused more problems that it solved, because many people were asking us about Typo3.

What about my content / theme / plugins ?

The old typo:code macros won’t work anymore. They’ve been replaced by the same publify:code macros. We’re providing a migration that makes your content work with publify:code.

Your old themes should still be working. If not, just replace all occurrences of TypoPlugins by PublifyPlugins, and all occurrences of Typo by Publify.

Your homemade plugins probably won’t work, because the TypoPlugins class they inherit from doesn’t exist anymore. To fix them, replacing TypoPlugins by PublifyPlugins in your code should do the trick. Don’t forget to restart your Publify blog after doing the changes.

That said, we’re now going to go back to work to release the first Publify version during the summer. Have a nice, sunny blogging.

Published on 10/07/2013 at 14h05 by Frédéric de Villamil, tags

Rails 3 Typo is coming soon

I’m thrilled to tell you that, since tonight September the 26th 22:22 GMT, Typo official blog and my own blog are now running our Rails 3 development branch. This was made possible by Matijs great work – and a bit of mine as well.

The past weeks were quite exciting, and I really had great fun working on this branch, making specs pass one at a time, getting excited because Matijs had pushed something new, and I had to push more as well, fixing this and that in the train on my way to work.

Typo is a very old application, almost as old as Rails is, and it has seen many major releases: 1.0, 1.2, 2.0 and now 3.0. Some code is very old as well, and Rails often took the opposite path as how we did things. Rails 3 is probably the biggest evolution I’ve seen since I started, and migrating Typo is a long and painful process. It was only made possible because we had a good – thus insufficient – test coverage.

What’s next?

In the next days, we’re going to polish the few remaining details. Typo installer needs to be changed to match Bundler evolution. Oh, and we also want to add some feature we had in mind for a while. So stay tuned.

Published on 26/09/2010 at 20h22 by Frédéric de Villamil, tags

Admin plugins integration

Commit 281e6dc6941c0987b75a8777df30b84928f44d6d (as well as 132697c2184a4a89fd3ca16d327bbe47a9644d09) introduced the possibility to dynamically load access to plugins admin section into Typo administration. Links to plugins admin zone are displayed into the admin/themes zone. This is – for now – fairly limited, but we’re working on extending it.

This is important to us since Typo has always been missing a nice plugin API. This is a first step towards something bigger, even thoug we don’t know how big it’s going to be yet.

I’ve released a quick proof of concept using a contact form plugin. It’s really simple, lacks lots of functionnalities one could expect from such a plugin but… it’s a POC and I’ll update it later. To test it, you need to be following our development branch, and update to the latest commit.

Typo plugins admin interface

First, install Typo Contact Form plugin on your Typo instance:

<typo:code lang=’sh’> ./script/plugins install </typo:code>

Then restart your Typo application.

You can now access the contact form using: http://your blog url/contactform Administration: http://your blog url]/admin/contactform

How can I integrate my plugins into Typo administration?

It’s fairly easy.

Typo plugins are just plain Rails plugins.

To have their admin detected, they need to be called typopluginsomename. They should just include a lib/app/controllers/admin/somename_controller.rb

I recommend you to start with Typo Contact Form code, to make your own plugins Typo compliant.

More to come very soon!

Published on 20/04/2010 at 23h43 by Frédéric de Villamil, tags , , ,

Typogarden is back from the grave

After a few months being slightly brocken, Typogarden, Typo’s theme catalogue is now back from the grave, better, and more up to date.

I incidentally broke Typogarden while upgrading the Typo that was hosting it, and forgot to backup things before doing it. I had to change a few things in the new default theme and in every theme picture to make things right. You can now submit new themes at neuro[at], and I’ll add them as soon as possible.

Published on 14/03/2010 at 17h55 by Frédéric de Villamil, tags

Release of Typo 5.4 Willy Ronis

After 9 months of hard work, we’re proud to announce the official release of Typo 5.4 Willy Ronis, the most advanced and user friendly blogging platform on Rails. Despite having a minor version number, Typo 5.4 is a major release, coming with a lot of new features and some bugfixes as Willy Ronis was a great photographer who died this year at the age of 99. Since Typo 5.4 fixes some major security issues, you should really think about upgrading.

Typo 5.4 is also a major release because we had many contributors from all over the world sending new features and fixes along this year. After contributing for a while, Matijs van Zuijlen ( finally joined the core team in late February and did a great job on this release. We would also like to thank, in alphabetical order: Diego Elio ‘Flameeyes’ Pettenò, Edward Middleton, Erik Ostrom, Hans de Graaff, Jakob Skov-Pedersen, Kurt Werle, Michael Reinsch, Mike Mondragon, Wei Jen Lu, Yuka Ouka, jzellman, and mpagalan.

Published on 19/12/2009 at 11h00 by Frédéric de Villamil, tags ,

Typo gets blue (dabadi dabada)

Next release will come with a brand new theme called True Blue. True Blue is a simplified port of the theme I'm using on my own blog. It's a nice, clean, 2 columns blue theme coming with Twitter native support.



Hélène's Typographic is a great theme, but we needed something more casual. To quote Matijs' own words, the default theme should be one that anyone could start off using, no matter what their blog was about (like the Kubrick theme half the Wordpress blogs use).

Since True Blue is using its own helpers, you may need to restart your Typo installation to have it work after enabling. We're working on fixing this.

Published on 18/10/2009 at 17h59 by Frédéric de Villamil, tags , , ,

Features frozen for Typo 5.3

Yesterday, Cyril and I have decided to freeze the long list of features of the soon to come Typo 5.3, pushing password protected posts and spam filter daily digest to a later release.

many bugs have been fixed lately, and, unless we discover remaining bugs, we consider the current version as usable in production, which means a first release candidate may come quickly. Stay tuned !

Published on 14/03/2009 at 12h14 by Frédéric de Villamil, tags , , ,

Typo gets dynamic permalink URL

If you’ve been following our commits on Github, you must now know that, despite being quite silent here, we’ve been working hard on your favourite Rails application. Typo 5.2.1 is on its way, and even though it’s now too late to submit requests for enhancement, you can still submit bugs, and we’ll try to fix them as much as possible. You can also ask for features and improvements, but they won’t be in our next release, unless you submit a patch with tests.

Cyril has recently been working on a separate branch, to develop Typo 5.2.1 main feature: dynamic permalink URLs for posts. This is a great improvement and a great work he can really be proud of. Permalink URL were almost hard coded in typo, forcing people to use the /date/month/year/permalink scheme. You can now define your permalinks in the SEO part of your Typo install, using some reserved keywords:

  • %year%: year.
  • %month%: month.
  • %day%: day.
  • %title%: post slug

This gives fancy things like :

  • /%year%/%month%/%day%/%title% is the default option, and will generate /date/month/year/permalink.
  • /foo/%year%/bar/%day%/joker/%month%/hiphop/%title% will generate /foo/year/bar/day/joker/month/hiphop/permalink. I know, this is totally useless, but it works.
  • /%title%.html will generate /permalink.html URL.
  • And so on…

Will this break something?

Absolutely, this will break your existing theme an horrible way if you’ve been using an heavily tweaked one. Check in your themes for the /views/ directory. If you find something there, it must be brocken. Otherwise, it may still work fine.

So, what do I need to change?

Not much actually.

  • In articles/commentbox.html.erb use @article.commenturl instead of commentspath(@article)

  • all link previewnewcommentpath(@article) are change to @article.previewcomment_url

  • all link urlfor formattedarticlepath(@article, :rss) are change to @article.feedurl(:rss)

  • all link formattedarticleurl(@article, @format) are change to @article.permalinkbyformat(@format)

That’s all folks, see you soon on #typo, we always enjoy newcommers and feedback.

Published on 19/02/2009 at 20h56 by Frédéric de Villamil, tags , ,

Typo goes GitHub

I’ve always been pretty hostile to Git and Mercurial like version control systems, and have a particular love to SVN. We’ve however decided today to switch Typo from Subversion to Git, and more precisely on Github. Sources have already migrated on a new repository, and we’re going to close the old one soon.

There are many reasons for this. Some of them are dead obvious, some other are less, but things are now done.

Why choosing Git?

Because Cyril Mougel, my co maintener has been harassing me for months and bribing me with fresh Guiness.

A large majority of Ruby on Rails projects have already migrated from Subversion to Git, following the framework itself. While Typo was sticking to Rails 2.0.2, this didn’t bother us at all. With trunk having switched to Rails 2.2, managing external resources has become impossible. We’re now using both Git submodules for Rails itself, and gem dependencies for other plugins. We’re trying to enlighten our codebase, which has recently been drastically reduced with a double sides axe.

I also wanted to split our officially supported plugins in separate repositories after moving them apart Typo itself. Each plugin now has its own depot, and it’s cleaner this way.

Why Github?

Mostly for marketing and visibility purpose. But also for its great usability and user friendlyness.

We’ll keep using Redmine at Typosphere. The codebase has been cloned locally and will be refreshed every hour to be displayed on the depot part of the site. This is still in progress but will be done very quickly.

Published on 23/10/2008 at 22h02 by Frédéric de Villamil, tags , , ,

Typogarden is now our new official themes repository

We’ve been working the whole week-end to set up the new Typogarden, and even thoug there are still much themes to port, we’re happy to announce our new official theme repository is now open.

Typogarden used to be Typo theme contest website. Unfortunately, the site became a forsaken land since mid 2006. We had the project to take over it and make it revive for long, but lacked both the domain name and the time to do it. And since a garden is notheing without a gardener, we’re happy to welcome Damien Mathieu, a French web developper and happy Typo user as Typogarden maintener. Welcome to the crew dude. I’m sure you’ll be the man.

There’s still a lot to do. First we need to finish importing themes from Proofread and dev411. Then, port some popular Wordpress themes to Typo to enlarge our collection, and wait for genuine theme submission.

Submit a theme to Typogarden?

Now that you have tested your theme, it looks great, and you’re a kind and giving person, so you want to share it with other typo users. Remember, typo thrives on the contributions of the many contributors all around the world. Please do become one of them.

While guaranteeing full employment for intellectual property lawyers may seem to be a laudable goal to some, please make sure that you have permission to use all the elements you submit with your theme before you send it in.

  • Make a “tar ball” or zip : Zip up your theme directory or make a tar ball with a command such as tar cjvf mytheme.tar.bz2 mytheme.
  • Share your well-tested theme: Create a new ticket with [THEME] as the first word in the summary and upload (not paste) your zip or tarball.
  • Keep an eye on your ticket in case there are any reservations raised before it can be added.
  • Bask in the glory of being a typo contributor!

Published on 09/06/2008 at 12h06 by Frédéric de Villamil, tags , , , ,

Powered by Publify | Photo Startup stock photos