I did significant work for AudioVerse building a WordPress plugin which reproduced the functionality of their existing website. Goals were to make the website easier to update for their non-technical staff and to eventually take advantage of PWA browser APIs to reduce their reliance on maintaining separate mobile apps. Locally I used Docker as my development environment.
Links:
Technologies:
-
php
-
phpunit
-
twig
-
test-driven development
-
docker
I did several contracts building a WordPress plugin for AudioVerse. I built a router, I built a system for them to use to place content on different media pages. I built short codes. I architected the whole thing. It's written using test-driven development.
Goals
-
Reproduce functionality of existing AudioVerse.org site
-
Add Progressive Web App features to the site using the pwa-wp plugin to create a site that could eventually replace the organization's mobile applications
-
Support AudioVerse' headless strategy for keeping the database decoupled from the new website. This strategy is for the purpose of allowing new consumer-facing clients to be developed without requiring large changes to existing infrastructure.
Tasks
-
Configure Docker development environment
-
Set up CircleCI for continuous integration
-
Set up PHPUnit for test-driven development
-
Build router and composable route objects to allow for easy addition of and modification to complex routes
-
Build listing and detail pages for multiple entity types
-
Protect listing and detail pages from deletion while still allowing modification via standard WordPress editing UI