Where should I store this data? A custom post type? Taxonomy? Custom Table? WordPress has a few different built-in mechanisms that allow you to store custom data, each with their strengths and weaknesses. The question is, which one should I use?
Having a well-designed data structure is crucial to a project’s long-term success. It acts as the foundation of your project, and if not well thought out, could lead to massive technical debt, and costly migrations down the road.
In this talk, we will walk through a few specific examples of project requirements, and the thought process involved when deciding how to architect the data to fulfill the requirements.
We explain what the WCAG 2.1 guidelines are and why they are so important to us as WordPress developers and agencies.
Then we offer our easy and actionable steps that you can do to your website as soon as you get home to help you become compliant.
We of course go through and explain each step we offer so you will understand clearly.
Finally, we offer some resources and links to completely free plugins that you can use to test your websites Section 508 compliance and help your compliance instantly.
If you’ve ever wanted to build your own plugin for WordPress, this is the session for you. We’re going to start from scratch and work our way up.
First, we’ll take a look at the basic requirements of a plugin. Next we’ll take our example plugin idea and break it into the various components and steps that we’ll need. We’ll code up the plugin together and install it on our sites, debugging any problems that arise. Finally, we’ll look at ways that we could further extend our plugin.
This tutorial assumes some HTML and CSS knowledge, but you don’t already need to be familiar with writing PHP or JavaScript.
The steps that we’ll work through include: – Setting up a folder and PHP file for our plugin – The plugin file header and what it does – Creating a README file – Adding a menu item and sub-menu item in the dashboard for our plugin settings – Creating a plugin settings page, settings sections, and individual settings with the Settings API – Using WordPress hooks to enqueue scripts and styles, and display output for the user – Moving our plugin settings into the WordPress Customizer – Preparing our plugin for translation and future updates
