WordPress 5.0 is a significant step in this direction and the changes WordPress introduces with the new version will provide many benefits to non-techies and non-coders in the future.
This comprehensive guide, then, is aimed at helping non-technical users understand where WordPress is going, why WordPress has introduced these changes, and what these changes will mean to you. This section contains links to in-depth tutorials that will help you understand and apply these new changes to your website and the way you create content online.
WordPress 5.0 – Why
As discussed in ‘Non-Techies Are The Future Of WordPress: WordPress Gutenberg & The WordPress Paradox’ if you are a non-technical person working in a business where everyone else is also a non-techie, non-coder, non-web developer, or non-digital marketing expert and your business wants a web platform that can deliver better results, then your best option is to choose a technology platform where things are made so simple, automated and easy to use that you don’t even need to understand how the technology works to get the results you want.
As a non-technical user who has been observing the evolution of WordPress for over a decade, this seems to be the direction they are heading, and WordPress 5.0 is the first step toward this destination.
The introduction of the new WordPress content editor, called Gutenberg (after Johannes Gutenberg, who invented the printing press over 500 years ago) is part of a plan to transform WordPress into something bigger than just a website publishing and content management platform.
As the video presentation below recorded at a WordCamp held in Nashville, U.S.A. in 2017 (and its mission to democratize publishing) shows, WordPress is moving toward being a platform where non-technical users will be able to transform their web presence into just about anything they want using modular elements and components that will:
Provide users with all different types of functions
Integrate seamlessly with what you already have built
Be simple to configure, using methods like ‘point and click’, ‘drag and drop’, WYSIWYG (what you see is what you get), selecting options from drop-down menus, etc.
(Gutenberg and the WordPress of Tomorrow)
While the decision to introduce a completely new content editor generated heated debates and strong reactions from many users, web developers, and members of the WordPress community, it seems that WordPress had to make a decision if it is to continue to grow and evolve.
WordPress 5.0 and the new Gutenberg editor, then, is just the first step toward the bigger picture.
WordPress 5.0 -What’s New
To learn what’s new in WordPress 5.0 and what you need to do if you haven’t upgraded yet, go here.
WordPress Gutenberg Tutorials
To learn more about using the new WordPress content editor, click on the links below:
Widgets are one of the main basic buiding blocks of WordPress and one of its most powerful and versatile features …
WordPress Widgets – A Practical Guide For Non-Techies
Widgets are one of the main basic buiding blocks of WordPress and one of its most powerful and versatile features.
This section provides detailed step-by-step tutorials for non-techies that explain what widgets are and provide practical examples of using widgets to enhance your website, display different types of content, add new functionality to your header and footer sections, sidebar menus, and much more!
Click on one of the tutorials below to get started:
Learn how to use and configure WordPress widgets on your sidebar. This tutorial explains the basic concepts of using Widgets to extend the functionality of your website and provides an overview of the Widgets area ... Read More
Learn how to add and configure various useful WordPress widgets on your sidebar and how to create custom sidebar widgets ... Read More
"I love the way your email series "Infinite Web Content Creation Training Series" is documented and presented. It is very absorbing and captivating. The links and tutorials are interesting and educational. This has motivated me to rewrite my content following the concepts I am learning from the email series." - Mani Raju, www.fortuneinewaste.com
Although these folders and files are mostly accessed by technical users like website developers, it’s good to know what these folders and files are used for, especially if you plan to build or manage your own WordPress site.
(WordPress installation files)
You can view these folders and files using an FTP application or cPanel’s File Manager. For help with this, see the tutorial below:
WordPress Installation Files: A Glossary For Non-Techies
Your WordPress site is made up of your WordPress installation files and your WordPress database. These are responsible for creating, storing, and managing all of your site’s information, web pages, etc.
Below is a glossary of WordPress installation files for non-techies. The glossary includes non-technical explanations and descriptions with links to related tutorials.
If you need more technical information about the folders or files below, please refer to the official WordPress documentation here:
This file contains useful pre-installation information about WordPress …
(WordPress ReadMe file)
This file confirms that the activation key sent in an email after a user signs up for a new site matches the key for that user and then displays confirmation.
This file decides what to display based on the parameters that are passed to the blog from any page that wants to display WordPress content and loads the WordPress environment and template.
This file receives posted comments and adds them to the WordPress database. It also prevents duplicate comment posting.
This is a sample of the wp-config.php file used to connect WordPress to your MySQL database. You can use this sample file to manually create the wp-config.php file (see below).
The wp-config.php file is one of your most important WordPress installation files. The wp-config.php file is located in the root of your WordPress file directory and contains your website’s base configuration details, such as your database connection information (e.g. Database Name, Database Username, Database Password, Database Host, etc.)
Here is some useful information about wp-config.php file:
The wp-config.php file isn’t included in the WordPress download files. It is created during the WordPress setup process based either on the information you provide during the manual installation process, or automatically, if you use a WordPress installation script (e.g. Softaculous, Fantastico, etc.)
A wp-config.php file can be created manually by editing the sample file (“wp-config-sample.php”), resaving it as wp-config.php and uploading this file to the root install directory.
The content of the wp-config.php file follow a specific order. Rearranging the order of this content may create errors on your website.
Editing WordPress files like wp-config.php should always be done using a plain text editor. Never use a word processor like Microsoft Word or Google Docs to edit WordPress files.
Many important modifications to WordPress can be done manually by adding lines of code to the wp-config.php file. Some of the features and functionality affected by the wp-config.php file, for example, include:
Debugging WordPress (troubleshooting errors and making repairs)
Allowing WordPress users to optimize and repair the WordPress database
And so much more …
A CRON job is essentially an automated scheduled task. It’s like someone programming a robot to do XYZ at a specific time. If someone asks the robot “is it time to do XYZ yet?” the robot can then either say “no, it’s not time yet” or “yes, it’s time” and then automatically perform the task.
By default, WordPress calls up wp-cron.php whenever someone visits your WordPress site and a scheduled task is present. Also, web hosts normally offer CRON. The wp-cron.php file provides a CRON function for hosts that do not offer CRON or where a CRON job has not been set up by software installed on your site.
The wp-cron.php file is used to perform virtual cron jobs (i.e. scheduled tasks) to automate things like publish scheduled posts, check for plugin or theme updates, send email notifications, etc.
This file converts links added to your site via the WordPress admin menu into a format called OPML (Outline Processor Markup Language).
OPML allows outlines and lists to be exchanged between different platforms, such as exchanging lists of RSS feeds between different feed aggregators.
Essentially, this file allows links to be exported from one WordPress site to another.
In computing terms, bootstrapping is a technique for loading a program by means of a few initial instructions which then enable the rest of the program to be loaded from somewhere else.
The wp-load.php file is a bootstrap file that loads the wp-config.php file. The wp-config.php file then loads the wp-settings.php file, which then sets up the WordPress environment.
WordPress uses this file to obtain blog posts submitted via email. The URL of this file is usually added to a CRON job so that it is regularly retrieved, enabling new email posts to be accepted.
This file performs various pre-execution routines and procedures, including checking for correct installation, including auxiliary functions, applying user plugins, initializing execution timers, etc.
WordPress uses this file to set up the area where users can sign up to your website or blog.
This file handles incoming trackback requests to WordPress.
This file provides XML-RPC protocol support for WordPress. This allows you to do things like post content to your site using programs and applications other than the built-in web-based administrative interface and for WordPress developers to extend WordPress functionality using plugins.
The additional files below aren’t part of the default WordPress installation but may be found in your server’s WordPress directory:
A php.ini file is the default file for configuring and running applications that require PHP. The server looks for this file when PHP starts up for instructions on how to control variables such as upload sizes, file timeouts, and resource limits.
Server & Webhosting
Below are some useful terms to know when installing WordPress on your server:
DKIM (DomainKeys Identified Email) lets a domain associate its name with an email message by affixing a digital signature to it.
Verification is carried out using the signer’s public key published in the DNS. A valid signature guarantees that some parts of the email (possibly including attachments) have not been modified since the signature was affixed.
Usually, DKIM signatures are not visible to end-users, and are affixed or verified by the infrastructure rather than message’s authors and recipients.
SPF (Sender Policy Framework) is an email validation protocol designed to detect and block email spoofing by providing a mechanism to allow receiving mail exchangers to verify that incoming mail from a domain comes from an IP Address authorized by that domain’s administrators.
The list of authorized sending hosts and IP addresses for a domain is published in the Domain Name System (DNS) records for that domain in the form of a specially formatted TXT record. Email spam and phishing often use forged “from” addresses and domains, so publishing and checking SPF records is considered to be one of the most reliable and simple to use anti-spam techniques.