Before we go on to the last topic in this Thesis 2.3 for DIY Website Builder seminar, we have a question that I’d like to answer. It is “If you make a change to one of your containers on a template do all of the other copied templates reflect that change. So when you copy a template do the contents stay linked?”.
ID Follows the Box
The answer is yes and no. Let’s just say we go to this columns box and we give it an ID of content and save that. Everywhere that this copy of the box exists, it will have that ID. If we go over to the Single template now and look at columns now it has the ID of content.
Schema Follows the Box
This is something that I was going to show you a little later but remember when we set the schema? This is the post box post page and we set the schema to web page. Well, that’s actually not appropriate for this template but since we set it one place we’ve set it everywhere.
What that means is that if you need to draw a distinction in schema and most of the time you do then you need to actually create a separate post box for each of those instances. Because we have changed it here, anytime this box is being used any changes you make to it you make to every template.
Location of Boxes Can Be Different on the Templates
However, that’s not true for the location of the box. We could move columns up here and save that template and go back to Home and you’ll see that the columns box is in exactly the same place as it was. It’s not up above the header. It still has the ID of content but the distinction here is that the location and the contents of a box do not follow from template to template. Unless they have the parent child relationship in which case the change will be replicated.
Options/Settings Continue from Template to Template
However, the options or the settings for that box do continue from template to template. Let’s go back over here to Single. If you need a separate and different schema setting for your post box then what you have to do is create a new post box for that and put it in this template.
Add a New Post Box to Change Schema
So the easiest way to do that is first to rename this. I’d rename it “typical page”. Then I would come over here and under Select a Box to Add I would create a new post box. Give it a name. Don’t ever create a box without giving it a descriptive name. It becomes a problem in the future.
We’ll call this one “Typical Post”. In its schema we are going to call it blog posting but somewhere along the line we might want to do an event one. In that case we’d have to create a new template for an event and again change the schema for that. But we’ve got our Typical Post Box now and we shift that out and drop that into the loop. Then we look at how this is being used.
Right now in our Typical Post Box we’ve got description, tags, content, post image and featured image. What we will do now is put author description first. So we open up the tray, come down to author description. Just click on it and it pops up there. Then tags and then content, come down here to tags. We already have content there. It puts it at the bottom not the top.
We want our wp featured image and Thesis post image in there. And then wp featured image is going to come up above content. Thesis post image comes up above content.
So you see you keep this thing here as a sort of recipe. So author, description, tags, content, post image, featured image. Then we’ve got author, description, tags, content, post image, featured image. Now we can hide this tray for the moment.
You can see what we’ve got here. We’ve got a headline and a byline. Now what we are going to do is Shift+Drag this up here to headline above that. Open this and we’ve got author, avatar and headline. Now these actually don’t belong to the typical post one, they belong to the the typical page one. So we are going to Shift+Drag those out and drop them in a typical page.
We have to go find author avatar. Then Shift+Drag that into headline area. And Shift+Drag headline into headline area. Then rearrange it. Then we are opening up byline and for all practical purposes you could leave it like this now.
Nothing untoward is going to happen by you leaving the author, date, edit link and categories inside the byline from this post box. It will still behave correctly. All we are going to do is Shift+Drag that away and drop it up here. Hide the tray. Oh, these go down into the tray.
Now that you’ve used that as a way of starting you can save your template. If we go back to this post we’ve got the avatar showing up there. The headline is here. So, you have exactly the same style and everything is working exactly the same way.
Now if we inspect this element and we look at the schema.org, it is now blog posting not web page. I forgot, I moved all of the columns up at the top. Let’s take the columns back down here where they belong and save it. Let’s reload the page.
Now you have that set up correctly but if you go to your menu and inspect the element you can see that the schema.org is web page.
Agility Skin Makes Application of Schema Easy
We aren’t going to go through the process of changing the schemas on all of these. I personally found that this method for changing schema was cumbersome. So what I did when I created the Agility Skin was I gave you the ability to set schema on a post by post and page by page basis.
Set Schema on a Post by Post/Page by Page basis
For example, if you are using Agility you could come along here and go down to the Agility Page Details section and you can set what schema you want it to be. And in fact, at the very beginning of all of this at Thesis Home you can set default schema by post type.
So if you come over here and click on Skin you can see that there is this Agility Schema Settings. Now you can say for the post type we’ll do creative work. For pages we’ll do article and then custom css and change sets shouldn’t be there. You can just leave it at no schema.
Set Default Schema for Post Types
It’s likely that your schema is going to be different for different post types and it may be different within each post type so I let you set the default by post types here and then once you are in the post you can set it to something else.
Never Need to Use the Skin Editor
If it were an event or a review you could just choose the correct schema for that page from this. That way you don’t have to do it in the Skin Editor.
It is my feeling that schema is too important for beginners to ignore but that Thesis makes it too hard for beginners to change the schema. So I decided I would make Agility, my skin, with a lot of tools that would make it easier for beginners without having to get into the Skin Editor.
Create Separate Schema on Posts with Classic Responsive
Susan asks, “How do you make a distinction between blog posts if you are using Classic Responsive?”. What you do is you create another template. You create one template that is for say Recipes and another template that is for an Event, one template that’s for a regular post and so on. Then when you are posting the post you just come down here and choose the correct template for the post.
What is Schema?
Someone asks, “What is Schema?”. Schema is one of the most important SEO tools at your disposal because you are using Thesis. Schema allows you to tell Google what the main content of your page is and what it’s about, what the secondary content of your page is and what it’s about.
It is also often referred to as structured markup. It is one of the massive benefits of Thesis 2. You want to become familiar with it. I have a seminar on Schema that you can check out to learn more.
Pros and Cons of Using a Schema Plugin
Susan says, “I’ve been using a Schema Plugin. Will it override Thesis schema?”. No, it won’t override Thesis schema. If you are using a schema plugin, it has to be a json-ld plugin which takes all of your content and wraps that all inside of json-ld code. That significantly increases the size of your page.
I will admit it’s better than nothing but since you have Thesis, you should consider making sure that your schema is correct on your pages using Thesis and then eliminating that plugin. That plugin is slowing your site down.
It’s slowing your site down in two ways. First, every time your page loads it has to figure out what the schema is and set it all up. Second, it essentially doubles the amount of content you have on your site by taking all of your content and wrapping it in the json-ld schema tags.
Again, it’s better than nothing but you don’t need it with Thesis as long as you understand how to set your schema with Thesis and your site will run faster.
Advantages of BYOB Testimonials Publishing System
Susan says she likes the fact that it let’s you use a star rating to reviews. Do you have any other suggestions? Well, Susan I’m not sure if you are a member of my site or not. If you are a member of my site you have access to my testimonials publishing system which is built for Thesis.
It creates a testimonials post type. It adds all of the testimonial schema including all of the stars and the rest of that stuff. Plus it gives you Thesis like control over your testimonials. So you can do anything with your testimonials.
You could watch the video I have on how to use this system and you’d be amazed at the possibilities. The thing is that since Thesis can do anything with post types, if you make your testimonials into post types then you can display them anyway you want.
You can display related post types on related testimonials. You can put related testimonials under products. The world is your oyster when it comes to schema and testimonials and Thesis.