As a university student, part-time freelancer, and occasional blogger who also has other hobbies, keeping up with news and content about any one topic – WordPress included – can be a daunting prospect. In a lot of cases – again, WordPress included – news aggregators can gather and list items of note. For a busy person, this can simplify finding new content.
In the case of WordPress, there are a number of hubs on the web that produce and/or centralize news and other content. Some of these go back quite some time, while others are relatively recent. Over time, some sites have come and gone, or just become less active, or essentially started over.
Some current well-known sites in this vein are Post Status, WordPress Tavern, A Better Planet, and Torque. I follow these, and more, and they do well at listing content of note. What they don’t do is indicate the noteworthiness of freshly listed content, as seen by the community. This is a visible aspect of sites such as Reddit and Hacker News, with commenting and voting on content.
Until now, there has been something of a void in WordPress content aggregation with community voting on the noteworthiness of said content. ManageWP have stepped into that void with their new site, ManageWP.org. (more…)
A common fixture on websites is a contact page, which provides the means for visitors to send a message to the site owner or administrator, whether a question, comment, compliment… or complaint, as the case may be. The simplest way to do this is by creating a
mailto hyperlink with the destination email address, but this leads to at least two problems:
- the user experience is marred by having to open a mail client, paste the address and type a message, or clicking on the link, having the mail client appear, and typing a message.
- an email address embedded into a page’s markup becomes a target for email harvesters, which trawl the web looking for unprotected email addresses that they can then spam.
There are technical solutions to avoid the email harvesters, but this still leaves the user experience issue on the table. Fortunately, there is another option which addresses both issues: contact forms. (more…)
A previous post on template partials showed how to componentize a theme by breaking out reusable blocks of code into discrete files, and consume them via the
get_template_part() function. This has the potential to lead to numerous “extra” files located in the theme root folder beyond the standard theme files. WordPress offers the option to organize template files into subdirectories; this post will continue the example in the previous post and show how to make use of this functionality. (more…)
It used to be that WordPress theme templates were monolithic beasts, with a fair bit of looping and conditional logic to display content in a certain way. I know, I’ve done it too. In past years, this has been helped somewhat with the availability of content-type-specific template files, such as page.php, attachment.php, and so on. This helped to reduce the monolithic aspect of, say, index.php and single.php. However, the result was repeated code across multiple files (almost even a multitude). Repeated and redundant code should make any coder cringe. Well, there is a further step to take with the use of a little function called get_template_part(). (more…)