‘A-Z of WordPress’ with Nathan Wrigley and David Waumsley
Hello, This is another A-Z of WordPress where we attempt to cover all the major aspects to building and maintaining sites with WP. Today is K for… Killer Tips
We are cheating with this, but it has been a while since our chats have featured the thoughts of the WP Builds Facebook group. Interestingly I looked at a few articles on top WP tips and I think our group covers all the major one mentioned elsewhere and more so yay us!
When you upload a plugin that is already installed, WordPress lets you compare the versions and choose what to do.
Uncheck the “discourage search engines” settings.
Since WordPress 5.2 you can’t see the errors when you’re developing, or make mistakes when editing your functions.php.
To counter that David almost immediately turns on WP_DEBUG, but also WP_DISABLE_FATAL_ERROR_HANDLER by setting the constants in wp-config.php
David’s notes. One of my tips would be to concentrate on image file sizes. There is a trend at the moment on speed testing themes and page builders. The fast themes may only be loading 50kb less than the slowest. Optimise your images and you may lose 10 times that!
Use a Starter Site – time saving.
Self plug for Admin Page Spider! Basically worth having a look around for WordPress navigation tools (David uses Beaver Builder’s Assistant)
David’s notes. Good to get client on the same page. http://www.5minutemarketingmakeover.com/video-1/ (Story Brand Donald Miller) and https://www.youtube.com/watch?v=6YtrieuSlhY (Watertight Marketing Bryony Thomas)
Business and clients
Have a lean stack, and master what you have.
Never assume what the client says means what you think it means… Always really dig into the details of “expected behavior”.
https://wordpress.org/plugins/simple-history/ (this one makes sense when we talk about clients)
Sincere thanks to all of you who took part and submitted your thoughts, this was the easiest way to make a podcast, so we’ll be getting you guys to do all the work again at some point in the near future!
This content was originally published here.