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.<p>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.<p>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.<p>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.<p>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.
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.<p>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.<p>WordPress is a tool, not an end product, and it's been around for over 10 years.<p>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.<p>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.
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.<p>Once you drop the ecosystem there are plenty of alternative to creating static or near-static sites.<p>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 to Wordpress however brings a lot of assumptions that may cause people to focus on the wrong things.<p>There's probably a market for a form of Wordpress that could use existing themes but not plugins, and only allowed basic posts and pages, with perhaps a more robust security model. E.g. prevent commenting (in order to avoid having to accept external content) except via Disqus or something.
The problem with this post, and other "WordPressis too complex" posts like it, is that WordPress did not intially start off this way. Wordprrss was originially a simple blog. Once Barley gets enough users, people will want it to do more and more things until it becomes yet another blog turned CMS platform.<p>As for me, I use Jekyll and disqus because I'm just one guy.
About a year ago I moved my blog completely off of Wordpress and onto Piecrust[0]. I realized I didn't need all the dynamic tools available in Wordpress, because blog, and Piecrust has so far worked beautifully.<p>Comments were replaced with Disqus. No more opening my site to any possible security holes, no more having to keep on top of plugin updates, no more crying tears of shame when I snuck a peek at said plugins' source code, I can check in my whole site into github and be done with it.<p>[0] <a href="http://bolt80.com/piecrust/" rel="nofollow">http://bolt80.com/piecrust/</a>
I agree that WordPress is a little convoluted for simple projects. However, you can get great starter themes that eliminate that complexity for you from the get-go. Like the _s starter theme or something like Bones.<p>I think WordPress is often the go-to platform because it's just what people hear about -- plus, it's free. My preferred CMS for websites is ExpressionEngine because it's flexible enough to make it what you want. There's no "loop" that you have to deal with over and over and there aren't a gajillion default things that you have to strip out at the outset of a project.<p>The trouble is that clients are afraid to try something that isn't what their neighbor is using. I often get, "Yah, but this is what I used in a past project." or "A buddy of mine used WordPress and he gets 10 million hits a day!" Getting them to pay $299 for a commercial license for EE seems like a really steep cost when they could just get WordPress for free and it's "good enough."
I couldn't agree more. In fact, this is why I started building a project for my girlfriend so she could create her own site. And now it's grown into something powerful that I really enjoy using too.<p><a href="http://simplpost.com/blog/what-is-this-thing/" rel="nofollow">http://simplpost.com/blog/what-is-this-thing/</a>
The first comment on the article is by Jason Schuller, who created a great little open source blogging platform called Dropplets (<a href="http://dropplets.com/" rel="nofollow">http://dropplets.com/</a>).<p>I use it myself and it's fantastic. Simple and elegant and I feel in control of my blog now- there's no magic.
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.<p>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.<p>Recently I've started looking for another server-side platform. I've been getting annoyed with the extra work involved with static site generators, especially for a rather trivial "look what I saw" blog. I installed Anchor [1] last night, and plan on playing with it. I'm also interested in Ghost, but it hasn't been publicly released so far as I know.<p>[1]: Anchor CMS: <a href="http://anchorcms.com" rel="nofollow">http://anchorcms.com</a>
> Some sites are blogs, others are small business web sites, others are photo galleries, others are one pagers of information, and some are pages that let you buy things. There shouldn't just be one tool to build all of these.<p>I find that above text a bit odd. Maybe I'm misinterpretting it, but why exactly shouldn't there be one tool to build all of those websites? It might very well be that Wordpress is not suited to build all those things, but it doesn't follow logically that there should not be a "mastertool", no matter what.<p>I understand the general sentiment of "horses for courses", but I also think that it's important to make sure that your tools are performing well, rather than trying to make a blanket statement about what web dev tools should and shouldn't do in general.
If you're into simple, hosted services, you might give <a href="http://www.postagon.com" rel="nofollow">http://www.postagon.com</a> a try.
Incidentally I just released my me-too static generator. It's targeted for academics, with all the features an academic expects (hyphenation, LaTeX math support and so on). If anyone's interested: <a href="https://github.com/lrem/phdoc" rel="nofollow">https://github.com/lrem/phdoc</a>
I point complete novices to <a href="http://www.weebly.com/" rel="nofollow">http://www.weebly.com/</a>.<p>It has a gui site builder (wysiwyg) and what not, and is considerably simpler than wordpress.<p>What does barley have over weebly?<p>Can I download barley and install on my servers like I can with wordpress? If not, this is apples and oranges.
You should try out Silvrback (<a href="https://dsowers.silvrback.com/introducing-silvrback" rel="nofollow">https://dsowers.silvrback.com/introducing-silvrback</a>). It's a hosted, markdown powered blog as clean as medium.
The only differentiator that I see you offering is inline editing, which can be activated very quickly with a Wordpress plug-in.<p>I think you're traveling down a meat grinder of a road by choosing to spend time on this.