If I was MODx, I would start an education program on it. Kind of like the old Apple vs PC commercials. Scream and shout the benefits of MODx over (big name CMS here) and make that very visible. Differentiate and attract attention.
☆ A M B ☆
Quote from: smashbrand at Mar 28, 2013, 06:43 PMAs an agency, that is where we were at before MODx. It's a huge niche and with the right education program (marketing) it could really be opened up. [ed. note: smashbrand last edited this post 13 years, 6 months ago.]If I was MODx, I would start an education program on it. Kind of like the old Apple vs PC commercials. Scream and shout the benefits of MODx over (big name CMS here) and make that very visible. Differentiate and attract attention.
I would think there's a whole sector of WordPress and Joomla site creators out there that are frustrated with the limitations of the platforms, and those site design limitations could be largely alleviated by moving to MODX.
☆ A M B ☆
☆ A M B ☆
Modx cloud is a fantastic product, and by using it I feel in a very small way we are ensuring the future of modx. That said I am not thrilled about sending clients mysite.mycompany.siphonlabs.com urls !
Will the "modxcloud.com" domain name still be left available for in-development domains and for the Cloud dashboard login? - Will we still be able to rely on the MODX branding to help support our MODX-focused businesses?#1 - While this gets a bit tricky, we're definitely going to look to see if this is possible. I'd like it to be, if we can.
No, we do not (at least we do not plan on adding any, there are tools like that in the wild, but not things we will offer).
Do you plan to have one-click WordPress > MODX/MODX > WordPress migration tools? - if you do, would is be possible for an account admin to switch these off so clients don't play around with them?
When MODX Cloud was announced it was a real bonus for my business, it showed dedication from the MODX core team and also showed a reliable platform for my clients to build on to.
Is the reliable backing from the respected MODX brand simply going to be changed to SiphonLabs?
Play nice guys, please don't say community contribution is up now like this was ever possible before. I think what you should state is that you have made community contribution hard in the past.Not by intent, by any means.
Some decisions were made that didn't involve the community when what is now MODX 2 came about, ExtJS for 1 has kept community involvement low, we have just now started to grasp how to use the thing.To be frank, if we switch to Angular JS or something similar in the future, people will have to re-learn that and we'll have a similar learning curve problem. Learning software just takes time. At the time MODX 2.0.0 was released, jQuery was nowhere near able to support the UI we wanted to make.
The use of Github only started since MODX 2 and whatever you were using before was behind hidden doors.We used SVN, and actually were pretty transparent about it - we had quite a few contributors at that time, and a lot of people complained about us moving to Git because they liked SVN and thought the change "made it hard for them to contribute". So, yeah.
MODX Bug Tracker still being something separate from the Github repo doesn't help this, Issues is was more easier and accessible for anyone to use, I find Tracker daunting and less intuitive.GitHub Issues did not exist at MODX2 release time. (Didn't till around 2.0.4 I believe.) Plus, there's a *lot* to developing Revo and related projects, and Issues, while neat for small projects, doesn't really scale well to massive, distributed systems like MODX Revolution.
I have to disagree there; you're basically saying with this sentence Jason and I have not been open to new tech - that's not at all true; I've stated in multiple posts we are 100% OK with switching tech as long as it meets the functional requirements of the product (I've even said I wouldn't mind moving from ExtJS should we be able to find a suitable alternative, which there are definitely more of now than there were 2 years ago). As for others, Jason and I have discussed using Composer for MODX3 and beyond, and are looking at other tech solutions as well. We're definitely not set on building everything from scratch.
Many times have I asked why not start using other Components inside of MODX to lessen the time core devs spend on reinventing the wheel, this has not been received nicely by any member of the core dev team I have spoken to.
I am happy for what you guys are doing over at SiphonLabs and wish you all the best. I hope this message is received positively rather than negatively, take notes and not try and reply to address every comment in a defensive way.Oh, I hope our replies are not being taken negatively. I'm just trying to clear through some of the FUD here and get to the basic facts and numbers behind MODX's situation. I hope people can empathize with that.
As Director of Cloud, I can guarantee that won't happen. If you'd like to know, I'll be blatantly transparent: here's our priority roadmap for SiphonLabs for the next couple quarters:
One thing I find myself wondering is how much is the SiphonLabs team going to prioritize developing Wordpress Cloud features over requested features such as script automation with CRON jobs (or something similar). I've got a handful of clients that were ready to move sites over the day that feature landed, when it was MODX Cloud at least.
But it was my understanding that you could go with the Magento model, offering Community and Enterprise level editions eventually. I thought that was a possible direction you were headed in. Did that change? Why did that change?A few reasons:
Why not asking for a 5$ or 10$-donation at the download (-> and for motivation, you can add the newly created modx-website with rel follow, a ascreenshot and a small description to a catalogue of MODX-made websites on modx.com for your donation ---- or someting like that)?