The document summarizes key points from a presentation on using less code in Joomla development. It discusses evaluating whether external code is needed to accomplish tasks, prioritizing security by using code you understand, and how to implement forms, models, views, controllers, and libraries in Joomla according to MVC patterns. Examples are provided of how to add form fields, validate data, and include jQuery, Bootstrap, and other libraries while avoiding version conflicts.

2. JoomlaDay 2017
Chicago
Less is More
Matt Christensen
@the_real_mattc

3. Who am I?
● Developer
● Offense and defense
● PHP - WordPress - Joomla - .Net
● Analytics
● Freelancer

4. Introduction
● Look - learn and grow before adding/buying unknown
code
● What do you need to accomplish?
● Do you need external code?
● Is it too complicated?
● Time

5. Introduction
● Security - you own the code - you know the source
● If not you - your team
● Duplication of code - multiple copies of the same library

6. Speed
● Not always a time saver to add third party code
● Last 20%
● Need to weigh the options
● Trust your team

7. Outline
● MVC
● Forms
● Libraries

8. Components - MVC
● Not true MVC
● MVVM-C
● Explain (code sample)

9. Model
● Interacts with data
● Returns data to the caller (view - maybe controller)
● Logic and processing can be done
● Business rules
● Calling the database

10. View
● Calls model(s)
● Naming can be accessed by default - see example
● Prepares display

11. Template(tmpl) - View-Model
● Acts like a view-model
● Displays to the screen
● Calling View
● NO LOGIC HERE

12. Controller
● Traffic cop
● Executes functions based on task parameter

13. Code

14. Forms

15. Forms
● Demo - contact form

16. Adding Form Fields
● Inside Models
● See com_contact

17. Validation
● Add rule path
● Classes act as rules
● com_contact

18. Libraries
● jQuery
● jQuery UI
● Bootstrap
● Take a look

19. jQuery
● No conflict mode (jQuery vs $)
● Version difference

20. Bootstrap
● Version issues
● 2 vs 3

21. Extras
● Update / stay up to date
● Use version control
● Backup

22. Conclusion
● Try before you buy
● Trust your team
● Inspect code
● Know versions
● Update/backup/source control