I've posted an article that hopefully clarifies and lays to rest Trongate's position when it comes to Composer, Packagist and PSR-4.
The URL is:
https://trongate.io/essays/composer-packagist-psr4-where-does-trongate-stand
For anyone in a hurry, Trongate's stance is broadly the same as that of WordPress.
Neither WordPress nor Trongate builds its core architecture around PSR-4 autoloading. However, developers who wish to use Composer, Packagist and PSR-4 are welcome to do so.
I also have some documentation due to go up within the next 24 hours that will provide clear guidance on using Trongate with Composer. If you're reading this after 23rd September 2026 then that documentation has (hopefully!) already gone live.
DC
Composer, Packagist And PSR-4 - Clarifying Trongate's Position
12 days ago
12 days ago
#1
7 days ago
#2
That means Trongate's ecosystem is as large as any other PHP framework or larger if module market is included.
6 days ago
#3
Trongate v1 did indeed have a Module Market, and it was a valued part of the ecosystem. It was subsequently retired, and the official position today is plain: no code sharing platform of any kind is currently available for Trongate. A successor may yet come, but it would be under a different name and would probably differ somewhat from what came before — and it would be announced properly (forum announcements, videos, and all the rest).
Trongate is open source, of course, and nothing stops anyone from launching whatever they wish within the terms of the licence. That, however, is not the same as an official marketplace, and it should not be presented as one.
So the honest comparison is this: Trongate's ecosystem cannot be measured by downloadable add-ons, because there is currently no market from which to count them. What the framework offers instead is completeness — database, validation, file handling and templating all arrive as native modules, so a full application can be built with no third-party dependency whatsoever. 🎩
Trongate is open source, of course, and nothing stops anyone from launching whatever they wish within the terms of the licence. That, however, is not the same as an official marketplace, and it should not be presented as one.
So the honest comparison is this: Trongate's ecosystem cannot be measured by downloadable add-ons, because there is currently no market from which to count them. What the framework offers instead is completeness — database, validation, file handling and templating all arrive as native modules, so a full application can be built with no third-party dependency whatsoever. 🎩
HEADS UP: Grady is our friendly AI assistant. The above post is designed to help, but a quick double-check is always a smart move.
3 days ago
#4
I like the point about completeness. I'm still learning PHP, and I find it much easier when the framework already gives me the things I need instead of having to look for several different packages.
And I think it's good that Composer can still be used when you need something extra. Having the choice is better than making everyone work in exactly the same way.
For me, good code is a little like good typography. There needs to be enough structure to make things clear, but not so much that the structure becomes the thing you're noticing.
And I think it's good that Composer can still be used when you need something extra. Having the choice is better than making everyone work in exactly the same way.
For me, good code is a little like good typography. There needs to be enough structure to make things clear, but not so much that the structure becomes the thing you're noticing.