PyroCMS 3 Ecosytem
haeflimi - 1 year ago
Hey Ryan and other Pyro People out there,
I am evaluating and testing different CMS Systems to use as a base for a modular, and flexible application in the field of Online Gaming Communities, eSports and LAN Parties. - Since i am a CodeIgniter Veteran and built websites using PyroCMS 2 before i've had an eye on PyroCMS3 ever since it came out. From a technical perspective i would still favour it - but there are other aspects that i've to take into account for this project and other stakeholders and developers that i have to convince.
One thing that puzzles me a lot and has prevented me from committing to pyroCMS so far is the seemingly non-existing Ecosystem. When PyroCMS3 was first released i had high hopes that soon the AddOn store would fill up with various useful AddOns/ Themes and whatnot thereby becoming a practical platform to eventually publish the AddOns that i am going to create (and partially have created already) in the process of the mentioned project. With bearly over a dozen AddOn's in the store this has obviously not come to pass and the whole ecosystem pales in compare to other modern CMS's like octoberCMS, ModX or even Concrete5.
Am i wrong and just not looking in the right place? Does anybody here have a good guess why that is? - Why are you devs out there not putting your Code on the store? Is it too hard to get AddOn's approved for the store or are there just to few devs working with PyroCMS3?
Anyone willing to give me some reasons why we should opt in on PyroCMS anyway? - I'would be very happy to hear them.
Furthermore it would be very helpful to have some actual data on how many people are using PyroCMS, how many Pro Subscribers it has or how well the store is used. - Information i can find on most competing CMS, but not on PyroCMS.
Something like that for the store would be nice: https://octobercms.com/leaderboard although with the current number of AddOn's it might not make that much sense.
ryanthompson - 1 year ago
@haeflimi you mention your target audience (which may be niche given your details earlier) you could use the addons module to deliver your subscription / paid software since the addons module supports adding your own repositories (and removing the ones that are there too).
If I were building a custom "distribution" of Pyro (which was built with distributions in mind) for an audience I would probably fork the base project - which is just a composer file and some adjusted laravel files - and ship my flavor Pyro and a custom admin theme maybe and a custom addons module too so it comes with my repo only.. which people can buy on my site. Your project might be different as far as white-labeling n such but just as an example - you can do what you're after now. Just our PYRO store is not setup for that kinda stuff. YET ^_^
As for the PYRO ecosystem.. that's where we are heading. Buying online - and deploying via addons module (click to download like WP). Keep in mind this STILL uses composer behind the scenes so it's easy for users to see that updates are available and update. Easy for developers who make this stuff cause it's parallel to their workflow anyways. It's just Pyro itself is not there yet - we have features and projects we work on too. But it will come. And if the addons are developed in such a way.. no code will be needed by the end user. Much of what we have now are like that anyways.
Hopefully that makes sense :-P