Gantry 6.0.2-rc.1
The first public release candidate in the Gantry 6.0.2 line is published on GitHub under matthewxmurphy. The release notes tell the whole story, including the strict benchmark result. No hiding the work.
At LinuxWorld 2008, Joomla and WordPress debated on stage and Matthew was in it for Joomla. Joomla was the CMS. WordPress was a blog. This roadmap is the rematch: bring Gantry up to modern and bring what was built for WordPress home to Joomla.
The first public release candidate in the Gantry 6.0.2 line is published on GitHub under matthewxmurphy. The release notes tell the whole story, including the strict benchmark result. No hiding the work.
The domain is back, the public site is up, and the contact form is protected and working. The proving install runs Joomla 6.2 at testing.joomlamafia.com.
Thirty catalogued JoomlaMafia extensions were inventoried. Twenty seven have source staged for the port, and the three source gaps are named instead of papered over.
The smallest self contained system plugin goes first. It exercises manifest conversion, namespaced code, install and enable, a real function test, Web Services registration and CalVer stamping.
The flagship package follows: component, content plugin and the first real house API for gallery data. A port is not done because code exists. It is done when it installs and works on Joomla 6.2.
MafiaCRM, MafiaSMTP, MafiaForm, MafiaCart and MafiaSocial are specified and researched against the advanced products they replace. The target is advanced parity, not a lite clone with the hard parts left for addons.
One site houses the true MafiaCRM hub. Every other licensed site runs the lightweight bridge and works through the hub. That one authority is what makes the fleet view real.
BootmarkAccess, HTML5AV, InfiniteScrollDown, Masonry and Workarounds follow, then the Vanilla theme comes forward from its Joomla 2.5 base.
The legacy modules come first, then the components. The Dealership component goes last because it carries real dealer and vehicle data, and the data migration is its own step.
The WordPress and Grav tracks trail the matching Joomla work. Each version gets built from behavior that was proved again on Joomla, not from legacy code alone.
The planned paid layer is a particle library, a template cloud, editor polish on the Gantry layout manager and, in phase two, a one way Elementor layout importer.