The C4AA.org WordPress Theme

C4AA.org

A child theme of the standard WordPress Twenty Nineteen theme.

Our aims are:

1. Create a site that aligns with the Center for Artistic Activism Design Standards

We have some design standards created by Diane Shaw, then built upon over the years in our Center for Artistic Activism print material and by subsequent designers like Andy Outis.

2. Code as few modifications as possible.

Minimize use of plugins, javascript, and other dependencies. Hopefully avoid front-end plugins entirely.

Plugins we are using:

• Gutenberg - just to get upcoming features early.
• Akismet - we don't really use comments, but why not.
• Jetpack - we use downtime monitoring, brute force protection, carousel gallery, markdown, extra widgets, post via email, social network sharing, etc.
• Give - Donation Plugin - we use this to process and manage donations. We're subscribers and use some of their add-ons as well; Annual Receipts, Currency Switcher, Email Reports, Fee Recovery, Form Field Manager, MailChimp, Manual Donations, PDF Receipts, Recurring Donations, and Tributes.
• EWWW Image Optimizer - not everyone using the site knows how to optimize images or wants to bother with it.
• Advanced Custom Fields PRO
• Blubrry PowerPress - for our podcast
• Contact Form 7
• Post SMTP
• Comet Cache
• Login Lockdown
• Redirection
• Widgets Reloaded
• WP-Matomo for our Matomo stats install.

Contributing to this site

C4AA welcomes all contributions to the C4AA website.

Understanding Issues and Requests

• We use GitHub Issues to tracking problems, bugs and feature requests for the website. If you see something wrong with the site, or some change you think would be helpful, feel free to create an Issue and we'll review it.
• Issues marked with the "request" tag have been created by the site administrators and generally reference one or more Issues. These represent "tasks" or "actions" requested by the site administrators and are a great way to push the site forward and make things better. If "issues" represent a problem, "requests" represent a proposed solution that we'd like to see actioned.
• To make code contributions to the codebase, please follow the guidelines below.

Making code contributions

To participate, please follow asmeurer's Open Source Git Workflow.

To summarize briefly:

• Fork the repo
• Make your changes in your fork in a feature branch off of master
• Submit a Pull Request against the master branch of the C4AA.org repo
• Reference the Issue or Request that you're attempting to solve in the PR.
• All Pull Requests will be reviewed by site administrators and changes may be requested before a PR is accepted.

Local Development

• Download a recent copy of WordPress, as well as the TwentyNineteen theme and install them locally in a directory you're comfortable working in.
• Start a local environment and install base WordPress. We recommend Laravel Valet.
• Clone this repo into your wp-content/themes directory.
• Once the theme is cloned, run npm install to download dependencies.
• npm run dev - Start the Sass watcher for development.
• npm run prod – Minify CSS before opening a PR.

Credit:

• Lara Schenck @laras126
• Steve Lambert @slambert
• Zoraida @zoracreates
• CSS Duotone
• Roboto Slab
• Raleway Font from the League of Moveable Type