Tag: WordPress (Page 160 of 219)

Over the last few posts, I’ve been sharing my thoughts on the WordPress Philosophy and how I generally think that many of us who build things for WordPress are ignoring the philosophy that drives the application for which we build.

So far, I’ve talked about how I think we do a bad job of making sure everything works out of the box, and I’ve also talked about how we do a better job at designing for our peers than we do designing for the majority.

If you’re not aware of anything that I’m talking about, then make sure to read the WordPress Philosophy and it will bring you up to speed as to exactly what these posts are all about.

With that said: The third point, Decisions, Not Options, is arguably my favorite point in the philosophy, but it’s the one that we’ve trashed the most.

And that’s a sad thing because I think that if we’d paid more attention to it, then we wouldn’t have so many of the complaints about so many different themes, vendors, marketplaces, and so on as we do today.

Continue reading

Earlier this week, I shared my thoughts on how I believe that many of us who are participating in the WordPress economy are practically ignoring the WordPress philosophy.

There are a number of different pillars on which this philosophy sits, the first of which is Out of the Box. But there are more each of which I want to share my thoughts on as it relates to building themes an other things for WordPress.

If you’re unfamiliar with what I’m talking about, then be sure to check out the WordPress Philosophy first; otherwise, much of this likely won’t make sense.

With that said, on to the second point: Design for the Majority.

Continue reading

If you head over to the WordPress.org homepage and click on the About link, you’ll be taken to a page that, y’know, tells what WordPress.org is all about, what the software can be used for, some history, and so on.

Then, there are also links to various WordPress-related collateral such as logos and graphics, fan art, the GPL, the project roadmap, and the philosophy.

Wait, what? A philosophy?

Exactly. WordPress – a piece of software – has a philosophy. It’s a really, really neat page that I think everyone who is involved with WordPress – be it designers, developers, or users – should read. It’s not technical, it’s easy to understand, and it helps inform us what the software is all about.

As far as developers are concerned, there are a number of things in the philosophy that I believe we give excellent lip service, but we don’t actually practice, abide, or behave in such a way that we support the philosophy.

That’s a longer post for another time.

Anyway, though there’s a number of things in the philosophy that could be discussed (and probably ultimately will be :), one of the many things that we’ve forsaken is the “out of the box” philosophy.

Continue reading

For those developers who are coming to WordPress from other platforms such as .NET or other major database driven system where they are responsible for devising their own database schema, one of the problems that’s often seen in the WordPress-world is this desire to create sets of tables that may or may not interface with the existing WordPress tables.

Just as it takes time to learn the WordPress event-driven paradigm from, say, Model-View-Controller, or something else, it takes time to make sure you fully grok the stack on which you’re working.

And starting at the foundation of WordPress is the underlying database schema.

Continue reading