Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Joomla for PHP Developers (ditching com_content)

717 views

Published on

Presented at DC PHP Meetup, 10/10/2011

We'll take a look at Joomla from the developer perspective, setting aside the typical configurer process and instead introduce the custom component structure, where to put your function libraries, a better theme format, core modifications for a better UX and more.

Published in: Design
  • Be the first to comment

  • Be the first to like this

Joomla for PHP Developers (ditching com_content)

  1. 1. Joomla for PHP Developers (ditching com_content) > Anthony D Paul
  2. 2. Who am I… › Technical lead at Fathom (end-to-end; 5 years) › User experience developer › @anthonydpaul
  3. 3. What we’ll talk about › Project overview › Out-of-the-box strengths & weaknesses › Anatomy of a component (code samples) › Rapid prototyping (breaking fixing $h*!) › Finishing the job (testing, theming, testing, launch)
  4. 4. Project overview › Installers/Configurers versus developers › CMS versus framework › Development cycle (Long Term Support versions)
  5. 5. Out-of-the-box strengths & weaknesses › Documentation =  › Administrative menu bloat › Article system (all for 1 and 1 for all) sucks; causes all kinds of learning curve BS; ultimately kneecaps
  6. 6. Out-of-the-box strengths & weaknesses
  7. 7. Out-of-the-box strengths & weaknesses › Documentation =  › Administrative menu bloat › Article system (all for 1 and 1 for all) sucks; causes all kinds of learning curve BS; ultimately kneecaps
  8. 8. Out-of-the-box strengths & weaknesses
  9. 9. Out-of-the-box strengths & weaknesses › Documentation =  › Administrative menu bloat › Article system (all for 1 and 1 for all) sucks; causes all kinds of learning curve BS; ultimately kneecaps
  10. 10. Out-of-the-box strengths & weaknesses
  11. 11. Out-of-the-box strengths & weaknesses
  12. 12. Out-of-the-box strengths & weaknesses › Documentation =  › Administrative menu bloat › Article system (all for 1 and 1 for all) sucks; causes all kinds of learning curve BS; ultimately kneecaps › However… › Common tools (ACL, media management, WYSIWYG editor, etc.) › Makings for a nice admin experience
  13. 13. (code samples)
  14. 14. What we talked about › Project overview › Out-of-the-box strengths & weaknesses › Anatomy of a component (code samples) › Rapid prototyping (breaking fixing $h*!) › Finishing the job (testing, theming, testing, launch)
  15. 15. Closing remark › Build your own library
  16. 16. Thank you! > @anthonydpaul

×