The events in Genesis are named by a set convention. You will see this naming pattern throughout the framework. Let’s talk about this pattern and how you use it to locate the different files, components, and features within Genesis.
In the previous episode, you explored the file structure. In this one, you will walk through the Genesis framework’s codebase. You’ll explore the actual code. We will focus on the main structural templating files. Here is the link to the PHP while Docx.
Web pages are comprised of various components, such as the header, footer, navigation, content areas, etc. Genesis divides up its architecture into components. In this episode, you will explore the file structure of the framework in order to find the various components. You’ll learn about the intent of each of the sub-modules, where files are loaded.
Let’s continue exploring the Genesis framework’s HTML markup structure in a visual manner. In this episode, you will look at the footer component, which is from the <div class=”footer-widget”> (if you have footer widgets configured) to the closing </html>.
Let’s continue exploring the HTML in a visual manner. In this episode, you will look at the sidebar component, which is from the closing “content” </div> to the <div class=”footer-widget”> (if you have footer widgets configured). You will look at both the primary and secondary (sidebar-alt) sidebars.
Let’s continue exploring the HTML in a visual manner. In this episode, you will look at the content component, which is from <div class=”site-inner”> to the closing “content” </div>.
It helps you to know the end result of the code when you see it. In this episode, you will use the Genesis Visual Hook Guide plugin to first visualize how Genesis structures the HTML. Then you will look at the actual HTML to see what has been built for you. In this episode, you will explore the header, which is from the opening DOCTYPE to the <div class=”site-inner”>. Here are some links to the Docx to help you out: get_header() genesis() Let’s Test What You Learned Let’s test what you just learned doing this episode with me. Take a […]
What is the intent of the WordPress theme? What purpose does it serve? How is it different from plugins? A theme’s intent is to prepare and render out the HTML, i.e. content presentation. It handles the process of building what is needed to head out to the browser. In contrast, plugins are meant for extending or changing behavior and functionality. Features such as custom post types, taxonomies, widgets, shortcodes, etc. all go into a plugin. Plugins may even have their specific template files; however, styling is still a theme responsibility.
Next, let’s go into the actual WordPress Core, Genesis, and the child theme code. You will see the order (or sequence) in which files are loaded.