When I started publishing more technical content on my Joomla website, one of the first practical issues I ran into was code formatting. A normal article editor is fine for regular text, but it is not ideal when you need to publish PowerShell scripts, Terraform examples, Bicep templates, YAML pipelines, JSON configuration, PHP snippets, or HTML blocks.

For a technical blog, readable code snippets are not just a visual improvement. They make the article easier to follow, easier to copy from, and much more professional. Poorly formatted code can quickly make a useful article look messy, especially when indentation, brackets, comments, or multi-line commands are important.

In Joomla, there are a few different ways to handle code snippets and syntax highlighting. Some options are built into Joomla, while others require installing an additional plugin or extension.

1. CodeMirror editor in Joomla

Joomla includes the CodeMirror editor as one of the available editor options. It is mainly useful when editing code inside Joomla itself, for example when working with templates, modules, custom HTML, or plugin configuration.

However, CodeMirror is not really the same thing as front-end syntax highlighting for blog articles. It helps inside the Joomla administrator interface, but it does not automatically make code blocks in published articles look like professional developer documentation.

In other words, CodeMirror is useful for administrators and site maintainers, but it may not be enough if your goal is to display nicely formatted PowerShell, Terraform, YAML, or JSON snippets to readers on the public website.

2. GeSHi-based syntax highlighting

Another traditional option is using a GeSHi-based syntax highlighting plugin. GeSHi, which stands for Generic Syntax Highlighter, has been around for a long time and supports many programming and scripting languages.

This type of plugin can be useful if you want to wrap code in a specific tag or shortcode and have Joomla render it with syntax highlighting on the front end. Depending on the plugin version, it may support common languages such as PHP, XML, HTML, JavaScript, SQL, PowerShell, and configuration-style code.

The main thing to check is whether the plugin is still actively maintained and compatible with your Joomla version. Some older syntax highlighter plugins were built for Joomla 3 or earlier, so they may not be suitable for Joomla 4 or Joomla 5 without testing.

3. Prism.js-based syntax highlighting

For a modern technical blog, a Prism.js-based solution is usually one of the cleaner options. Prism.js is widely used for front-end syntax highlighting and supports many languages commonly used in infrastructure and DevOps articles.

This is especially useful if you regularly publish examples using:

• PowerShell
• Terraform HCL
• Azure Bicep
• YAML pipelines
• JSON
• PHP
• HTML and CSS
• JavaScript

A Prism-based plugin can make code blocks much easier to read and can usually be styled to match the rest of the website. Some implementations also support line numbers, copy buttons, and different colour themes.

Before installing any Prism plugin, I would check whether it supports the Joomla version currently used by the site, whether it loads only when needed, and whether it allows custom language aliases such as powershell, hcl, terraform, bicep, and yaml.

4. JExtBOX Code Display

JExtBOX Code Display is another Joomla extension that can be used to display code snippets inside articles. It typically works by allowing the author to place code inside a specific syntax or shortcode, which the plugin then renders on the front end.

This type of extension can be useful for a blog where most articles contain practical examples, scripts, commands, or configuration files. The benefit is that the formatting becomes more consistent across the whole site, instead of manually styling each code block.

As with any Joomla extension, the important checks are compatibility, update history, documentation, and whether the plugin works properly with the article editor you are using.

5. RokPad and editor-focused extensions

Some Joomla extensions focus more on improving the editing experience rather than improving how code appears to visitors. RokPad is an example of an editor-style extension that was designed to make editing code inside Joomla easier.

These tools may be useful if you regularly work with templates, overrides, or custom code directly inside the Joomla administrator area. However, for a technical blog, I would treat this as a secondary requirement.

The main requirement for publishing articles is front-end code rendering. The editor experience is helpful, but the reader experience matters more.

6. Developer debugging tools such as J!Dump

J!Dump is not a syntax highlighter for blog articles. It is more of a developer debugging tool for inspecting variables, arrays, and objects while working with Joomla code.

It can be useful during development or troubleshooting, but I would not use it as a solution for publishing formatted PowerShell, Terraform, or YAML snippets in articles. It solves a different problem.

What I would look for in a Joomla code highlighting plugin

For a DevOps or Azure-focused technical blog, I would not install a plugin just because it says it supports syntax highlighting. I would check a few practical requirements first:

• Compatibility with Joomla 4 or Joomla 5.
• Support for modern languages used in cloud and DevOps articles.
• Support for PowerShell, YAML, JSON, Terraform HCL, Bicep, XML, HTML, and Bash.
• Ability to preserve indentation and spacing.
• Clean front-end styling that matches the website template.
• Optional copy-to-clipboard button for longer code snippets.
• Minimal impact on page loading performance.
• No unnecessary JavaScript or CSS loaded on pages that do not contain code.
• Clear documentation and simple shortcode or HTML usage.
• Active maintenance and recent Joomla compatibility notes.

My preferred approach

For my use case, I would probably avoid relying only on the built-in Joomla editor. CodeMirror is helpful inside the administrator interface, but it does not fully solve the problem of displaying clean, readable code snippets to website visitors.

A better approach would be to use a lightweight front-end syntax highlighter, preferably one based on Prism.js or another modern JavaScript highlighting library. This would give better-looking code examples in articles and make the blog feel closer to proper technical documentation.

I would also keep the implementation simple. For example, code blocks in articles could use a structure like this:

Get-AzResourceGroup

Or for Terraform:

resource "azurerm_resource_group" "example" {
  name     = "rg-example"
  location = "australiaeast"
}

This style is clean, portable, and easy to understand. It also avoids locking every article into a complicated Joomla-specific format that may be hard to migrate later.

Final recommendation

For a Joomla-based technical blog, I would separate the problem into two parts. The first part is the editing experience inside Joomla, where CodeMirror can help. The second part is the reader experience on the public website, where a proper syntax highlighting plugin is needed.

If the blog regularly includes Azure, PowerShell, Terraform, Bicep, YAML, and JSON examples, then a modern Prism.js-based plugin or similar front-end syntax highlighter would usually be the most practical option. It gives the site a more professional look, improves readability, and makes long technical articles much easier to follow.

Before choosing a final plugin, I would test it on a staging copy of the Joomla site, confirm Joomla 4 or Joomla 5 compatibility, check the impact on page speed, and verify that the most common DevOps languages are displayed correctly.