WordPress Widgets Refactoring, Part 12 We're going to working on the area of the code that renders information for the user on the area of the site... As far as refactoring WordPress Widget Boilerplate is concerned given how far we've come since the project started eight years ago we've done lot of work in refactoring it.. And this is from the standard of the boilerplate and from standard so that maintenance and code quality is higher.. In the last post, we wrapped up much of the work for the area and are ready to begin our work on code for the front-end.. We're nearing the end, of the refactoring of the Boilerplate and there's just bit more to do before we're ready to merge it into the branch of the codebase... If not, be sure to pull it as that's where we're going to pick up in the remainder of the post... Now it's easy to think of the front-end as anything the user sees before them regardless of if it's in the area or not.. this series has been clear that we're dividing what the user sees between the area and the area of the site.. So what we're going to be doing is working on the area of the code that renders information for the user on the area of the site. The last thing we're going to look at after this is tightening up some of the conditional logic along with word about caching data ..
Read more