My SEO-optimized Joomla CMS template development workflow.

It looks simple. Right? Hold on.

Joomla CMS supports a powerful and flexible template integration process. A non-technical administrator can use it to install any third-party template. However, not all third-party templates are SEO optimized.

I invested years of my efforts and created the five-step workflow process. It helps me create beautiful and performant templates every time.

Static HTML pages

My customer can give me Figma designs, Canva designs, or rough sketches. These give me an idea of what my customer wants from me.

I start creating static HTML pages from these artworks using TailwindCSS. I do not worry about Joomla configuration, data flows, or any other dynamic stuff at this step. I use all static data. It helps me to build my concept quickly.

Once I finish it and my customer has confirmed these static pages. I start breaking them into layout positions.

Layout positions

I start breaking a layout into different positions with proper names. These proper names help adjust various modules into the layout positions without a second thought. But why?

The Joomla template system does not render an entire HTML page into proper positions. The Joomla admin needs to assign each module to their respective position in the layout. Remember, each position may have multiple modules. I need to make sure the website layout adjusts accordingly in such cases.

Next, I allow the administrator to configure the default layout.

Template configuration

I do not want the website administrator to worry about the template configuration. Sometimes he wants to change the theme color, font styles, or layout position. Sometimes the customer has no idea of the configuration. I therefore take time to question him or infer the needed configuration.

I prefer not to confuse my customers with the configuration stuff. I know he will start asking me about the global configuration after reviewing the first draft anyway.

Override default views

Joomla comes with many default components like article, contact, search, and tag. I at least override their default views so that my customer does not get confused. I know the customer might not be aware of the default views. They install any template and assume all default views will be updated automatically.

I choose to update the default views for all base components. My work does not end here.

I question my customer about third-party extensions he might have installed on the website. That gives me a clear understanding of what other views I need to update.

For example, one of my customers installed a third-party contact extension. My template did not work as he expected. However, upon inspection, I found the extension and updated its default views. Everything worked.

Next, I bundle the template as the final delivery process.

Template installation build

I do not assume that all customers will share the website’s administrator access. I therefore bundle all template files into an installation zip file. I share this file with my customer, even with administrator access, so that he can try to install the template.

I noticed this always worked. I am ready to see installation error messages. Upon this, I rebuild the entire file and test it again.