A child theme of the standard WordPress Twenty Nineteen theme.
Our aims include:
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.
Minimize use of plugins, javascript, and other dependencies.
C4AA welcomes all contributions to the C4AA website.
- 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.
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
develop - Submit a Pull Request against the
developbranch 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.
developis the integration branch. Every push to it is built and synced to the staging site by GitHub Actions (.github/workflows/develop.yml).masteris production. Changes get there through a pull request fromdevelop, and every push to it is built and copied to the live site (.github/workflows/main.yml).- Both workflows install dependencies, run
npm run prod, then connect to the May First shell host and transfer the theme. Hosts, users, paths and keys live in the repository's Actions secrets and environments (StagingandProduction), not in the repo. build/is ignored by git on purpose. The workflows compile it on every deploy, so there is nothing to commit after a CSS or JS change beyond the source.
- 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.
- The theme expects Advanced Custom Fields PRO for its custom blocks (
blocks/) and fields (acf-json/). - Clone this repo into your wp-content/themes directory.
- Use the Node version in
.nvmrc, then runnpm cito install dependencies. npm run dev- Start the Sass and esbuild watchers; they compilesrc/cssandjs/intobuild/.npm run prod- One-off minified build, the same command the deploy workflows run.
functions.php- enqueues, ACF block registration, block editor setup and the smaller tweaks.src/css/- Sass sources.main.scssis the entry point.js/- small plain scripts bundled by esbuild intobuild/main.jsfor the front end (js/main.jsis the entry), pluseditor.jsfor the block editor.theme.json- palette, duotone presets, typography and block settings.blocks/- ACF blocks (person title, person email, promo image).template-parts/andfooter.php- the few parent theme templates this theme overrides.
- Lara Schenck @laras126
- Steve Lambert @slambert
- Zoraida @zoracreates
- CSS Duotone
- Work Sans
- Zilla Slab