Blogger to Bricolage 2.0
Bricoleur Matt Rolf shares his experience migrating from Blogger to Bricolage 2.0. He details the installation, content migration, woes and successes of his journey:
Over the summer I migrated a site I do on the side, the Fake Sigi Soccer website, from Blogger to Bricolage 2.0. The first question is why do this? Why leave something as easy as Blogger for something as powerful as Bricolage? For me it came down to control over my site and control over a tool that I know. Blogger has a number of limitations over what users can do with their design. I thought that for what I was getting with the minimal layout, the code was too heavy and slow to load. I also wanted to optimize my site for users and search engines. Creating a fast loading, navigable, article archive was something that gave me a lot of trouble on Blogger, and was what -- ultimately -- pushed me over the edge.
The installation of Bricolage 2 was fast - much faster than what I've experienced with Bricolage 1.10. In one evening I put together the hardware and had a running Bricolage instance. My four years of experience with Bricolage helped me in this regard, but system administrators who are familiar with CPAN will also have a leg up. If you're new to the command-line interface, be prepared for a challenge.
I was also helped by my reliance on NetBSD and the pkgsrc framework. The most important word of advice for Bricolage installers is "build everything from source" including your installation of Perl. Since pkgsrc does that, and better yet, automates most of it, it's the perfect companion for Bricolage.
Once Bricolage was installed, I spent some time building my templates, elements, and story types. The site needed to be simple but flexible, with regular web pages, article/blog posts, keyword archives, a sitemap, and an Atom feed. The core process took me about a week, followed by tweaks to the templates as was necessary. In addition to the site migration, I did a full site redesign, which you can read about on the site if things like that interest you. Getting the site design right took much more time than setting up the Bricolage templates. Obviously this will vary for other installations.
The migration itself was not too bad, but like many Bricolage administration tasks, it's not geared toward non-technical users. I got the Blogger XML dump of my site and mapped it to my new elements. I used a perl script with XML::XSLT and an XSL Template to convert the Blogger XML into a Bricolage-friendly SOAP format. I also had to run some regex to clean up the code. Specifically, Google has taken to dumping a unique ID into the content field of their blogs, and that was a little tricky to get out.
Once I had the Bricolage-friendly XML, I imported the content without much fuss. I imported about 800 blog posts. I did not migrate any images to the system. Since the migration was relatively simple, the Bricolage-specific work -- installation, template development, import -- took between a quarter and a third of the project time. The rest of the time was spent on the redesign, implementing a KinoSearch search engine for the site, making some needed content and keyword updates, and most importantly, beta testing. The final beta testing period lasted about three weeks.
So, what's it like using Bricolage 2.0? The new workspace and content editing interfaces are a glorious improvement over the previous version. Whereas 1.10 was challenging but trainable, I can actually use the word intuitive to describe several aspects of the 2.0 interface. In bringing new users to the system, the most challenging aspect is explaining how Workflows, desks, the "shelf," workspaces, check in/out, and the editing interface all work together. But the pain of drilling down into story elements has thankfully been eliminated, and the result is a much more usable product. When looking at the current state of enterprise-class content management systems, the Bricolage 2 interface compares favorably.
Not all is golden. I am currently using JS-Quicktags (which inserts HTML tags into text) to get around some bugs with the Xinha WYSIWYG text editor. A couple aspects of the new interface seem like a step back. For example, I still miss the "cancel checkout" button after two months of use. Document publishing is still *the* system bottle neck using SFTP to transfer files. Bricolage can generate around 800 pages of HTML content in 5 minutes for my site, but it then takes 20-25 minutes to distribute those files to the server via SFTP. Not only that, I had to apply some patches were not in the 2.0 release to get the SFTP publishing to work at all. David Wheeler has already rewritten the SFTP framework from the ground up for the next release, and hopefully the other minor issues I've found will be soon be patched for a bug-fix release.
There's no question Bricolage is more powerful than Blogger -- so much so that I've considered expanding my one-person blog to other writers. Since Bricolage can handle the web publishing efforts of very large organizations, it's probably over-kill if you're just one writer. But it sure is fun.
For hardware I'm running two machines. The Postgresql database is on a 1.6Ghz Core 2 MacMini with a 250GB HD and 2GB RAM. Bricolage is on a 2.0Ghz single-core Athlon from early 2005, with a 80GB HD and 1GB RAM. This setup works very well for my needs, and is probably a little more hardware than is necessary. SFTP publishing is far and away the biggest performance bottleneck.
Overall, I'm very pleased with Bricolage 2.0. Once some of the minor bugs are squashed, it's an easy upgrade to recommend to users of Bricolage 1.10. This post only scratches the surface of my installation. I'll be happy to answer any questions via e-mail (mattrolf at me dot com).
Have a similar story to share? E-mail us at the-oc at bricolagecms dot org.blog comments powered by Disqus