81–90 of 162 posts
I've used Symphony CMS (getsymphony.com) to build several websites, one of them quite large. I love it. It's the first CMS I've used that isn't a total mess architecturally. At it's core it provides a highly customizable interface for maintaining a database of content, XML data sources that pull from that database (or external XML sources), and XSL templates that are combined with the XML to produce the HTML pages of…
WordPress needs more rules I'm convinced Wordpress is successful despite this. No rules implies very low barrier to entry .
Earlier quoted context omitted.
It's massively entrenched because of the network effect of the themes and plugins, no doubt. What will overtake wordpress as a blog/cms platform is something that can allow for a large number of the popular themes and plugins to be dropped in (or converted silently). It probably won't happen, but think of Lotus/Excel, for example (or WordPerfect/Word) - both Lotus and WordPerfect were dominant for a long time. People…
But the thing is, many of the major flaws of WordPress are baked into its theme and plugin formats. Much like with Excel, you'll need to match it quirk-for-quirk to interoperate with it. And what's the point of simply reimplementing WordPress?
The goal would not be to reimplement all of wordpress, but implement a compatibility layer suitable to emulating enough of the basics to allow some migrations and encourage people to try out something new.
There's dozens of CMS and blogging engines out there, but no one has attempted a WP-emulation layer (as far as I can tell). Although, given it's PHP nature, and direct grabbing of $_GET and $_POST and such, it may simply not be possible at all.
For geeks and people who understand technology and programming, I suppose Wordpress wouldn't cut it.
Here's a suggestion, If we can't get WordPress to change, why not fork it and build a "developer" friendly version while maintaining compatibility with subsequent iterations of WordPress? Frankly, I find the people who run the WP development community to be insufferable (Matt included). If you've ever read their discussions for code changes, it just makes you want to pull your hair out. Their pedantic in fighting riv…
Maintaining complete compatibility with WordPress, including any future changes, while trying to clean up design problems (how is this actually possible without breaking anything?) would be a full-time unpaid job from hell and who would actually thank you for it?
To paraphrase Churchill, Wordpress is the worst CMS -- except for all the others. I'd love to find an open-source CMS (preferably in Python or Ruby) with clean, secure, elegant code and a well-organized framework that comes with a friendly admin and active, responsive development community like Wordpress, but so far I've got nothing. (If anyone has any suggestions, please do feel free to share them!)
I like ExpressionEngine if what you really want is a CMS.
WordPress needs more rules I'm convinced Wordpress is successful despite this. No rules implies very low barrier to entry .
I think you mean it's successful because of its lack of rules, and I disagree. WordPress's low barrier to entry stems from a combination of PHP's ubiquity and a positive feedback loop of popularity. More rules wouldn't hurt either of these factors.
To paraphrase Churchill, Wordpress is the worst CMS -- except for all the others. I'd love to find an open-source CMS (preferably in Python or Ruby) with clean, secure, elegant code and a well-organized framework that comes with a friendly admin and active, responsive development community like Wordpress, but so far I've got nothing. (If anyone has any suggestions, please do feel free to share them!)
And don't forget the amazing amount of functionality that's available for free using the plugin system. It's a classic software development problem - Wordpress's complexity is both it's strength and weakness, and will probably be it's downfall one day (but not just yet)
I was helping a photographer friend who bought a commercial theme, which broke admin-side Javascript when he did the 3.4 -> 3.5.1 update. We still haven't figured out exactly what happened, but it just reinforced for me again that a) Wordpress hasn't adequately documented which APIs are stable and not, b) Authors, even of paid add-ons, don't keep their stuff up to date.
Even if the validator was just a grep for function calls outside of a whitelist, that would be an excellent starting point.