This week I was supposed to focus mainly on learning React, in preparation for the Zao project starting next week, but as anyone could have foreseen, client revisions and retainer obligations cut into some of that time. It wasn’t all bad news; projects got finished, retainer contract goals were met, and clients were happy.
ISS of BC
Following last week’s issue that came up with ISS of BC, the path forward was unclear, but I needed to figure out a way to get the students’ online english assessment answers when sending the notification emails to the student and the admin.
As it turns out, I was able to remove the emails from the default notification timing (as soon as the quiz is submitted and before scores are saved to the database) to instead happen after the quiz is scored, using the
sensei_user_quiz_submitted hook. It took a bit of adjusting since the other notification hooks
sensei_course_status_updated didn’t have the same matching variables as the new hook, but I got it to work and because this site only has one Sensei course I wasn’t worried about messing up emails for other courses by changing something very central to the course processing.
Practical Ecommerce and Qpractice retainer clients
This week we adjusted the footer of all articles to have new links to Previous and Next posts (based on publish date of the posts). Also updated a bunch of plugins, made tweaks to styling that were needed because of plugin updates, and removed some plugins we really didn’t need anymore.
For Qpractice this week there were some minor styling tweaks that needed to be completed and plugin updates to be done. I tested the plugin updates on staging, then I backed up the live site and perform updates to non-critical plugins. For the critical plugin updates Qpractice uses an overseas contractor who performs the updates during the middle of the night in North America, to minimize potential downtime if something goes wrong.
The exciting new project
On Wednesday I had a kickoff call with Justin Sainton and Liz Karaffa from Zao to go over the structure, process, and organization to prepare for the project starting next week. I came out of the meeting feeling excited and slightly scared because this project is the best organized and probably most well thought-out project I have worked on in quite a while. The majority of projects I am involved with no one else ever sees my code, documents the processes, or tracks the projects pulse daily. For the next month I will be doing my best to keep up with all the action, learn new things, build great habits into my process, and hopefully ship clean code.
During the kickoff call, we chatted about the local development process this project uses. For the first time I am trying out Lando and using Pantheon hosting. I had never even heard of Lando before but knew Pantheon existed and was leader in the WordPress and Drupal hosting space. I usually use Local by Flywheel for WordPress development and Homestead for Laravel, but for this job the Lando integration with Pantheon seemed like a perfect fit. Lando makes it super easy to make sure everyone has the same local development environment and makes it unbelievably easy for developers to have a proper staging site for collaboratively testing new GIT branches. Each developer can be working on a different feature of the website and have a unique url for testing that feature before the code is merged back into the main branch.
Setting up Lando was very quick and easy on Mac OS; the only tricky part was figuring out the exact credentials for connecting to the Lando MySQL server from my Sequel Pro desktop application.
Getting my learning on
I am hoping to hit the ground jogging next week, keeping all my projects moving forward, and clients happy. For the short term, I won’t be taking on any more new projects because things are going to be busy enough already.