Labs are hands-on coding projects that you build along with Tonya as she explains the code, concepts, and thought processes behind it. You can use the labs to further your code knowledge or to use right in your projects. Each lab ties into the Docx to ensure you have the information you need.
Each lab is designed to further your understanding and mastery of code. You learn more about how to think about its construction, quality, maintainability, programmatic and logical thought, and problem-solving. While you may be building a specific thing, Tonya presents the why of it to make it adaptable far beyond that specific implementation, thereby giving you the means to make it your own, in any context.
It’s time to finalize the base and common classes. The common classes will be migrated into the appropriate module, while the Base Sass Module will be finalized. You’ll be learning about different strategies and alternatives to setup your codebase for what fits you and your needs. You’ll be introduced to Bourbon mixins to save you time and allow you to automatically generate sizes. Then you’ll be migrating the media queries, assigning variables, and refactoring.
The layouts specify the overall widths of the site and the main containers such as site inner, wrap, content, and sidebars. In this lab, you will explore strategies to calculate these widths and then have each automatically generate based upon the base width. This step will save you a bunch of manual time as you adjust the widths for each component in the project. Then you continue finishing up the the Layouts Sass module. You’ll also get the opportunity to use the Bourbon Neat framework for calculating your column class widths.
In Part 2h, you will finish up the Plugins Sass module by refactoring, using the techniques you’ve acquired throughout this entire series. You will also add the plugins that you normally work with in your projects. Let’s get your codebase ready for how you work.
Let’s first give you a pep talk to reinforce why you are doing this series and how it will make you more moola. Then in Part 2g, you will finish up the Widgets Sass module. by refactoring all of the widgets. Then you’ll commit the changes to your version control repository.
In Part 2f, you will finalize the Comments Sass module, which includes respond form, the list of comments, and then the components with the comments itself. You’ll think through all the components and then break up the partials. Next, you’ll migrate the media queries, identify and assign variables, and then refactor to remove redundancies and make it more readable. Lastly, you’ll commit the changes using git.
In Part 2e, you will finalize the Entry Content Sass module, which includes the entry title, entry header, entry meta, entry content, and entry footer. You’ll think through all the components and then break up the partials to fit those components. You’ll migrate the media queries, refactor, identify and assign variables, and then refactor to remove redundancies and make it more readable. Then at the end, let’s setup the README and gitignore files and then commit the changes using git.
In Part 2d, you will finalize the Footer Sass Module, which includes the footer widgets and site footer components. Just like with the other Part 2 labs, you’ll migrate in the media queries, assign variables to make it easy to customize, and refactor it further to remove redundancies and clean it up. Then at the end, let’s commit the changes to GitHub.
In Part 2c, you will finalize the Header Sass module, which encompasses the site-header area including the site title, site description, and, if configured, the header right area. You’ll migrate in the media queries, assign variables to make it easy to customize, and refactor it further to remove redundancies and clean it up.
WooHoo! You are now done with converting the native CSS stylesheet over into modular Sass. I know that was a long process, but you only needed to do it once. Now you have a codebase that you can use on every single project and site that you build. Quick Summary of What You Learned: It’s Sass and not SASS. You have a modular codebase that you can use on every single project. Color changes are quicker as you change them in one spot and your entire stylesheet changes. Typography changes are quicker. Dimensions are customizable in one spot. It will […]
It’s time to check that we have all modules and sub-modules imported into their index files. And then we’ll make sure that everything is imported into the style.scss main style file. We’ll talk about the DocBlock too.
Know the Code develops and empowers professional WordPress developers, like you. We help you to grow, innovate, and prosper.