This is something I’ve been doing for a while now, and it’s something that I’ve found useful both for my personal and professional life.
And I don’t want to try to come up with some other reason for doing this so I’ll quote my previous post (because quoting yourself isn’t narcissistic or anything, is it?):
Every time I end up taking time off of social media in general, I never regret it. At the same time, I also find new things I want to do during that time.
But one of the things I like do during this post other than share that I am doing it (because I see this site as the primary place to keep up with me – not Twitter, not Instagram, not AIM, not ICQ), I like also to cover what I plan to do.
It’s one thing to be using PHP CodeSniffer manually but if you’re using a utility such as GrumPHP to check your work before committing it to the repository, then you’re likely going to want to use the version that you’re installing with your project.
This assumes that:
You are installing PHP CodeSniffer local to your project,
You want to install a specific set of coding standards to run against your code.
Remember, this is also done in the context of wanting to run automated scripts during the commit process and in a local environment (versus a global setting) with Composer.
This post is brought to you by Meta Box and the work they are doing to make working with custom meta boxes easier for all WordPress Users.
A FAQs page, as many of you know is short for Frequently Asked Questions, is a commonly used page to provide quick answers about a product or service. They’re common to us all, but it’s important to note the role they play when establishing a relationship with the customer.
Furthermore, if you run a site built on WordPress, you may also find it helpful to know how to build a custom FAQ template, as well.
In this post, we will share an easy way to create a FAQs page in WordPress by using the Meta Box plugin.