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 ?
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
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.