Book Image

Developing Extensions for Joomla! 5

By : Carlos M. Cámara Mora
5 (2)
Book Image

Developing Extensions for Joomla! 5

5 (2)
By: Carlos M. Cámara Mora

Overview of this book

Joomla! 5 is a groundbreaking CMS that helps you take a significant leap into the world of content management systems. Joomla! 5 features a variety of impressive new features that align with current web standards and enable you to experience lightning-fast performance for optimal web page optimization, leverage the new code architecture, and tap into the WebService API, among others. This book takes you on a journey of extending Joomla's capabilities by developing your own extensions. The chapters not only explain the key concepts behind Joomla's architecture but also equip you with the latest techniques for crafting components and plugins. You’ll discover how to leverage existing features within Joomla! to empower your extensions and create tailored solutions. The book takes you from the initial stages of planning your extension development to a fully featured finished product. As you advance, you'll learn invaluable techniques for testing your extension, addressing common issues, and preparing it for publication. The concluding chapters of this comprehensive guide teach you how to test your extension for common issues, along with how to publish the extension for everyone to use. By the end of this book, you’ll have the confidence and skills to complete the cycle of extension development.
Table of Contents (21 chapters)
1
Part 1: Developing Components
8
Part 2: Developing Modules and Plugins
12
Part 3: Extending Templates
15
Part 4: Distributing Your Extensions

Why do we need child templates?

In Chapter 10, Creating Unique Web Applications with Template Overrides, we saw the power of Joomla! to create custom-designed web applications with template overrides. We can use template overrides to change the design of our component area for a website, we can add new styles or JavaScript-loading new assets, or we can even create new view types for our menus. This might seem enough, but there are some additional points:

  • With template overrides, we cannot change the main site structure, as we cannot edit the template positions.
  • With template overrides, we cannot edit web assets for the whole site, our changes will be limited to the areas of the site where the override takes place
  • Most important, we cannot create an override of an override. You can have only one override per element. This is very important when the template you use uses a template override for the layout you want to override.

Child templates inherit files and...