Start learning with our library of video tutorials taught by experts. Get started
Viewers: in countries Watching now:
In this course, author Joseph Lowery shows how to combine the utility of WordPress and the power of Adobe Dreamweaver to transition existing websites to the WordPress platform. The course demonstrates how to create new blog posts and pages, customize WordPress themes, and extend WordPress editable pages from within Dreamweaver. It also covers how to add Spry elements, add and customize plugins, and enhance WordPress-stored content with Dreamweaver's dynamic pages. Plus, a chapter on responsive design shows how you can adapt your layouts for tablets and mobile devices.
The next section of the WordPress page we're going to turn our attention to is the main content area. In this lesson, we'll address the general content wrapper that includes both the primary content div and the sidebar as well as style in the content area itself. Along the way, we'll make some minor adjustments to the WordPress PHP code. Just as WordPress uses a file stored in the theme folder called header.php to contain all the header elements, the code for the main content area, which you see here on the left under the heading Roux Academy Blog, is in another file, also stored in the theme folder with the name of index.php.
Now, this is not to be confused with the main index.php stored in the WordPress root. To customize this, we'll need to copy the index.php file found in the custom theme folder, and paste it in the roux theme folder. So I'm going to go to my Files panel and expand it, so we can work a little bit easier. Scroll down a tab until we're in the wp-content area. And here, I have my themes already expanded, and there's custom and roux.
So let's open up custom a little bit. There is that index.php file that I mentioned. I've selected it. Now I'll press Command+C to copy. Select the roux folder and Command+V to paste it in. Okay. All of our preps done, let's tackle that content area. So, I'm going to go ahead collapse the Files panel, and then let's go and make sure we're pulling in right from the blog, it's kind of hard to see down here.
Right below the blog folder is my index.php. You want to make sure that you've got the right one you're working with. So, double-click that to open it. Let's discover the files and go right into Live view. So, for me, the guerilla on this page is pretty obvious. The sidebar in the comp that we see here is on the right. While in the current WordPress page, it's on the left. Let's see how that's done in the comp and make any necessary changes.
So I'm going to head on over to my blog comp, and I'm going to collapse the Files panel here just so I have a little bit more room we're going to be mostly working with CSS styles for a little bit. So, we're in Live view. Let's turn on Inspect mode, and I'm just going to go into the content area. I have my h1 tag there highlighted. I'm going to walk up the DOM tree by pressing the left-arrow key just to see what we get. So if I look over in the CSS Styles panel, I see that main area that we see there is article#mainContent, and that seems to be this main area on the left.
So, in this article with a id of mainContent, and I look at the properties. I see that there is a float: left property. Well, that's key. And this rule also has the widths and margins involved. So, let's go ahead and click once to turn off Inspect mode and then I can right-click on my Rule in the Rule pane here, and choose Go to Code. And that will take me right to article#mainCcontent, and I'm going to copy these properties here.
I know since working with this that we don't have exactly the same selectors in my index.php file. Instead of mainContent, our selector over there is called just content. So, I'm just going to copy the properties. Let's narrow down our files here. We'll go to the Custom Filter. The files we're going to be working with primarily are style.css, put in a semicolon, and also index.php. There are our two style sheets.
Let's go to the first one which as I hover over it, I can see is the one that's in my Roux Theme folder. I want to add in those properties that I had for the content area. I'm just going to scroll down past the header styles and the nav styles. Go all the way to the bottom here, and just so you know just to double-check and make sure I've got that div give right, I am going to just click right into this area here, the main content area that we see. And if I inspect that in a similar sort of way, I can see that I did remember it correctly, that there is a div called #content.
You want to make sure that even though you may think you remember something properly, there's a lot of selector names going around, so sometimes double-check that. So, I'm going to make this content, and then just put an open and closing curly brace. And if you recall, I copied just the properties, and I'll paste those in. Let's go ahead and refresh the page. It looks like that was successful. There, I've floated the content to the left, but that just is half the battle.
If I scroll down a little bit, you'll see that my sidebar area is now also on the left here, and we want to float that one as well. So let's head back to our comp, and see what we can find about how that is handled. I'm going to scroll over a little bit here. He's my good friend, Inspect, and again, I'm just going to hover over a little bit of the content in that area, and then walk up the DOM to find exactly what it is we're working with.
So there's the rule for the widgets. I'll press my left-arrow key again, and here we're getting a little bit closer into it. Here we see a section.info. That seems to be part of it. But if I look down at the tag selector along the bottom of the screen, I see that section.info is actually within a within aside. So let's go up again, again pressing left-arrow key, and there's my aside, and I see that it does have a float: right with a particular width, 318 pixels. Perfect. So, I'll click once on the screen, turn off Inspect mode, right-click on aside rule to Go to Code, and there it is right there. So, let's copy these properties.
Again, we have a different selector named in my comp, and I'm going to scroll down and find, I believe it's called widget area, but I'm not absolutely positive of that. So, let's go into Inspect mode, into the sidebar text, and again creep up the DOM, and I'm right, there is a widget area. I don't have that defined in this style sheet, it's in my parent style sheet. So I need to add that in. So it's a class widget-area, and again, we'll open and close those rules, and I will just paste in those two rules. All right.
Let's hit Refresh here and see if that works its magic. And if I scroll up, indeed, so we're moving along pretty well. We have the sidebar in its proper place. Now, we can address the look of these columns, specifically the equal length of the columns. In the comp, this is accomplished, as I said, by using a image, and let me actually, sometimes I'll click on Edit Rule if I can't see everything. I can go in here and find it pretty quickly, and that will open up the CSS Rule Definition dialog box, and I can see that it's a image called blog_content_bg. it looks like PNG.
So, that's good. So we'll need to get that file, and bring it in. I'm going to go back to my Files panel, expand it so we can find our work easily. And this time, we're going up to the _images folder that's found in the site root. I'm looking for blog_content_bg.png, and there it is. So let's copy that. We want to paste it in, you guessed it, our child theme folder and the _images folder. So I'll just expand that, so we can see what images we already have, and verify that it gets pasted in.
I'll press Command+V, and there's that image. Okay. We can collapse the Files panel one more time. So, we've got the file moved, but now we have to get the rule. Let's go to this particular rule here, right-click on it, and go to code so we can get all of those properties, and head back over to our Roux style sheet. I'm looking for whatever the wrapper is that's around these two content areas, the main content area and the sidebar.
So, let's use our friendly Inspect mode again, and again highlight an area, and go up the DOM with first one press of the left-arrow, and we don't have our wrapper quite yet. Let's keep going this tree, up again, #contentWrap. All right. So we're looking for a property called #contentWrap. And I do not believe I might have something already defined in that area, #outerWrapper, no, but no #contentWrap. Okay. So that's fine. Let's go down.
And I'm going to put it actually above content wherever possible. I like just as a best practice it makes it easier for me to find things to kind of put things in a logical order. So, my #contentWrap is around the main content area and the widget-area, the sidebar. So I'm going to put that ahead of things. And again, put in my curly braces and paste in my properties. Now you'll recall that earlier we've had to adjust the path for any images that we bring in, in the background, and we'll do the same thing here.
We're going directly to that folder now in the child theme, so we don't need to go up a level as we did with the blog comp. So, let's get rid of that path. Now, I'm going to save the file, and click Refresh. Let's head to Design view, and there's our full column, design. Obviously, we are going to have some work to do over on the sidebar to bring that in. But things are now looking relatively good.
Find answers to the most frequently asked questions about Dreamweaver and WordPress: Core Concepts.
Here are the FAQs that matched your search "":
Sorry, there are no matches for your search ""—to search again, type in another word or phrase and click search.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.