view release on metacpan or  search on metacpan

t_data/blogsperl.atom  view on Meta::CPAN

    <author>
        <name>Barbie</name>
        <uri>http://barbie.missbarbell.co.uk</uri>
    </author>
    
    <category term="labyrinthframeworkweb" label="labyrinth framework web" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/barbie/">
        <![CDATA[<p>On the 1st January 2011, I released the first Open Source version of <a href="http://labyrinth.missbarbell.co.uk">Labyrinth</a>, both to <a href="http://search.cpan.org/perldoc?Labyrinth">CPAN</a> and <a href="http://github.com/ba...
<p>Labyrinth has been in the making since December 2002, although the true beginnings are from about mid-2001. The codebase has evolved over the years as I've developed more and more websites, and got a better understanding exactly what I would want ...
<p>Labyrinth now is the backend to several Open Source websites, CPAN Testers using it for the <a href="http://www.cpantesters.org/">Reports</a>, <a href="http://blog.cpantesters.org/">Blog</a>, <a href="http://wiki.cpantesters.org/">Wiki</a> and <a ...
<p>As mentioned, I see Labyrinth as a Website Management System. While  many similar applications and frameworks provide the scaffolding for a  Content Management System, Labyrinth extends that by not only providing  the ability to manage your conten...
<p>When writing the fore-runner to Labyrinth, one aspect required was  the ability to turn on and off functionality instantly, which meant much  of the logic flow was described in the data, not the code. Labyrinth  has built on this idea, so that the...
<p>I'm primarily releasing Labyrinth so that I can release all the code  that drives the CPAN Testers websites. Giving others the ability to  better suggest improvements and contribute. The system allows me the  freedom to build websites quickly and ...
<p>More news of plugins and sites being released coming soon.</p>            
]]>
        
    </content>
</entry>

<entry>