Continuous integration and Wordpress development

[Hung, Jonathan]

Hi everyone,


We've been designing, developing, and deploying more and more Wordpress sites for various IDRC projects. Many of these sites are using two common components:


  *   Floe UI Options Wordpress Plugin<https://github.com/fluid-project/uio-wordpress-plugin>
  *   Floe wp-a11y theme <https://github.com/jhung/wp-a11y-theme/tree/foundation> (in development)

Since many of these production sites are using their own customizations on the wp-a11y theme, there needs to be a good way to propagate changes to the wp-a11y theme to these sites without affecting the customizations.

Approach 1: Core features + Continuous Integration

A possible approach to this would be to create a standard WP configuration with the following features:


  *
  *   UIO Plugin + Continuous Integration configured to get changes from github
  *   wp-a11y theme configured to get changes from github
  *   a wp-a11y child theme stub for the customizations
  *   documentation explaining how child theme development would work

This would give us the ability to push changes to the UIO Plugin and the wp-a11y theme without clobbering any changes (assuming the site authors did not directly edit the theme files).

Approach 2: Register with Wordpress.org

Another approach is to register both the UIO Plugin and the wp-a11y theme with Wordpress.org and have changes pushed out using the WP update process. Ultimately I think this would be ideal for end users outside of the IDRC, but the wp-a11y theme has a way to go before it's ready.


Does anyone have any thoughts on how we might do this? Does Approach #1 seem reasonable?

- Jon.


---
Jonathan Hung, Inclusive Designer
Email: jhung at ocadu.ca
OCAD University
Inclusive Design Research Centre

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170710/c1454edc/attachment.html>