Working with custom post types and taxonomies is an essential part of unlocking the full power of Greyd.Suite’s dynamic architecture.
Understanding the concept of dynamic data
The following video walks you through the entire process of working with dynamic data in Greyd.Suite:
- When and how to create custom post types
- How to display post data with query loops / post sliders and dynamic tags
- Overview of how to use post templates (single, archive, search results)
-
Hi, this is Sandra from GREYD and today I’d like to give you a comprehensive insight into working with posts and post types in GREYD.SUITE. To start with, a few terminologies. Post types are different types of content on your website, for example by default WordPress comes with the post types pages and posts — for example for news articles. And each post type now has up to three different templates. First of all the single template, also called the post template, that defines how the individual post pages should look like. So for example on our GREYD.SUITE website we have regular pages and we also have a blog that displays several blog articles. And those blog articles, they all have the same structure and layout which is defined by the single template or post template. And depending on what kind of post type you have, there may also be additional templates, for example to create archives like these ones, also for search results pages. And the last term you should know when talking about posts and post types is the post overview, which is a block that enables you to display several blog posts as an overview as the name already indicates.
So what we’re going to do now is, we’re going through the entire process and create a custom post type and all corresponding templates and a post overview. So let’s go to the GREYD.SUITE backend and open the post type dashboard and let’s create a new post type that we name “Job ad”.
So I’m going to do that all in fast forward. If you want to learn it all in very much more detail, then we have a dedicated tutorial on post types in our Helpcenter. So I now just select an icon, we need content editor, no post image, nothing like that, categories and then we need some fields. For example we need the contact person, we need a description, no that’s no, location — that’s it. So now the post type is ready and we can create posts here, for example developer, the job description, contact person is me, location is Munich. Let’s just create a couple of posts. Another cool job at GREYD, contact is also me and location is Munich and that’s two. One last one, and that’s it. So now we’ve created a post type and we also have three different posts.
So what I now want to do is, I want to have a career page like on our website where we have a post overview displaying the available jobs. So I’m now going to create a career page and I want to show the open positions and this is where the post overview comes in. With the post overview — as already described — I can show in the frontend a couple of posts, so I’m going to have to select the template I want to use to display the job ads, which I’ve already prepared. So let’s just take a quick look at the template. As you can see here I’ve made all elements like for example this headline here dynamic, same with the link and everything. So I can now fill it with content of my posts.
The first thing I have to do in the post overview is to select which post type I’d like to display. The post overview in general is a variation of the native WordPress query loop as you can see here. So I can now select the job ad post type. This variation works basically the same as the native query loop but it offers a lot more options. For example, I can not only define in which order I’d like to display my posts and work with certain filters like only display posts of a certain category or of a certain author. But there are lots of additional options, for example much more detailed and sophisticated filter and sorting options, responsive options. In the template there are also many design options, for example to display the post overview as a slider, with animations, with frontend filter and sorting options. We won’t deal with that today — there are dedicated tutorials for that in our Helpcenter.
What I want to show you now is how you get the content of your posts from the custom post type into that post overview. And that’s where Dynamic Tags come into place. So I now mark everything that I want to fill with content and I will find a dynamic tag here and can say okay, I want to display the post titles or the job ad title. Same for the location. I can either work with the icon here or alternatively I can just enter # and can then also select my dynamic elements. The same works for images and links. For links for example I just set a dynamic link here in the trigger picker and link it to the post. And that’s basically it.
So let’s just update the page and have a look at the frontend. Now we have this post overview displaying all my job ads and when I now click here, I can see the dedicated post. But as you can see that doesn’t really look good. Why? We haven’t dealt with the single template yet, so that’s exactly what we’re now going to do. We are moving to the site editor. By default there is already a single template for posts, but we want our own single template for our custom post type job ads, so that’s what we’re now going to do — we create a single template for job ads.
So let’s get that. I’m now just going to place some content here. For example, we want a header, we want a heading, we want the location. As before you can again work with dynamic tags to display here for example the post title and the location. But in a single template you can also use dedicated post blocks like for example post content. The result is the same, it’s just a different way of how to do it. Let’s put that into a group. Okay, that won’t be really beautiful but it’s going to do the job, so let’s just have a look again at our job ad. If we now look at it, it looks much better. So it has our dedicated content from this particular job ad and in terms of design I can do whatever I want here on that single template and all my posts will have the same layout.
And that’s basically all you need to know when working with post types and posts in GREYD.SUITE. We had a look at how to create a custom post type and create posts of that post type, we had a look at how to create post overviews to display several posts on a page and we just had a look at how to design an individual single template for that post type. For most use cases you won’t need more, but I’m going to show you two more things — archives and search templates.
So for this example here, it might be cool to have another section here that displays additional jobs for example from the same category. So what we could add here now: let’s start with a heading “other cool jobs for you”, we want a spacer and now we put an archive here. Now I could say for example in that archive show me all posts of the job ad, sort them by month. I could also have a category archive if I want to do that. There are again lots of formatting, design, filter and sorting options. We won’t have time to look at all of that. I’m just going to show you how it works. Okay, so let’s just have a look again here. Well, not beautiful, but it doesn’t matter now. What we can see is, we just created an archive that shows us all related posts for example by month.
And we just had a look at a single template. This is exactly the same but for archives, so there’s a dedicated archive template in the site editor. We can just have a look at it. Here it is. So that’s the archive template. Again I’m completely flexible in what I put in here, the only difference is that in the post overview here, we have one option which is this one here — “inherit query from template”. This makes sure that only the posts related to the archive are displayed here, for example I selected all job ads from July and that’s exactly what this is doing.
According to exactly the same principle works the search. We have a dedicated search block in GREYD.SUITE. Let’s just add one here, GREYD search. So I can enter for example a job search with filtering and sorting options, again lots of possibilities. There’s a dedicated tutorial video in the Helpcenter. I just want to show you that it works exactly the same with posts. So you have the search block and you again have a search template with a post overview, again with this option here that will make sure that only the posts related to the search term will be displayed — and that’s it.
So let’s summarize again. Maybe here on our website where there is a little bit more content and let’s have a look at the blog. We had a look at post types — you can work with the default post types by WordPress, pages, posts etc. But we can also create own custom post types in GREYD.SUITE, also with custom categories, taxonomies and everything like that. With post overviews you create overviews that display several posts like here. When you click on an article in a post overview, you will land on the single template. And there are also possibilities to add for example an archive, like you can see here, let’s show for example all marketing articles. And you can also work with searches.
For more videos and information please visit our Helpcenter.
Dynamic Post Types
Greyd.Suite has a built-in feature to create custom post types and taxonomies.
The following video show you how to create and work with Greyd.Suite’s Dynamic Post Type feature:
-
Hi, this is Sandra from GREYD. In this video I’d like to show you how easy it is to create custom post types in GREYD.SUITE without coding or plugins with our Dynamic Post Types feature. You’ll find the Dynamic Post Types in the GREYD.SUITE dashboard or also in the menu here on the left. Here you’ll find an overview of all your post types and you can create a new one by clicking up here. At first start with giving your post type a name. This name will also be displayed in the WordPress menu later.
In order for your post type name to appear correctly everywhere in the back end, please enter it in singular and plural and then we just have some general settings to make — for example where and how do we want the post type to appear here in the menu on the left. We can select an icon and a position. If you can’t work with these WordPress defaults here just select one of those options here, so for example after media. And then we define which features we want to have available, for example the content editor to be able to edit the content of the post by the block editor, define whether we want to have a post image, excerpt and/or author, categories or tags. And we also have the possibility to create custom taxonomies to further categorize the posts of this post type, for example by country. Again add in singular and plural and define whether you also want to have sub categories or not.
In terms of taxonomies you can also create global taxonomies, that are not only available to this post type but also to other post types. For example, let’s categorize our post types by partners and then we can define which post types I want to have this taxonomy — for example customer statements and posts. So this is really handy because you can make lots of very interesting stuff in relation to post overview, filtering, searches and all that, because these two post types now both use the same taxonomy and can be categorized by partners. With this option here you define whether you want the taxonomy only to be available in the back end for you to work with it or also in the front end, for example when you have filtering options in the front end and searches or post overviews. And again you can make it hierarchical.
Other than that we have some general architecture features, for example do you want the post type to be searchable, do you want to have an archive, do you want to add posts to the menu, do you want it to be hierarchical. And the last one — obviously we still have to translate this new option here — it’s a very interesting one. It makes the information of the latest post available as dynamic tag on your entire website. So you can use it and insert it dynamically anywhere on your website without having to work with post overviews and query loops and all that.
Let me show you an example of a post type that I’ve already created. Just go and create page and tag test, this one. Let’s just add some content here and let’s say for example: check out our newest job offer in … and now I want the website to automatically display the location of the latest job ad, which is a custom post type of mine. So I can now just say use dynamic tags here and I can not only insert the website title and the default dynamic tags or standard dynamic tags, but also information from my post types where I’ve activated this option here. And for example I could say display the location of the latest job ad and as you can see here, that’s automatically there, without post overview or anything. And if I now create a new job ad that has a location Frankfurt, it will automatically be changed on the website to Frankfurt.
Now you’ve made all basic settings and can start with creating your individual post type fields. Click here to add a field. Then add a label as well as a unique field name. The label is like a headline in the backend, displayed directly above the field and an important help element for the person who will be creating and editing posts later. Therefore choose a label that clearly explains what this field is to be used for. The unique name on the other hand will be used in the backend, for example you will find it later in the post overview block. Then define which field type you’d like to add and whether the field should be mandatory.
You can now choose from different variants of text, number, email or date fields, radio buttons, dropdowns, links, files or image fields as well as fields with HTML editor. You can also make the backend even more lucid with the field types headline, description and separators. That way you can add helpful information for the content editors in terms of how exactly the fields should be filled. For example you can also inform them in detail about optional fields only being visible in the frontend when they are filled with content.
My tip: If you want to have only one image in your post type, you could also work with the post image. However, when using the image field you will be able to add information for example about which format or subject should be uploaded. Here you can add additional inputs to support content editors who autofill your post types with content. Depending on the field type, you’ll find several different options. You can define placeholders, default values and descriptions. For number fields you can also add a minimum/maximum value as well as the steps. And for dropdowns and radio buttons you can add the selection values which should be offered in the field.
You can even vary the display option and the backend option. And for headlines for example you can also define the H-tag. So now let’s create our post type with the respective fields. By clicking here, we can add additional fields. I’ll just have a name, company image and statement as fields. You can also drag and drop your fields, edit them, duplicate or delete them.
So, ready is our Dynamic Post Type “customer statement”. You can now see the respective menu element here on the left and there you can edit your post type or create posts. Here you can now see all the fields which we have created earlier and can fill them really easily. This here is a WordPress standard that you don’t need. You can also hide it by disabling it here. So now it’s super easy to add new customer statements here without any WordPress skills.
How your posts will be displayed in the frontend is defined by its post template. By default, posts in WordPress are displayed with the so-called single template. If you’d like to create an individual layout for your new Dynamic Post Type, just click on “new template”, select post page and your Dynamic Post Type.
To include posts on pages, you can work with the post overview block or also the native query loop of Gutenberg. I’ve prepared an example post type here with some already published posts and I now want to include them on a website. I’ve already prepared it. So here we have several post overviews of one and the same Dynamic Post Type with an image, name, position and a statement. Here we have the post overview or the query loop. It’s almost the same. And with dynamic tags, I have included my post type fields of my custom post type.
There’s also a dedicated post overview or query loop tutorial in our Helpcenter. If you now combine that with our Dynamic Templates feature, that also offers you the possibility to implement optional fields. So it’s super easy to create different designs and layouts with one template and one post type. So here you can see different post overviews, but they all use the same template and they all refer to the same custom post type.
So how have I done it? I’ve got a template with a lot of optional fields, so there are no placeholders here. If you want to learn more about that, there’s also a dedicated Dynamic Template tutorial. And here I now have created several post overviews and sometimes I have used all fields and here for example I’ve only got the template filled with the statement. That way you can create different layouts by using the same template and only creating one custom post type.
So through that separation of content and design or layout, it’s possible for content editors without any technical knowledge to easily edit and fill Dynamic Post Types, while you still have all design options at your disposal. The editor only has to fill these fields and all this is managed by the designer.
For more videos and information, please visit our Helpcenter.
How to display post data
To display post data (from core post types or custom post types), you will need to use the query loop block, of which Greyd.Suite offers various variations with advanced filter & sort functionality.
The first video shows you how to
- create custom queries with individual layouts including sliders
- insert dynamic data from you posts
- benefit from Greyd.Suite’s advanced filter & sort functionality in both backend and frontend
- create interactive live searches
-
Hey, this is Sandra from GREYD and in this video I’m going to show you how to create individual post overviews and sliders with GREYD.SUITE.
To build a slider or post overview, you always need a Query Loop. A Query Loop is there to display certain posts of a post type and it always consists of a post template and the content. There are different ways to start. For example, if we just add a Query Loop here, we can either start with a template or pattern. Or we can start blank and then you will see a couple of presets, among others our post sliders.
A post slider is basically a variation of the post template. So if you have a look at the structure we had before, we had the Query Loop and post template. And now we have Query Loop and post slider. Since this is a variation, you can directly start with post slider and automatically get this layout.
In order to see something in the preview, select some pattern or template. Now in the parent block, the Query Loop, you can set the alignment and how many items you want per page, how many offset, or how many pages you want to have. If you set zero, the Query Loop will create as many pages as necessary to display all your posts.
On the right you will find more options. Depending on the width, you can say that the inner blocks should use the content width as defined in the site editor. This option is only necessary if you place your post slider in an archive or search template. In all other cases, you select which post types you want to use for your post overview. For example, I’ve got a post type “movies”. Then you can define the order of posts and further narrow them down with filters — by taxonomy, authors or keywords. If this is not enough, we offer more advanced filter options. For example, exclude a taxonomy, only include terms of the current post, or exclude them. You can filter by meta fields, by date, or select individual posts to include or exclude. Advanced sorting options are also available — by meta fields, most popular posts, random, etc. And you can combine filters and sorting.
Now let’s go into more detail with the post slider. You can switch between list view and grid. For each breakpoint you can define how many elements per page, how many columns, and how much space between them. This makes it simple to create responsive grids.
You can always switch between post templates and post sliders. You can also add filters in the frontend so users can filter posts themselves. Place the filter on top, below, left, center, or right, and define the design, size, and spacing. Users can also sort posts themselves with a dropdown. You can customize the labels, which is useful for multilingual sites.
You can add arrows to switch between pages and place them anywhere: top, bottom, beside posts, or overlapping the content. You can use icons or upload custom images, and define colors, hover effects, size, and spacing. Alternatively, you can add classic pagination with digits or icons, top or bottom, overlapping or not, again with lots of design options. You can also define the animation of page transitions, enable looping, autoplay, and set the speed. On mobile you can enable automatic scrolling so that when a new page loads, the view jumps to the first post instead of staying at the bottom.
To display your individual post content, use GREYD.SUITE dynamic tags. Either place a dynamic template or individual elements like headline and image in your post slider, then connect them to your post content using the dynamic tag icon or a hashtag. You can display post titles, dates, featured images, custom fields, or general tags like site title, user name, or date. You only need to configure this once — it applies to all posts in the loop.
When you click on a linked post in the frontend, you see the post page defined by the post template. Post templates are regular WordPress templates you edit in the site editor. You can use default placeholders like post content, or GREYD dynamic tags like author. For custom post types, you can create individual single templates, so each post type can have its own layout.
If you combine the post slider with GREYD.Search, you get an interactive live search. The results of your post overview update instantly as you filter. GREYD.Search also provides more advanced design options and filter features, like date pickers. To enable this, just add the GREYD.Search block inside the same Query Loop as your post slider. Or start directly with the live search block, which includes both by default.
So as you’ve seen, you have lots of different possibilities to design and create individual post overviews and sliders. There are more tutorials in the Helpcenter on working with templates, creating post types, and building searches. One tutorial in particular shows the entire process — from creating a custom post type to styling post templates, to building post sliders and overviews. Definitely have a look in our Helpcenter.
For more videos and information please visit our Helpcenter.
If you want to display post data in tables, this video is for you:
-
Hi, this is Sandra from GREYD and today I’d like to show you how to display posts on your GREYD.SUITE website as a table. To do that just enter the block post table somewhere on your website. Post table is a variant of the native WordPress query loop. If you want to learn more about that in general or the GREYD.SUITE version post overview, please have a look at our tutorials in the Helpcenter since I will now focus on those functions that are relevant for the table.
At first, as usual in query loops you can select which post type you’d like to display and can of course also select from your custom post types here. And you will find the usual settings for the order and if you want to filter your post type. As soon as you click somewhere in your table you will get to the table settings and can define how many columns your table should have and whether or not you would like your table to have a header and or a footer. All other settings already belong to the respective columns. You can for example set the alignment and define whether or not the user should be able to sort the table after that column in the frontend.
And you can define the size of the column individually per breakpoint and even hide columns for certain breakpoints, that way creating really mobile responsive tables easily. All the other design settings in terms of colors, fonts, forms are defined in your global table stylings. So now let’s fill our table with content.
As you’ve seen, you can just enter your text directly here by just typing it in, which makes mainly sense in the header or footer or if you want to have the same text in the entire column. Other than that, filling your table with content works with Dynamic Tags – either with the symbol here or by just entering a hashtag. You will find all available Dynamic Tags – all the standards like the post title, author etc. – but also all your custom fields like for example for my post type I have a price field. And I can of course always add individual text directly in the editor.
You can also work with all options from the toolbar including links that you can set here. Other than that you can always edit your table here by adding or deleting columns. There are also some very interesting Dynamic Tags especially for the header and footer, for example you can build totals or averages, which is very interesting if you have numbers here.
If you want to learn more about Dynamic Tags in general, there’s also a tutorial video on that in our Helpcenter. For more videos and information please visit our Helpcenter.
Working with post templates
In the site editor you can create custom templates for post pages (single template), post archives and search result pages.
-
Hi, this is Sandra from GREYD. In this video I’d like to show you how to create individual post archives in GREYD.SUITE. As you will see, we have added some very nice features to the native Gutenberg features. With the archive block you define which post to be included in your archive. In the editor you can at first define the alignment before it’s about the details on the right. By default, your archive categories will be displayed as a list but alternatively you can also go for a dropdown appearance.
And you can define whether you want the number of posts found displayed or not.
Now it’s time to define which type of archive you want to have. At first, select the post type to be used. If you’ve created individual post types with GREYD.SUITE’s Dynamic Post Types feature you will be able to select them here as well as the WordPress standard post types – like pages and posts – or for shops there will also be additional ones. Based on that you can then show posts from a certain time frame, with certain tags or of certain categories, where you can also work with your custom taxonomies if you’ve created some. You can also define how the results should be sorted. For example chronologically from the newest or oldest or also alphabetically, backwards or forwards. You can define whether or not to show subcategories and for date-based archives you can also choose from different formatting options.
Depending on which display variant you’ve chosen earlier, you will now find some design options. For example for list archives, you can add an icon and adapt the size and space and select from your global button or link styles. You can also of course work with an individual style. For dropdown archives it’s almost the same: Here you can choose from one of your global field designs or also overwrite the design individually. Now your individual archive is already finished.
How the archive page itself looks like is controlled by the archive template. With this template you can style and layout your archive page completely individually. Therefore you will for example need the post overview or query loop block to display the posts that were found in your archive. To learn more about that there’s a dedicated post overview tutorial in our Helpcenter.
For more videos and information please visit our Helpcenter.
Example content & use cases
Custom post types and taxonomies are extremely powerful features, especially when combined with other Greyd.Suite features like Dynamic Templates or Global Content. To make it easier for you to fully understand the concept of working with dynamic data in Greyd.Suite, we have prepared two example sites which come in handy while learning how to use these features. But they can also be used as templates in order to not having to start from scratch.
Welcome to this walkthrough of our Greyd Suite prefab demo site called Events. We’re going to walk you through three very powerful features of Greyd Suite: global taxonomies, nested queries, and conditional content.
The site demos a scalable setup for promoting and managing training events all over the world. Fun fact, although the locations, people, and schedules are 100% fictional, the content of the training sessions actually isn’t. These could be real training sessions that people can give around the globe.
The site is designed to show you how you construct your content efficiently using only Greyd Suite, so you don’t have to rely on custom code or external loaded plugins that bring in a lot of stuff you don’t need.
So let’s go over to the back end. Let’s start with the core structure. I’ve created three main custom post types: Location, Expert (which throughout the front end is also called Instructors), and Event. Now, to make sure that we can display those with nested queries—meaning we can actually display data from one custom post type inside the template of another—we have to make sure that they have something in common. And this is where global taxonomies come in.
Every custom post type in the setup has been connected through shared taxonomies. Those are the ones you see here. Now if I open up the edit post type, you will see that these are all checked to connect. The Event post type also has a lot of custom fields because of course we want to filter by date, start time, end time, and so on.
So all in all, we have 274 events happening all over the world and online, which is also registered as a location. This is a very simple, straightforward page. It displays a query loop with the locations. But now we go into, for example, Madrid. Actually, the post itself is very boring. If you go in, all it has is the name, the address, and the featured image. But it shows a lot more. And this is happening in that template.
Now I’ll show you what is happening in the back end. One of the many advantages of the WordPress site editor is that if you’re logged in and you’re on the front end of the template, to get there all you have to do is click Edit Site. So here we are. This template displays the featured image here and here. And on the left it has the address of the location. But in the location I’ve also hooked it up to the correct global taxonomy. As you can see here, when we are inside of that post on the right there is Locations. And I chose Madrid because that’s where we are showing the events from.
Back to that query. So here’s the query I nested inside of the location. And on the right you can see how you actually visually build up your query. This is post type Event. And then I used an advanced filter saying I want to filter it by taxonomy. There are more options than that, but we are going for global taxonomies here. And in this case it’s a global taxonomy Location. And then I said terms of the current post, and the term of that current post is Madrid in this case.
Now I also want to sort the results chronologically because we’re speaking about dates. So for that I sort results, ask it for meta to be ascending, and then by date, which is a custom field in the post, and set it to chronological. And this is how it displays the event in the right way.
So we’re moving on to conditional content and using the conditional content block, which is an incredibly powerful feature in Greyd Suite. For this, I’ll dive into the template straightaway.
Here are the considerations: There are 274 events, some of them happening in a location in a certain country and some of them happening online. Now, if an event is online, you need to append a time zone for people coming from other regions so they know when to attend. However, if an event is taking place physically in a location, you don’t need to do that. Instead of trying to resolve this through creating even more custom fields, this is where the conditional content block is absolutely perfect.
Now, let me quickly take you back to the custom post type Event so you understand the relation between the steps I’m taking now. The Event has of course its content, its trainer, and then here are all those custom fields: date, start time, end time. I left the fee empty and the level is beginner. And the format is very important. This is an in-person event. I have two other formats being Online and In-person, and Online & In-person (a so-called hybrid event). And the capacity for this course is 12 people.
Now we go back to that template. I’ve added several conditional content blocks. Here are the two that decide whether something is showing up with a time zone appended or not. The conditions are set on the right side. And in this case, I’ve set the conditions based on the post meta, which means a custom field. The post type is Event, and the custom field that it depends on is Format. Now Format has Online, In-person, and Online & In-person. And now it says: if the Format has the value Online, then show this. If it doesn’t have the value Online, show that.
I have also added a block that is actually depending on tags. And the reason I highlight it here is as follows. Because in the bottom here it says the dependency on taxonomies only works in archive templates. And this is not an archive template. But then again, we are not talking about a taxonomy but we’re talking about tags. So to the post type Event I have added the possibility to add tags in the post type itself, and so I get to select that here. It says select the taxonomy. And I know this can be confusing because this is WordPress speak. Factually, a tag is also a form of taxonomy. But just so you remember: if you use tags then you can set conditions based on them as well.
So now let’s move on to the heavier lifting. I had this consideration when creating these events: again, 274 events. Now imagine you’re going to type the price for each and every event inside of that post. That’s a lot of work. It’s inefficient and it’s not scalable. Instead, I have set the pricing based on the event type of being in-person and all kinds of things.
Of course, you have to think about the exception. So this is the first thing I built in. I said: if the post meta for the fee has a value, then show me that if it has been set. And that’s what I was showing you when I said earlier, the fee is not filled out. Because if the fee has not been filled out, the other conditions kick in. If there is no value in this field and the value of the Format is Online and it is on beginner level, this is the fee. And as you can see here on the right, I have set more than one condition. This is why it displays like this. So that way I have set several conditions, and this is incredibly powerful. You can endlessly add types of conditions.
The next one I’m going to show you is the first one in the row: the URL parameter. As you can see, there are several of these conditions that you can use. On the series overview page, I’ve been using the URL parameter as a condition to change what offer someone sees. Using that parameter lets you send personalized campaigns with targeted messaging. And this is all happening on the same page. You don’t have to redirect. You don’t have to duplicate layouts. And so in this case, I show a standard offer for general visitors. But if someone clicks a newsletter link that has a ?a=1 appended, they see a special version of the same page with a different design and a different message.
Now, if you go to conditional content on the page, I have added in these links. This is the link with that appended parameter. And as you see, this is a completely different layout. Let me show you that under the hood. If it doesn’t contain this parameter it shows you this. But if it does contain this parameter and the value is 1, it shows you that.
This content is available to every content creator. You can download it from our website. The link is in the description or on the page that you are watching this video from. And I’d say: use it. Build it. Adapt it. And most importantly, use it as a blueprint for scalable thinking.
Event website
This website is about international training events. All trainers, locations, prices and dates are 100% fiction (AI generated). We built this to show you the power of nested query loops, connecting dynamic data via global taxonomies and the use of our conditional content block. The site comes with three custom post types and several global taxonomies which are used in all three post types.
The site shows you how events can be displayed per location, how information on a training detail page (event) is manipulated through conditional blocks in the template, and even how that block is used to show the time zone for the online events is always CET, whereas the other times as local.
Yoga studio website
This second website shows another real world example (Yoga Center) with fictional (AI generated) data. The site comes with several custom post types, like teachers, classes and classrooms. In fitness and yoga there are often teachers who give more than one class. And customers are happy when they can see on which week days and times their favorite class (yoga style) is given.
We created individual templates for the Classes and Teachers post type. The Classroom post type is currently there to be displayed as nested in the classes template. However, it’s a great opportunity for you to create a custom template for that where you can nest which classes usually take place in this particular room, per week day for example.
Greyd.Suite website
On our own website we have used custom post types extensively. In this whitepaper you will learn how and why: