Live data from Hacker News

A case for something, anything more simple than WordPress

colin.getbarley.com

21–30 of 51 posts

Re: A case for something, anything more simple than WordPress

#22
post #2

I used WordPress for a while, but switched to a host of static site generators about two years ago. One of the big reasons I switched was because WordPress was so huge, and unnecessarily so. Their big overhaul of the wp-admin section, in 2.5 I think, de-emphasized the post writing page (something which was previously instantly accessible). That's what started pushing me away from WordPress. Recently I've started look…

These days there's a "+ New" button at the top of every single page of a Wordpress site - both the admin section, and the public section if you're logged in - that lets you add a new post, piece of media, page, or user. Or more; I use the Comic Easel plugin to manage my webcomic, and it lets me add a new page that way.

That said if you want a CMS that only does the five things you need, you don't want WP.

Re: A case for something, anything more simple than WordPress

#23
I point complete novices to http://www.weebly.com/.

It has a gui site builder (wysiwyg) and what not, and is considerably simpler than wordpress.

What does barley have over weebly?

Can I download barley and install on my servers like I can with wordpress? If not, this is apples and oranges.

Re: A case for something, anything more simple than WordPress

#24
I'm so weary of people pitching the solution to WordPress and then tossing a proprietary cloud hosted thing at me. That's a complete non-starter.

All the time I hear from fellow devs "oh don't advertise you use WordPress, it's irrelevant to clients." Tell that to my bank account and all the jobs I've stolen from agencies who wanted to use their BS proprietary CMS.

I sell WordPress like this: when you want a rebuild in 10 years and I'm in Thailand smoking drugs with your money pile you just gave me, you'll be able to find someone to work on it no problem.

There's plenty to dislike about the WP codebase, but we all have to remember that WP was made in an era when coding reasonable software in PHP was nearly impossible. Nothing backwards-compatible can happen there that isn't going to destroy all the millions of existing sites. It's still pretty freaking easy to build a site with, especially when you compare it to other CMSes of that era.

Moreover, their development roadmap is actually really solid. I like where WP is going. I unfortunately would no longer recommend it for basic blogging due to its complexity but as a CMS, there's really not a lot of free software options that can function on that level without extensive database programming and security knowledge.

Re: A case for something, anything more simple than WordPress

#27

I'm using Wordpress for a project because of the wealth of existing templates and plugins. Without these Wordpress is not terribly interesting; it's not Wordpress. Once you drop the ecosystem there are plenty of alternative to creating static or near-static sites. edit: I should point out that more alternatives for creating Web content is, on average, a Good Thing. Presenting a tool, however good, as an alternative t…

If you don't like WordPress[1], and don't want your authors/editors to have to know any programming, but you do want fast cheap and easily hackable PHP for the CMS itself, consider a free open source alternative called TextPattern:

http://textpattern.com

It has good documentation:

http://www.textpattern.net/wiki/index.php?title=Index

And an ecosystem of plugins:

http://textpattern.org

The separation of editing and design roles in the admin is worthwhile as well.

// 1. Having built and hosted multiple WP sites scaling to millions of uniques a day, and even having built and managed a WP install for the most notorious domain name in the world, I have to say I don't advise it for most cases.

Re: A case for something, anything more simple than WordPress

#28

I'm so weary of people pitching the solution to WordPress and then tossing a proprietary cloud hosted thing at me. That's a complete non-starter. All the time I hear from fellow devs "oh don't advertise you use WordPress, it's irrelevant to clients." Tell that to my bank account and all the jobs I've stolen from agencies who wanted to use their BS proprietary CMS. I sell WordPress like this: when you want a rebuild i…

So the advantage of Wordpress isn't anything you could find by looking at Wordpress itself... it's the popularity and huge amount of support that brings? Makes sense.

So the "next Wordpress" won't be able to be the next Wordpress until it's popular. It'll have to be good for other reasons until then.

Re: A case for something, anything more simple than WordPress

#29

I'm so weary of people pitching the solution to WordPress and then tossing a proprietary cloud hosted thing at me. That's a complete non-starter. All the time I hear from fellow devs "oh don't advertise you use WordPress, it's irrelevant to clients." Tell that to my bank account and all the jobs I've stolen from agencies who wanted to use their BS proprietary CMS. I sell WordPress like this: when you want a rebuild i…

This is so true. Open source and hosted commercial products fill totally different niches. Sure, there are some projects where either one would suffice, but many where that's not true.

I'm working on an open-source Wordpress replacement right now. (No link yet. I want to get a little farther before I put it out there.) The basic concept is:

1) Use Rails, to ease development of plugins and per-site functionality.

2) Don't save content or site config in the database. Save it to disk.

3) Git keeps track of your content and config, just like a regular Rails project. The user-friendly admin interface is actually just a wrapper around Git plus a text editor and some menus. Developers can work in a text editor and a terminal while the client works in the GUI.

4) Because content and config are Git-controlled text files and not database records, you have a sane workflow for developing locally then deploying.

Re: A case for something, anything more simple than WordPress

#30
Here's a crazy idea: You're a developer. If it's too complex for your customer, then simplify it. Fight the urge to build something new just because you can. You're really the only person that cares that you built it, everyone else just wants something that works.

I understand why you're following 37signals' simplicity model, but those markets didn't have flexible CMS' to start with like we do. The beauty of WordPress is that it's easy to hide and remove extraneous features. It has everything you need and you can just remove the stuff you don't, just like the way a sculptor chisels away the unneeded parts. It's building from a different direction.

WordPress is a tool, not an end product, and it's been around for over 10 years.

Face it, websites are a commodity these days. What new features, processes, or anything else exist that WordPress can't do with a few tweaks? Front-end editing, one-click setup, drag and drop, it's all easier to add than building from scratch.

If your goal is to create value, then think hard about what problem your customer is trying to solve. If it requires something new, then by all means build it! But I don't see this as one of those cases.

Post reply on HN