Using Confluence as a Website CMS tool? Why not?

confluence_logo.gifMcBlog - place to eat real meat: Stop using confluence as Website CMS tool: “I am watching more and more open source projects backing their website completely on Atlassian Confluence. While this tool is a viable choice for Wikis and documentations, i find it horrable as a website. First of all, you look like so many other projects, because there is a common layout for Confluence. Then you have links that normal webusers dont need and are simply a waste of space.”

While this is certainly true for sites like OpenWFE and Blojsom, you can actually do better by using Confluence as a backend and exploiting its XML-RPC APIs to provide a rather different and altogether more pleasing frontend, like you can see here and here, for instance. The content of both sites is managed using Confluence.

But even if you use Confluence alone, it's not the worst thing you could do. You could be using Maven to generate your website. Now that sucks! ;)

2 Responses to “Using Confluence as a Website CMS tool? Why not?”


  1. 1 Tech rulez

    I like the idea of using confluence as a backend and exploiting its XML-RPC APIs to provide a front-end.

    Pls pass on to me if you can, some more detail on how this could be done.

    cheers,
    tech rulez

  1. 1 rebuilding www.openwfe.org « processi

Leave a Reply