News for hackers. Stuff that matters.
Re:Wordless: stop writing Wordpress themes like it's 1998. by csomar on Wednesday December 07, 2011 @03:07PM (#3325673)
Cool. As someone doing heavy WordPress development (and will be doing even heavier dev. in the future) this is a step in the right direction.

The available tools for WordPress right now are just awful. I'm doing plugin development right now (but will get to themes in a couple of months); and in order to setup unit testing it took me a full 3 days.

When coding plug-ins, I noticed that I'm using awful and very old patterns (like mixing PHP with HTML). It's like I'm working on PHP when I was 15 years old. Checking a few WordPress plug-ins (popular and premium ones), it even proved to be worse: They were using procedural code and patterns. Huge and long code, a bunch of functions with long names binding to WordPress actions or filters.

Here are the improvements that I'm looking for (and working on):

1. Better Unit Testing: A better stack for Unit Testing.

2. Better debugging: Debugging is just a nightmare when doing WordPress development and your project (I'm using Netbeans) should point to your plug-in repository.

3. Developers plug-in: A plug-in to manage your WordPress install

4. Bootstrap plug-in: Administration interfaces (styles/tables/forms/buttons...)

EDIT: I just noticed that the following

  Include the assets in your Haml views using include_javascript() helper.

  = include_javascript("application")
  This will produce the following HTML, pointing to the assets/javascripts directory:

  <script src="/wp-content/themes/YOUR_THEME/assets/javascripts/application.js" type="text/javascript"></script>
This is a very bad practice. You should use WordPress functions to queue scripts and styles.

There are no comments on this comment yet.