Tag: WordPress (Page 160 of 219)

Articles, tips, and resources for WordPress-based development.

We’re Ignoring the WordPress Philosophy: Design for the Majority

June 25, 2014 / Tom / 0 Comments

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.

The Ultimate Goals of the Pressware Shop

June 24, 2014 / Tom / 0 Comments

About a month ago, I talked about some of the projects that were in the Pressware Pipeline two of which included the following:

Mayer
“The Pressware eCommerce Gateway,” my choice of words (not as elegant as they should’ve been I suppose :).

As of today, these two projects are officially launched and I couldn’t be more excited. That is, Mayer is now available for self-hosted installations, and The Pressware Shop is now open.

We’re Ignoring the WordPress Philosophy: Out of the Box

June 23, 2014 / Tom / 0 Comments

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.

About WordPress.org

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.

Change the WordPress Database Schema?

June 19, 2014 / Tom / 0 Comments

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.

Including a Template in a WordPress Plugin (Well, a Template Part)

June 18, 2014 / Tom / 0 Comments

Late last year, I wrote a post that provided a way on how to include a page template in a WordPress plugin. There’s an accompanying project on GitHub that’s been maintained and relatively-well updated since.

Although this post is similar in nature, it doesn’t exactly deal with templates, but parts of code that may be considered partials (or template parts, in WordPress).

Let’s say that you’ve got a single post and you want to append a template to the end of the content. The content can be a little more complicated that markup because that’s easy enough to do inline, isn’t it?

So, for all intents and purposes, let’s say that we have a partial that includes a form that can be used to submit some type of information.