I aim to help grow and support the WordPress community as a whole. Along with my code and plugin contributions to WordPress, I have also supported the WordPress Sheffield community group.
To cater to a wide verity of interests, the WordPress Sheffield format varies between speaker based ‘Mini conferences’, ‘Workshops’ and focussed code clinics, where I, along with other experts in attendance try to offer help and support to those who are having difficulty making their web applications and ideas into a reality.
This month, Make Do provided the free pizza and drinks, and our wonderful hosts Sheffield Hallam University provided us with the space, and we settled in for a code clinic, or should I say ‘Lean Clinic’.
Lean Coffee Clinic
At our non-speaker focused sessions, we really love the Lean Coffee format, as it lets us quickly get through lots of topics in one go, however we were really keen to see why our attendees were at WordPress Sheffield, and what specific issues they had, so we transformed the session into a ‘Lean Clinic’.
The basic format of a the session was:
- Give everybody time to write down an one or more topics that they would like to discuss (including specific issues) on post-it notes.
- Read out each issue and let the room take a vote on which ones we should cover
- Order the issues by vote number (higher votes will get talked about first, lower ones may get missed if we run out of time)
- Allow 5 minutes discussion of each issue, with a group vote of whether we should continue for another 5 minutes at the end of the allotted time period (repeat until the topic is exhausted).
Some WordPress Sheffield Attendees sharing their WordPress Issues.
Clinic Topics this Month
Here are the topics that were discussed in the clinic, and the answers and solutions that were given:
- What is Node.js?
- Does Top Level Domain (TLD) Matter in Search Engine Optimisation (SEO)?
- Why do Emails sent from my WordPress Website get Spam Blocked?
- What is the difference between WordPress.com and WordPress.org, and can I Monetise WordPress.com?
- Can WordPress be used as a Workflow Application, with Readership Restrictions based on Status?
- How can I Exclude the Last Viewed Post from my Post Category Archive?
- How Can I Consume External REST API’s with WordPress?
- How can I use Custom Image Sizes in my WordPress theme?
- Should I develop Widgets, Meta Boxes or the Customizer for my Client Projects?
A good case study of this type of development is the ustwo website (the team behind the popular Monument Valley game).
According to Google themselves, TLDs do not affect search rankings, however debate was had, and there is some anecdotal evidence behind the fact that if a domain that has been established for longer (e.g. it is a .com or a .net, not a .agency) it would have a better ranking.
Ultimately though, it comes down to content. A .com domain with very poor content would rank less than the equivalent .io domain with fantastic content and structure.
There could be multiple factors to this issue.
One factor could be that the
wp_mail function in WordPress which sends email via PHP (passing the mail off to the built in SMTP server on the host), by default does not include all the necessary headers that SMTP requires to send authenticated email.
Another factor could be that if you buy shared hosting from a hosting company, or if you host WordPress on your own servers, your servers IP may be on a blacklist due to previous abuse, or you it may be sending from a Dynamic IP, and or not be considered a ‘trusted’ mail server.
To remedy this you could look at SMTP plugins to route the email through a trusted server. For larger sites plugins such as SendGrid will route emails to their trusted servers, and give you status updates for each email, so you can see exactly where it was blocked (if at all).
What is the difference between WordPress.com and WordPress.org, and can I Monetise WordPress.com?
This is our favourite question at our WordPress clinics, as understandably it does cause some confusion for those new to the platform.
In simple terms, WordPress.org is the self-hosted version of WordPress which you can extend however you see fit, whereas WordPress.com provides hosted version of WordPress that is managed externally, and has fewer options in terms of themes and plugins.
If you are new to WordPress we recommend trying out WordPress.com, and if your website needs grow beyond what .com can offer, then there are loads of hosts out there that offer a simply way to setup a WordPress.org instance of WordPress at your custom domain. It is important to note that you can extract your data from WordPress.org at any point.
For more in-depth reading, checkout this great blog post from WordPress.com on the subject of .com vs .org.
If you run your own WordPress.org based website, the monetisation options available to you are limitless. You can use one of the many affiliate plugins available on the Plugin repo, or even install your own custom advertising plugin.
On WordPress.com you still have the ability to manually add affiliate links to your blog posts, but you are not able to implement advertisements such as those provided by Google AdSense. You can however use the official WordAds platform to place adverts from these providers on your website.
The question specifically was about data being sent publicly from web forms, which were turned into posts that had certain areas of them not editable based on what part of the workflow they had been through.
The answer to this is of course yes, with some custom development to match the exact requirements, however plugins such as GravityFlow and PublishPress may be a good step in the right direction to achieve what you need to do with less custom development.
If you are viewing a post that resides within a WordPress category, and you offer a link to the Post Category Archive, so that the visitor can view more posts in that category, how do you exclude the last post that was viewed from appearing in that list?
There are multiple answers to this question, and it all depends on what the data is, and what you want to do with data. Some of the options available are:
- Write a plugin to pull the external data into posts (custom or otherwise), that you can then handle and render in the usual way through the use of a WordPress theme.
- Use PHP to pull the data into the theme on the server, and render it into a theme.
Many themes have additional sizes built into them, but if this is not enough, with some custom development you can use the
add_image_size() function to add multiple image sizes to your WordPress theme.
There are also plugins available that let you add custom image sizes to your site, such as the Simple Image sizes plugin.
With regards to images within a gallery, custom development will give you exactly what you need, but many WordPress plugins, including JetPack with give you a great gallery with lots of configurable options.
As with many of the answers given at the WordPress clinic, the answer depends on you and/or your clients specific needs.
Between us we came up with the following use case for each:
This is the most visually pleasing option for the client, however this should mainly be used for global site options, and visual changes. Per post changes are possible, but these are likely to be done at the same time as the post is written, so meta boxes may be more suitable for that.
Don’t forget that widgets can be managed via the customizer, so a widget approach will also tie into this approach.
The future of the customizer is bright, and it may one day fully replace the default editor, to allow visual editing of website data.
Meta boxes sit right alongside the default WordPress post editor, and hold specific information about the post that is being written / edited. This is currently the best way to add post specific information.
Widgets can sit anywhere in the website where there is a registered widget area. The information within them is not usually tied to a specific post, and they can be added, removed and deleted by the your website administrators.
If widgets are used we recommend that the following steps are taken:
- Certain widget areas should be restricted, so only certain widgets can be added to them (so layout doesn’t break)
- All widgets have styles applied to them so they are in-keeping with the look and feel of the site (with special attention being given to widgets that come packaged with plugins)
- Widgets that will not be used on the website are unregistered
- Widget areas have appropriate styles / logic, so they do not look out of place if they contain no widgets
Widgets are the easiest way for a customer to break a design you have supplied for them, so use them with care.
While we are listing out ways that allow your clients to add data to a site, an honourable mention should go to the site builders. These are the most flexible approach for a client with good design skills is a site builder such as Site Origin or Beaver Builder.
Why Not Join a WordPress Community Meetup in Your Area?
If you would like to get involved in WordPress community events, or even start one of your own, check out the Make WordPress Community section of WordPress.org.