There is at least one other potential newbie entrance point into Catalyst. That is where he/she installs a fully functional application (generally a blog, CMS, forums, etc.), then slowly begins contributing within a plugin architecture, then full applications, as his/her understanding of how the parts work expands.
Or at least, the Catalyst app user will hire someone to work on his application. :) > Octavian said: >> Imho a beginner should not start by creating "best practice" apps, but >> apps >> which help him/her to understand each step as easy as possible. She or >> he >> just need to know that there are better ways that will be learned later. >> > > Your 2012 Catalyst Advent Calendar articles "Catalyst in 9 Steps" embodied > that principle nicely. I'd like to see those articles extended further, > and have them linked in the official documentation. > > Why not set a documentation goal that would allow a perl newbie with Perl > Beginner/(Intermediate) under his/her belt, be able to start hacking on a > Catalyst app, with relevant documentation to take them all the way to a > production ready, best practice site? > > That is where those 2012 Advent articles were heading, I think that is a > great idea. IMHO :) > > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
