As you mention, the system is in beta testing. It works well in most situations, but one of the challenges for us is making something that can be embedded in a wide variety of sites and publishing platforms, without forcing them to know much about how it works. We currently support WordPress, and also have a PHP library for people who want more control over the way WWL appears in their sites. Movable Type is coming soon, as are Ruby and ASP libraries. We are open sourcing most of the system so that people can adapt it as needed.

WWL is not limited to WordPress. It treats WordPress as a front-end to a global translation cache. When people post translations to your blog, they will appear on your site, as if they are part of it. They will also appear in the translation cache and search service. This makes translated texts visible to search engines, and makes them easy to link to. So, someone could translate one of your posts. Someone else could find it, and then link to the translation.

Our goal with WWL is not to create a destination, but to provide publishers, readers and translators with a suite of tools that are embedded in a wide range of platforms. If we do our job right, two years from now, people will be reading translated content without knowing how they found it.

PS – if you know any WP style gurus, we’d welcome suggestions about how to make the WP plugin play nicely with a wider range of WP styles.