Joomla 3 has been around for a long time. It is easy to forget how successful the series has become and how much it has evolved over the course of the minor versions.
As it approaches its final year as a mature, stable version of Joomla, it is about to enter its security support phase.
Joomla is a beautifully matured CMS, and long term Joomlers might knowingly nod, when I say it was a bumpy ride at times. Have a look at this article 'Celebrating Joomla 4' to get an idea of the new features of Joomla 4.
If you are (relatively) new to Joomla, chances are your website uses a template compatible with Joomla 4 (or at least your template developer provides a fully J4 compatible version of the template). Then you are lucky and this article is of no concern for you. But what if your website has been running for years now, and you are considering a migration from Joomla 3 to Joomla 4?
The mission: Recruit about 20 mentors to help guide four students through four projects that will ideally be integrated into future releases of Joomla 4.
In June 2020 Google published an article called “Protect your resources from web attacks with Fetch Metadata” on web.dev. It's a new set of request headers to protect your site against common attack vectors for web applications.
Have you ever wondered how new features make it into the Joomla core? While in the past, Joomla followed the paradigm "write the code, then we look at it and make a decision," Joomla today has a professional process that supports the "think first, then implement" strategy.
As covered a few times already in the magazine and announced in the Developer Portal, Joomla 3.10 will be released together with 4.0 and will then be supported for two years after its initial release.
Hi ?! My name is Ben Morss. I’m a Developer Advocate at Google, where my job is to help make it easier to make websites that are excellent for everyone. I also used to be a "serious" musician, so you can still find me recording songs in the attic that's now my workspace. And laboring on my opera that's sort of about Steve Jobs.
Good bug testing for software projects is about destruction not confirmation. You can easily follow the test instructions for a Pull Request (PR) and show that it fixes the problem it’s designed to fix. But what else might the new code be doing?
Contributing to the Joomla project is much easier when you’ve got a local testing environment. This month we’ve prepared a tutorial on how to go about configuring a local testing environment.
By accepting you will be accessing a service provided by a third-party external to https://magazine.joomla.org/
Community Magazine 
