Here are some possible topics that I would be happy to do a customized WordPress training on:
- Strategies for leveraging WordPress within your organization
- Strategies for WordPress content development within your organization
- Strategies for building community within your organization using WordPress
- How to create a WordPress theme from a PSD file
- How to make basic edits to a WordPress theme
- Creating custom page templates in WordPress
- Creating custom loops in WordPress
- How to add functionality using functions.php
- How to build a plugin
- How to Install WordPress
- How to run and test WordPress locally
- How to edit CSS
- What do all these files mean?
- Intro to PHP
- Intro to CSS
- Intro to HTML
- Intro to javaScript
- How to create an accordion effect
- How to create X effect
- HTML 5 primer
- How to use jQuery
- How to build and customize a slideshow
- How to edit the home page to create a “News” theme
- Intro to WordPress Multi-site
- Intro to BuddyPress
- Advanced WordPress Multi-site
- Advanced BuddyPress
What would you like to learn?
More posts from themightymo.com
How to auto-save Advanced Custom Fields (ACF) data to a file in your theme
With ACF 5, they shipped a relatively-unknown and awesome feature: The ability to have WordPress automatically-save your ACF fields to a json file in your theme folder every time you save your fields. This has the effect of: All you need to do is add a folder called, “acf-json”, to your theme folder, and it…
How to use $current_user or is_user_logged_in() with FacetWP and WordPress to show different content for logged-in users
I have a membership site where I need to display certain FacetWP results to people who are logged in and other FacetWP results to people who are logged out. Unfortunately, FacetWP forgets WordPress’ global $current_user variable the minute you use one of the facets. Same with WordPress’ is_user_logged_in() function – FacetWP forgets it all once…
How to shrink the size of wp_options table in WordPress
I was recently horrified to discover that the “wp_options” table of this site was over 1.3 gigabytes in size. For those of you counting at home – that is ENORMOUS and unnecessary. I was confused, because the table seemed to balloon overnight (and likely did balloon overnight, it turns out!). The issue was caused by…