CMSMS vs Wordpress

[SanderBroek]

I use both WP and CMSMS, depending on the type of project.

As I see it:

<cut>

Cheers,
Alex

Great analysis, both from a user and a developer point of view.

[Wishbone]

Did you ever work with WP? I mean, really *work* - publishing a lot of articles? I am sure you would see the difference, too. The searchable media archive for itself makes a big difference. Of course, we are talking about bigger sites here ...

No, I haven't used it.. Just trying to get a better understanding. Thanks for the review!

[Felix]

I've been using CMSMS for about 3 years now and have set up sites with Wordpress too.
CMSMS is certainly more challenging for the beginner with a steeper learning curve.
One of the benefits of lots of templates is the ability to learn from them.
The only thing I can think of that would increase the user population would be some good ol' marketing. There's a crowd here in Melbourne, Australia called Sitepoint that publish a couple of regular emails full of hints and ideas. It's mainly focussed on Ruby, but I guess they are associated with a digital media company so they can afford a team of reporters. Here's a link to one of their newsletters http://tinyurl.com/8xbf6tb

[calguy1000]

Keep in mind these facts:

Wordpress is primarily a blogging system that (as it seems, never looked at it that much) Can do some regular content management stuff. It shines at handling large amounts of articles. That's what it is built for.

CMSMS is primarily a content management system that can do some blogging stuff (via an addon module or two). It is designed for small to medium websites where the end user needs to manage content.

These are two different tools for two different jobs. Though they do have some of the same features here and there. I consider it like a pry bar and a screw driver... though you probably could use one to do the job of the other, it's not really designed for it, therefore it won't always work the best. The professional would know when and how to use each tool properly, and should certainly have more than one tool in his 'toolchest'.

For the above reason, we have no plans, or intent (and never did) to compete with the likes of Wordpress. Can a pry bar really compete with a screw driver?

Now that said... there are things planned to make some of the overlapping features, like file uploads a bit smarter and easier to use. But there's no way we're gonna duplicate the functionality of another system just for the sake of competing.

[SanderBroek]

Keep in mind these facts:

Wordpress is primarily a blogging system that (as it seems, never looked at it that much) Can do some regular content management stuff. It shines at handling large amounts of articles. That's what it is built for.

CMSMS is primarily a content management system that can do some blogging stuff (via an addon module or two). It is designed for small to medium websites where the end user needs to manage content.

These are two different tools for two different jobs. Though they do have some of the same features here and there. I consider it like a pry bar and a screw driver... though you probably could use one to do the job of the other, it's not really designed for it, therefore it won't always work the best. The professional would know when and how to use each tool properly, and should certainly have more than one tool in his 'toolchest'.

For the above reason, we have no plans, or intent (and never did) to compete with the likes of Wordpress. Can a pry bar really compete with a screw driver?

Now that said... there are things planned to make some of the overlapping features, like file uploads a bit smarter and easier to use. But there's no way we're gonna duplicate the functionality of another system just for the sake of competing.

Amen!

[carasmo]

I use CGSmartImage for the blog, news, and gallery modules and then I can specify the exact crop to fit or width for any thing (thumbnails, medium, super large) so that users don't break the layout, the the other modules (filepicker) is used on the content pages and since I use responsive CSS, I just put the results in a variable then that variable is put as the source for the CGSmartImage.

Re: SuperSizer.. I haven't messed with yet since I really tell people to size their images down since they are using a shared server and that's just rude to stick up huge ass images.

[carasmo]

500 is not the limit for blog or news posts. It would be unwieldily for that many content pages but most stuff can be done by forking or not forking either the blog or news modules or listit2 and then the content pages can be kept to a min.

[carasmo]

Word!

Keep in mind these facts:

Wordpress is primarily a blogging system that (as it seems, never looked at it that much) Can do some regular content management stuff. It shines at handling large amounts of articles. That's what it is built for.

CMSMS is primarily a content management system that can do some blogging stuff (via an addon module or two). It is designed for small to medium websites where the end user needs to manage content.

These are two different tools for two different jobs. Though they do have some of the same features here and there. I consider it like a pry bar and a screw driver... though you probably could use one to do the job of the other, it's not really designed for it, therefore it won't always work the best. The professional would know when and how to use each tool properly, and should certainly have more than one tool in his 'toolchest'.

For the above reason, we have no plans, or intent (and never did) to compete with the likes of Wordpress. Can a pry bar really compete with a screw driver?

Now that said... there are things planned to make some of the overlapping features, like file uploads a bit smarter and easier to use. But there's no way we're gonna duplicate the functionality of another system just for the sake of competing.