Tag: Envato (Page 6 of 17)

For those who have been in web development for sometime – especially those who have seen the rise (and stuck with) jQuery – then you’re likely all too familiar with some of the potential errors messages that you may see when working with the library.

But if you’re someone who is just starting out and perhaps you’re learning JavaScript and/or jQuery and you’re getting familiar with the developer tools that ship with your browser of choice, you’ve got your plate full of things that you’re having to debug.

And sure, Google is your friend and being able to ask questions on sites such as Stack Overflow and other similar sites is nice (though the community may not always be such), but it’s not always fruitful.

In those cases, I think those of us who have gone down the same road that you’re traveling have some obligation to help educate what the problem is, why it’s happening, and how to resolve it.

And that’s what I’ve tried to to do in my most recent article for Envato.

Continue reading

Comments are closed on this post. Please leave your comments on the original article.

For those who are just getting started in WordPress development, one of the more challenging aspects of working with some of the extended APIs is that of WordPress taxonomies.

Perhaps it’s because the term is one that’s not often used, perhaps it’s because it’s something that’s a little difficult to understand; however, whatever the case, I’m aiming to try to simplify the topic in my latest series on Tuts+.

Continue reading

Comments are closed on this post. Please leave your comments on the original article.

I don’t know if there’s ever been a time in WordPress-history where we’ve had such a plethora of options from which to choose as it relates to WordPress frameworks.

We have anything from drag-and-drop page builders to code-level abstractions that aim to make it easier to work with a variety of APIs.

But is using a framework always the best idea? Maybe. In my latest article on Envato, I weigh one of the pros and cons of using WordPress Frameworks in order to help determine if this is something that you may want to use or not.

Continue reading

The comments on this post are closed. Please leave your feedback on each of the respective articles.

When it comes to enhancing the functionality of the CMS, WordPress meta boxes are one of the most flexible features that we can introduce to the post editor screen.

In short, they’re a way that we can open additional fields to one, some, or all of the existing post types as well as custom post types. They also make it possible to introduce a number of different type of elements – be it input fields, textareas, checkboxes, etc. – so that users can easily view, add, and/or modify data associated with a given post.

When it comes to writing meta boxes, especially those that are more elaborate than others, it can become a bit of chore to maintain the code over time. But it doesn’t have to be that way.

Continue reading

The comments on this post are closed. Please leave your feedback on each of the respective articles.

Regardless of the type of software that you build either for a living, for a hobby, or for both, one of the most challenging aspects of the field is trying to write maintainable code.

That is, code that’s organized, follows a standard, is easily read, and adapts to change over time as the environment and requirements of the overall software changes.

It’s not an easy task and people far, far more experienced than I am are still talking about how to do it.

Still, that doesn’t mean that those of us who have been working in WordPress for some time haven’t learned some strategies for works, what doesn’t, and what’s proved to be maintainable WordPress code throughout the years of development.

Continue reading