This is an incomplete list of resources including courses and individuals who publish content that has helped me grow as a web developer and designer. Many of these resources are WordPress-specific as that is my current area of specialization. This list will grow over time. If you've got something to add, send me a link @kevinwhoffman and I'll check it out!
React Fiber is an ongoing reimplementation of React's core algorithm. It is the culmination of over two years of research by the React team.
var gulp = require('gulp'), | |
gutil = require('gulp-util'), | |
coffee = require('gulp-coffee'), | |
coffeeify = require('gulp-coffeeify'), | |
concat = require('gulp-concat'), | |
uglify = require('gulp-uglify'), | |
sass = require('gulp-sass'), | |
test = require('gulp-if'), | |
del = require('del'), | |
rename = require('gulp-rename'), |
Its a New year, and a new focus for shortcake. We met today on #feature-shortcode to catch up on feedback from the community summit and WordCampUS, as well as to chat about whats up next.
General feedback is that people are interested in what we’ve done, but there was some concern about how we’re storing data, as well as the general UI and how it is coupled with the media library and TinyMCE.
The technical limitations of the current Shortcode API are something we’ve run into. There have been a number of proposed solutions; from a new syntax, to storing structured data in post meta or as a custom post type. However the purpose of Shortcake has always been to make these decisions less critical. The biggest challenge for us right now is to come up with a really great interface and user experience.
For 2016, we’re decided to focus on creating a great way to manage complex blocks of content, implemented using shortcodes.
<?php | |
/* | |
* Dependent Plugin Activation/Deactivation | |
* | |
* Sources: | |
* 1. https://pippinsplugins.com/checking-dependent-plugin-active/ | |
* 2. http://10up.com/blog/2012/wordpress-plug-in-self-deactivation/ | |
* | |
*/ | |
<?php | |
/** | |
* | |
* This script will copy your wordpress from public_html (or wherever) | |
* and place it in a staging folder. | |
* It will then clone the database, reconfigure the config file | |
* and replace URL's from the original URL to your staging URL. | |
* It will then make sure to NOT allow search engines to index the page. | |
* | |
* Use this script to clone your main wp in order to test maintenance work |
/* | |
* Migrating your DB with Migrate DB Pro | |
* your "Disable Search Engines" setting | |
* can get pushed to your live site | |
* This is how you can automate that | |
* Ref: https://deliciousbrains.com/tweaking-wp-migrate-db-pro-actions-filters/ | |
* AWP Link: https://www.facebook.com/groups/advancedwp/permalink/951660888229459/ | |
* Care of Chris Perryman www.revelationconcept.com | |
*/ |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
<?php | |
/** | |
* This changes logging to only log fatal errors. This file should go in your mu-plugins directory. | |
*/ | |
// Set the error logging to only log fatal errors | |
error_reporting( E_ERROR ); | |
// Optional: change the location of your error log, it might be wise to put it outside your WP content dir. | |
// If you don't change it, the default place for this log is debug.log in your WP_CONTENT_DIR. |
This gist is to accompany my comment on Mark's article:
[Build modular content systems in WordPress] (http://www.creativebloq.com/web-design/build-modular-content-systems-wordpress-41514680) by Mark Llobrera
Which if you haven't read (or just stumbled upon this gist by chance) then I highly recomend you do.
It demonstrates some key concepts on how you can use ACF to build your clients mini page builders. By doing so you can avoid all the bloat that the big page builder type plugins use. You will also build up your own mini library of elements that you can reuse depending on the project.