Monthly Archives - February 2020

Week-End Review – 2020.06

I hope everyone had a great week number six of 2020. The Superbowl was a good watch as usual, and I’m happy to see Andy Reid finally get his ring. It’s well deserved and long overdue in my opinion. Little Tournamatch learned he can get on and off the sofa on his own. We were just thinking the other day that he needs something new to worry Mrs Tournamatch about </sarcasm>.

Development continued on asynchronous behavior and I also mixed in improved mobile-friendliness on the team profile page. This page contains the single-biggest opportunity to eliminate unnecessary pages (add in some Ajax) and several opportunities to improve usability on mobile. Check out a screenshot of the improvement below:

mobile-table-before

Before team profile mobile-friendly update.

mobile-table-after

After team profile mobile-friendly update.

I’ve determined precisely how to handle the endpoints on the backend – REST has emerged as the winner in that debate. In addition, using native JavaScript where possible is the go to solution for the foreseeable future. I expect to begin rolling out these updates next week. Once the team profile page is finished, I’ll turn my attention to the ladder standings.

Week-End Review – 2020.05

I can’t believe February is already here. Last month completely flew by! It was a terrifically productive month for us, too. We pushed out three updates plus one more today (which was really finished around Wednesday), so I’ll credit January with four updates.

The last two weeks have been focused on adding some asynchronous behavior to several user pages. There are a couple ways to handle it on the back end: WP Rest endpoints and admin ajax handles. I’ve written code for both and still considering which way to proceed. On the front end, I’ve also been comparing using native JavaScript to jQuery – and even some React! I think I’ll actually pass on React for now. The jQuery that ships with WordPress is incredibly old. I’m a bit worried about building out a front end using such an old package. In particular is the work required to update client code once WP Core eventually gets with the program. By building out the front end using native JavaScript, I can avoid some potential hassle later. Using native JavaScript so far hasn’t been that inconvenient.

There is still at least another week of development before any of these additions make it into an update. Have a great weekend and enjoy the Superbowl tomorrow!