An alternative structure for the Joomla! Project

You might have read my article ”Hard Truth“, this here is in some way a follow up.

I must say that I haven’t taken too much attention to the structure change discussion the last years. I can remember that I suggested that we should look outside of the US because my feeling was that the NYC State law has too many restrictions and is not really a good place for having OSM as organization located. Anyway, I don’t know if someone looked into this, so I did today.

Hard truth!

You might have noticed there is a proposal for a structure change for the Joomla! project. We have had a government working group for a couple of years now and today was the day they presented their proposal.

Are we doing it right?

Within the last months I looked into other frameworks and other ideas of development. I can't say it changed my mind completely but I see now some things differently. I am developing for the last 10 years or so with PHP, I had always interest in OOP and Design Patterns. I don't think I have written much functional PHP code. I am also deeply involved in Joomla! development and extensions development, I have tried to teach people how to use the framework and what you have to do to make it run with Joomla!

I am really asking myself, if it is the right way we are doing extension development?

{loadmodule} - do it the right way

Probably I missed the documentation somewhere but I struggled to load a specific module within an article.

One way to do it is to create a module-position like "myPositionThatIsNotUsed" and then you have to use the {loadposition myPositionThatIsNotUsed}. That's woking but why we have {loadmodule ....}? In the documentation you can find that you should use it like this {loadmodule mod_xyz}. But what is when you have a couple of "mod_xyz" modules and you like to show a specific one. In the sense of "hours of debugging can save you minutes of documentation" I did a bit of debugging and found how it works.