[00:00:00] Nathan Wrigley: Welcome. So the WP Builds podcast, bringing you the latest news from the WordPress community. Welcome your hosts David Waumsley and Nathan Wrigley.
Hello there and welcome to the WP Builds podcast. Once again, you've reached episode number 278 entitled build areas, a new and innovative way to create your WordPress website. It was published on Thursday, the 12th of May, 2020. My name's Nathan Wrigley, and I am glad to welcome you to the WP Builds podcast.
We produce a fair amount of content. Typically in a week, we do two shows. We do this week in WordPress, which is live on a Monday at 2:00 PM. UK time. If there's ever anything live on WP Builds, you can find it. WP Builds.com forward slash live. Please come and join us. Make some comments we'd love.
Alternatively, if you can't make that, you can always just subscribe. And if you do that, we will send it out to you in an email. We'll also send out details of our other shows. For example, the WP Builds weekly WordPress podcast. That's what you're listening to now. On a Thursday, but we're also doing monthly shows with peach and Arie all about you.
I and UX. And I've also started a show with Anne McCarthy from Automattic, all about what's coming up in WordPress. And so all of that can be found. WP Builds.com forward slash subscribe. Go there, subscribe to our newsletter and we'll keep you updated. I'd love it. If you felt it was possible to share the podcast with your friends, that would be really great.
If you're like WordPress and like saving money, we've got our deals page. It's a bit like black Friday, but every single day of the week, searchable, filterable, big long list of all sorts of plugins, themes, blocks, and you get the idea of WordPress things. You can find that WP Builds.com forward slash guest. What guess what? WP Builds.com forward slash deals. That's there, like I say, 365 days of the year for you to say you've.
The WP Builds podcast was brought to you today by goDaddy Pro, the home of managed WordPress hosting. That includes free domain SSL and 24 7 support. Bundle that with The Hub by GoDaddy Pro to unlock more free benefits to manage multiple sites in one place, invoice clients, and get 30% of new purchases. Find out more by going to go.me forward slash WP Builds once more go.me forward slash WP Builds. And I would sincerely like to thank GoDaddy Pro for their support, helping us to put on the WP Builds.
Speaking of the podcast today, we have Valenta Mia den chick and he is coming to us from build areas. Now build areas is a bit like a page builder, but a little bit more complicated. And in fact, I would say that this whole episode is fairly complicated. It's a new product. And when I say new Pagebuilder, you're probably thinking, oh, PSI another WordPress tool. But no, this is really not like any other thing you've possibly ever seen.
Is it a point click drag save UI. No, it's not. There's a little bit more. Every time you begin, you have to start from a blank canvas and there's an awful lot of settings and things to configure. So it's not quite what you're used to with tools like element or BeaverBuilder. And there's a lot more to it.
Loads of different features. You start with a blank canvas, build up some templates and the workflow is pretty extraordinary. So check out the podcast. If you're looking to leave some comments. I'd really appreciate that. Go to WP Builds.com. Search for episode number 278 and leave us some comments there.
We'd really appreciate it. I hope you enjoy the podcast. Hello there and welcome to the WP Builds podcast. Once again, we've got an interview today and I am joined by Volodymyr den chick. How are you doing?
[00:04:21] Volodymyr Denchyk: Thanks Nate. Hello, Nathan. Thanks for having me here. I'm doing well.
[00:04:26] Nathan Wrigley: How are you? Yeah, I'm good. I have to confess.
I had to rehearse Volodymyr his name? Quite a number of times. It just so happens that my tongue can't get quite get rounded, but I think I got. Yeah. Yeah, correct. We are going to be talking today about a totally, really sublimely interesting project. I don't think unless you've come across this and looked at it independently yourself, I think it's quite unlikely that you've ever used a tool quite like this.
It's called build areas. Again, apologies if I've pronounced that incorrectly, but the spelling of it is easy. It's builder. I U S so build areas and the website URL is build areas dot. I O I would highly recommend that at any point in this podcast, if you become confused or you just think, how, what are they talking about?
How does that actually work? Your best bet is going to be to go to that website. So build areas.io, pause this podcast, go to that website. Poke around and see what's over there and then come back and press play again because fear that the level of complexity, which this subject deserves is going to be a little bit difficult with audio.
Volodymyr first question, just give us the elevator pitch. What is building.
[00:05:42] Volodymyr Denchyk: Doris S we wrote in our logo in on our website, it is WordPress development environment. It is not typically lab, page builder side builder theme builder, like other builders on the market. It is something new.
That's why we tried to identify the category to do, to which we belong. And we decided to invent the new category of so far. It is like a really development environment because it's it it's functionality more than just the page builder it's functionality. You should cover page. Foreign building facade of filtration and even some work with multilanguage plugins and later we will add much, much more Frank functionality.
[00:06:40] Nathan Wrigley: Yeah. The idea here. It's a plugin, right? Yes. Purely for WordPress. So they label it as the all in one development tool. And I think probably most of the people listening to this podcast have great experience with things like a traditional page builder. We're a decade into that whole software environment where you go in, you log into your WordPress page.
Whatever it might be and you click and drag and move things around and save it. We're talking oxygen BeaverBuilder element or this is more than that, but it's also got a very different way of operating. So do you want to just outline some of the main differences between what we think of as a page builder and what your tool can do and how it works?
[00:07:27] Volodymyr Denchyk: Yes, of course. So bill Doris proposes you the main thing, which is different comparing to other builders that is that they build areas, proposes the let's say software development workflow. So let's consider WordPress website development software development like WordPress plugin, because actually if you.
Creating something. Let's talk about creating website outside of WordPress. How do I do this? You are creating some. You are doing some changes. You can preview how it's working in your local environment. But anyway, after from time to time, you should save your data. And of course, developers, they use something like, get version control system.
So save their data in the commits. And from time to time, they have more than one can meet. They can have different brains. And after they are happy with the functionality of the software, this website they are releasing eat. They are uploading this to the production server sometimes with some unit and functional tests sometimes not, but like this workflow of software development.
And we tried to implement the same the same software development workflow in a build areas. So in build era, We have them plates. We have apply rules, so it, everything close to other builders. So you can create a template for a single are pages. You can create templates for posts for five pages for custom posts for different types of archives, archived by user archive by category custom taxonomy, lots of possibilities and a.
Every template, which you are creating is a separate, let's say VCs repository, a version control system. It's like in a GitHub you have a repository for is plugging. So in our structure, every template of builders is a separate VCs repository and every complaint can have inside branches. But you can have more than one template in your in your site and it's okay.
It's naturally. And you can combine them on top of templates, you can have multiple levels of settings this settings common to more than one template and this global settings, they are also obviously has repositories, which can have their own branches and their own commits. It is focused on let's say complicated sides of development.
Of course you can create in simple sites. But I don't know, maybe if not reasonable because the workflow and the functionality we tried to implement. To help people to solve the complicated things with lots of pages, complicated logic some forms of mission. So that's why the structure is like this.
And even possibly possible that on one template can work. One development developer on another template can work another development developer and they have the. Different commits quantity. They can move some common things to global settings. They can, of course can there can be some conflicts and the same, more like in March conflicts in a get engaged version control system.
And we have in the profession, we have functionality to fixing those conflicts. A very powerful things. Complicated complicated websites. Yeah. And after an after old, this oldest stuff is ready. So you have 1, 2, 3, 5, 10 templates, some global settings during development process you are doing, and there is the the point where you're happy with all your parts of your site and you want to.
Group eight, some somehow, and deliver to the production server, show the customer different things. So on this step, we have another powerful tool. We call it our cut delivery system. Now it is possible just in, in this system. Just one thing can be created. One, we call it deliverables, builders deliverables, and now just one type of deliverables available.
It is really. So you can group all your templates, all your commits. Not all actually, but the specific commits you want. Let's say in one template you have 25 comments in another template. You have five commits in in global settings. You have just one commit and you are picking the right commits for you.
Version of the site and you add tech, you add the same tech to these commits. So in first template I want to tech commit number 23 in another template. I wanted tech number four and in global settings, as I have just one can meet, I am. The tech to this one commit. And by doing this, I am grouping all these commits from different parts from global settings and templates.
I am grouping them into the release. Release is the full version of my site. And by creating such release, I can publish it or I can export or eat and move it. It will be expert at, as zip archive will with all necessary images inside and it can be portable and it can be imported from the staging server to the production.
And on the production server, it is not necessary to have all these templates. Gametes branches just release is enough. And by importing there this release can be published there. And the good thing that there can be more than one release in the city. But just one can be published at the same time.
So let's imagine a situation you have previously created release. It is working. It is published. Customer is happy, but you are continuing, you continue your work on the website and you are adding some new functionality. And then once this functionality is already, you are creating new release.
We can also can be published but customer or just the regular users of the website, they found that there is some mistake that's bad situation. But what you can do, you can publish previously created release, which is totally good. And this version of the site will be visible to all your sites, visitors.
And at that time, And you have time, you can, you have possibility to fix the mistakes in your next release, which was published, but it was buggy. So it's like this is workflow, which build areas.
[00:15:23] Nathan Wrigley: Yeah. That's so much in there, so let's just recap. The premise really, I think here is that you are building out templates for things that you want to have on your website.
So that could be posts or pages or what have you. And then within that, you've got the option to have version control, staging. Option where you can get your team in and they can be working on things synchronously and, committing things and making decisions about what is finally going to make it into the production version of the site.
This is all really interesting. So that's the high level. That's what we're trying to achieve. Which brings us really nicely to how the, how these templates are constructed. Anybody that has been using WordPress for any length of time is probably familiar with the concept that behind things like posts are templates.
You need some sort of template in which the content, the data is actually going to reside and. We may have done those in the past with template files, you might've had your ID out and literally created the templates by typing them out. And then now I think a lot of people are using page builders.
They're setting up templates in that way and saving them away and then dropping for want of a better word shortcodes in where the data might reside. But. I suppose with the name, build areas this is where the builder comes in. You've got a graphical user interface, which kind of is a bit like a page builder.
But it's much more than that. It's really difficult to describe but you are able to operate on a gooey. You're not doing all of this by opening up an ID and typing. You are selecting things from a user interface. Depending on what you select further options are offered up to you.
So for example, it might be that you want to have a, you want to display this content on a particular page. If a certain condition is met, all of that is in there. So try to describe if you can, the process of using your builder.
[00:17:36] Volodymyr Denchyk: Yeah. Yeah, of course. So first what you need to do just one one thing I should tell.
The unique feature of build arrows is that. It is not over reading the theme. You can combine, you can afford some parts of your site for according to the templates. You're creating coding to the apply rules of templates you can cover just part of your site by builders functionality, but other part of your site can be covered by the, by your activity.
We're not over reading everything. We're just over reading that pages user create the templates for, and according to the apply rules of our templates, we are covering just just part of the site.
[00:18:27] Nathan Wrigley: Yeah. So like the first thing that you do, isn't it, you have to, in the part of setting up a template, you have to make decisions about where this template is going to be.
And so the theme can be used. If needed, but if you override that with build areas and you give it conditions, which mean, okay, use this template that's going to come into play.
[00:18:50] Volodymyr Denchyk: Yes, but if you create builder's template for some page if you're, if your site for archive page four for a singular page at that page theme will not be lauded at all.
You will receive the blank canvas and everything you need, you can do. In build areas? No files, no JS files from the theme that they will not be lauded at the pages. Wherever the build areas is So that's them, there's the main thing, but yeah let's talk about the workflow of builders.
So first, yes as we talked before, you should create a template. We have a few templates that we have we have technical. We have two options during the template creation, we have technology and we have template type technology. And now we have just one technology, which is HTML. But we are ready.
Our architecture is ready for something more. We created actually this for. In the future for adding another technology like amp. Now we are not sure about this, but we have such possibility maybe not maybe. Yeah. But yeah, we are ready. Let's say like this. After you choose the technology, you can choose the template type we have now have just three template types.
It's a singular pages collection pages and other pages single or it's for posts. And. Pages for custom push posts. Collection is for archive pages, different type of archives. And others is for not one. I apply rule it's just for error 4, 0 4 page. So you should decide your type of template and you're creating your complaint.
After you create your template, you should open apply rules. And from according to the type you have selected, you will see different apply rules for different template types. So according to play rules, you should select on. Pages you'll want to apply this template. So select a specific post by ID.
You can select posts by category. You can select posts by some tags, lots of possibilities. Provocation. We have more than just possibility to select apply rules based on complaints, WordPress templates, hierarchy. We have. What's the ability to combine two different groups. So you can select the posts of specific category and then a applied rule based on user credentials.
So user should be logged in user can be not locked in user should have some capability or just by ID of the user. Also we have by rules based on the. Multilanguage plugin you have installed. Now we have created just integration with polar Lang. So you can create a condition, apply rules based on the language which you are using.
So you can create them plate for some categories archive and for some specific language. And for another language, you can create another template. But this. One option except this, we at possibility to create. I want to play it for all languages and inside of this template, based on our functionality of string translation.
We have this in production. You can create this template and it will be translated according to the language you are using in polar Lang, not just. And this is string translation inside of builder. It is not related to any multilanguage plugin. It is working with a WordPress localization by default.
So no need to use some polar Lank or WPML or other multi-language plugins. So if you create a Buhr template, You can put there different strengths for different languages here. You'll think it will be necessary. And if the customer install your template on the language with English localization, and you have this translation, it will be translated in English.
Or if it's Spanish, it will be translated in Spanish, just one template. And it's possible to have their strings for different languages. Yeah. So like this. Oh, okay. You just wanted to,
[00:23:38] Nathan Wrigley: yeah I was just gonna say, so the w we need to set up a template and we need to give it a condition when it's going to appear.
As you've just described, it could be that it has a particular post ID, or it could be a category or in the case that you've just mentioned, it might be that a certain language has been selected. And so we've then got ourselves to the point where we know. Template will come into play. What does the actual building of the template look like?
Because on the videos that I saw, the it's not what we get necessarily with a page builder. So with a traditional page builder, let's go with the example of something like beaver builder Elementor or, and so on. We, when we begin a lot of the sort of styling options and the way things will look taken care of for us out of the box, there's some, comes with the theme or what have you.
Yeah. Building, I think I could be wrong about this, but I think you're building from a completely blank canvas where decide make decisions about everything, including, what an H one tag will look like, what fonts are going to be used in a paragraph. And so on.
All of that has to be decided because of the themes, not doing anything. And so you've got to, you've got to make all these decisions. Upfront, presumably with the designer or if that's you that you've got to make decisions about what everything is going to be like, what the head is going to look like, what the navigation is going to look like, what all the fonts will be, what the sizes and the weights and the color palettes will be.
All of that has to be decided at the outset.
[00:25:10] Volodymyr Denchyk: Yes. Yes. Correct. So just blank Canva and you can it's it's freedom. That's why we did this because we don't like the approach when you have theme and you have to work here or there with some hooks with some, shortcodes try to understand I can over read this part or that part.
We just wanted to build a, let's say vertical integration system. And if you are decided to style this, the design of this page by builders, so you have the freedom, you have the blank canvas and you have possibility to do whatever you need. Yes. Is
[00:25:52] Nathan Wrigley: it possible to, let's say for example, I'm on my third build areas, website and I'm just about to embark upon my third one.
Is it possible for me to make. Make the third site look largely like the second site. In other words, could I save those templates away, export them somehow and bring them to make that a little bit less onerous the third time around? Sure.
[00:26:16] Volodymyr Denchyk: Yes. What we what'd you can do now. It isn't the, it is not ready yet, but we are working on the cloud of layouts, but not just layouts in our cloud will be.
Multiple types let's save let's sell let's explain. So in the cloud will be possible to have just Bart's off your pages. We call them like fragmental or layout. Also there can be possible to save there another category, which is a full template. A full template. The difference between a layout and template that in template, we have a group of settings which belong to template layout.
Doesn't have this layout great just by modulus and the layout, just the group of modulus the fragment of the page and the difference between layout and template that in template it, the plate is like, Full page design and you have income plate settings related to the complex. There's the second one.
And the third level eats he's the cloud for releases release, ease the full site solution. So in this, in the release, you have more than one template in there. Louise, you have global settings. You can have you can export in the future. Now it's not possible not finishing this functionality, but it will be possible.
Once you created the release, you can export it as zip archive, or you can upload it to the cloud and you can make this release private, just for you. You can share this released to specific users of our cloud, or you can make it public. Okay. Yeah. And there will be. The possibility to download this.
And based on this, create your custom design just by changing this or changing that part and
[00:28:33] Nathan Wrigley: like this. Yeah. So at this point, then this is where the. The page builder feels starts to take effect. So we now have a a sidebar, shall we say, where there's a whole bunch of options of things that you can add to the page.
And now we're into familiar territory. I'm sure for many of you. So for example, can add in paragraphs and you can add in block quotes and you, but the options here are much, they're not the same as in a page builder because. What you're trying to do is offer us the scope to pull in any data from anywhere based upon anything.
Whereas other page builders on the whole you're dragging in modules with predesigned styles. So do you want to just describe how you actually use the builder to build pages or templates.
[00:29:26] Volodymyr Denchyk: Sure. Yes. So once you open our builder mod and you will see the blank canvas and the panel from the left or the right side and what to do, what how to start building.
So first, what if you are creating them some static page, so just just select independently. Possibility to add modules. And by clicking this button add module, you can see from our, from the least of our modules what you can add our modules mainly they are reflecting the HTML text.
So one tech, one module, and we have. Types of modules. We have a modulates with a container type, so you can put inside one module and other modules, some modules they are not containers. They can be like paragraphs heading. So it's. Like this. And once you add that the module to your three, you can style them.
You can double click, but this module and the settings will be opened. We have CSS settings, nonsenses settings, and by CSS settings, I think it's, everything is understandable. Just search the setting you need and a style this module, but also we have nonsense. And among those settings, I think the most interesting setting is data variables, and it's if you saw, if you want to do.
Work with dynamic data. You are building not static data. You should get this data somehow from the database and the in build areas. We did unique, I think, logic for WordPress. Like blueberry skews, unique product. And it has of course the unique logic. So it is not liking the Gutenberg. When you have add the module and you have specific module for specific data from the database.
Like you putting somewhere module, which is showing you the post title or post content. So you have dedicated, dedicated block for that, but there is not working like that. Bulgaria is modulus. They are, let's say data source agnostic. They don't care about the source of the, of your data. They care.
They, they know how to work with the data model. So that's the difference of builders. And I think builders, because it's it's unique feature. Between data source and between data representation, we have the thing we call data model what is data model? So before you create your complicated dynamic site, you need to understand which data you need from the database, how you will get them.
How you can do this, you should create your data model and your data model can be created from the data various. We have specific setting there, the variables and we have different types of this variables. The main type is deck where the database and for these database query, we we created the graph QL syntax.
All things which you have in the database, you can get by writing the draft Gail query. Wow. And this is graph. QL is just about getting some objects from the endpoint and not all objects. So if you need from a post, just some fields, just title, maybe some metadata. So just write the query to get this.
You don't need post content. You don't need feature image. So don't write the query to get this. If you need few fields just use them. So our graph QL is helping you to get everything you need from the database. So you can get posts. You can get terms, you can get users, you can get a metadata.
Also we created integration with the ACF. So all ACF, custom fields it's possible to get from different locations. You can get ACF related to post, to term, to user, to a options page it's also possible to get. And so just create your data model just by getting data you really need on this template.
Okay. That's the first first type and the main type. And then after that, if you. Got there's data from the database and that the format of the data is not good for you. You can use another thing. Very cool thing. It is expression, language, expression, language is we actually. Yes, the symphony expression language, there is symphony component, very popular, very powerful, but we also enhanced this.
We add lots of functions. We implemented there arrow functions, closures. So it is possible to now work with functional, like for each. So you got something from the database and in the, for each cycle, you are. Modifying every element of the array by some custom function, which you need. So you can uppercase lowercase, you can join something or you can delete something from the array based on its position or based on its value.
You can combine, you can join to erase very powerful. The
[00:35:37] Nathan Wrigley: principle here really is that your. You're able to do literally anything. If you're willing to put the required time in to figure out how to make that anything happen. And I think that's probably one of the biggest differentiators between yourself and the page builders that we've been discussing.
The idea over there more is to speed up the flow right off the bat by just of. Having pre-built things you've got limited options, you can't drag everything you would like out of the database, but you can probably get away with most of what you want, the post content and the featured image and things that you've described that can all be taken care of.
And probably things like ACF fields, where you're offering the option to literally put anything at all in the database. So long as you're prepared to go through the. The barrier of learning, how the UI and the workflow for build areas works. And I'm just curious as to where you feel your target audiences, is this really firmly in.
And the camp of people who would describe themselves as developers, or do you have customers who are like fresh to WordPress and have just explored through your UI? Because I noticed some of the marketing material that you've got, it feels like your you're able to take beginners even through this process because they don't have a fixed idea.
Of what ought to be possible in a WordPress website and what the constraints normally would be. And you've got the, you got the ambition of taking beginners as well as developers along for the ride. Yeah,
[00:37:18] Volodymyr Denchyk: yeah, correct. So we have two types of our potential customers and we have really, we have use cases where, like you told the people who didn't was familiar with the WordPress at all.
They just want to start website development. We showed them build areas and they did few projects on the build areas and now they are it's good. They are happy with this tool. They feel the freedom. They know of course they had to learn the north press database. They had to learn the WordPress templates hierarchy.
And that's what. Any way you should do, you should know you shouldn't have this knowledge in builders. You should understand what are you dealing with? Yeah this tool is can be used by new newcomers. Let's say to the WordPress world, but other, a other category of the user is really profile.
Which no nos, which know a lot of about all we were talking about. So they know what is the version control system. They know what is, let's say called delivery system. They know the structure of the database. They know the structure of the, of some plugins, which are adding something to the data base, like ACF and at the books and other things.
So they have everything this, we we are not forcing them to, we're not limited. We're not forcing. We are not limiting them in their design. So main logic is to create, get from the database. Everything you need transform eat according to your needs. And only after you have the belief, you'll finally, you will get that.
And Jason object, like your data model, you will, you can observe this data. You can see that here. I have this here I have that. I have array with objects and every object has four fields, title, content image. And I don't know let's say three fields, staple, content and image. And I after that I have this model.
I am creating. The view part. So I'm adding my modulars to the content area. And in this is, I am telling that I want to create the collection and the source of collection will be my module. And every element inside of collection should work with different fields of every. Oh dear in the model. So I am adding some paragraph and this paragraph should show me the post title and another paragraph.
Let's say row HTML should show me boost content. Another image element image module should show me. And it will be working after some time I can save my layout somewhere in the cloud, or I can just export this and this layout we'll be aware of the data model. This data model will not be tied to the specific location of this data in the database.
That data model will be just obstruct object with obstruct, let's say obstruct array with objects and this objects should have this, the three fields. So after I saved my layout, I in the future, I can use it on another project and another project, for example. Don't need to show this design based on my posts.
I want to create these design based on some ETF repeater. And this I say, repeater also has this, my three fields, title, description, and image. So after I input this layout into another project and I, eh, and that another project, I am creating data more. From the different source, this source can be even a external API request, but the output of this data model, same array with the objects and object has title, description and image.
And my layout will be working. I don't need to change anything because my data model is the same. I don't care about the source of the data that the other project that there's data is. They take him from the other location. But finally, my data model is the same that I used in the previous project. So this is the, that this is the power in the cloud of layout, or will be it's actually out that and description, which data model.
To create to get this layouts working. And this layouts will have to come fix one with the stating data, just in order to make preview, to see how it's looking. And another is dynamic part. So you can read in description, which data model you need to prepare and put this data model as the source for that layout.
And this layout will be working with the order data model doesn't mean. And above the source of the data like this. Yeah,
[00:43:04] Nathan Wrigley: Amazing. The, so really the intention would be that obviously developers can make incredible use of this more or less. If you can imagine it, you can build it. You may have to, go through some learning curves.
But also if you're just starting out, you could definitely get yourself up and running. Definitely going to be a learning curve. It's not just drop right in and start building off the bat. As you said, there's going to be some sort of prerequisite to understand how the templating system of WordPress works and where things are stored in the database.
And so on, I'm curious. In the future, you are, you're trying to really take the lifting of what at the minute is the realm of third party plugins and build that into build areas. And I'll just mention that at the moment you, you mentioned that you could do faceted search, so things like search and filter pro.
Or a grid build adult WP grid builder. I believe it's called or facet, WP. Those kind of plugins that kind of functionality is already in. So you can do the fasted search inside the builder, but on your website. And this may not be the case when this podcast, as perhaps they'll have gone live, you're also.
Saying that you'll take over the burden of creating custom post types as well. So you'll be able to put metadata in through the builder. And also there'll be a built-in form module at some point, and also amazingly a built-in email template builder as well, which is really.
[00:44:42] Volodymyr Denchyk: Yes. Yes. All this we have in our roadmap and some of the things you told them right now, it's already done.
So about, let's start about the physical. Filtration. So it's already done. So in your graffiti, I'll query you by specific syntax. You can inject that data from the get request from the post request from cookies. So a and by combining with farm functionality. So you are creating form and by submitting forum data from this form are going to the.
And get to the Europe part of the URL. It's get parameters and they'd get parameters you can use in the query to the database in graph Gale. So by default, if you don't have this parameters, you will get default query the fourth quarter with default our demands. So you will get just, let's say all posts by a specific category with pictures and you will show them on your content, but by clicking something in your sidebar, in your.
Form, you want to limit something based on some specific math or based on some terms, something like this, and you can inject this parameters in the query. So by clicking the submit button all this parameters will go to the. And get request. And from the get request, they will go to the query, to the database, to the graph, kale and draft Gail will return you your filtrated data.
So this part is already implemented. The second part is about in the probation almost. We have two types of forms. First, it just simple simple form like just a forum and show them all component. So you can create simple forms. We just add the hidden field action and it will submit data to the backend.
And if you have some requests handler on the backend, it will be processed. But this is not. I think we are working on this specific module, which goals smart form, and this smart form will give you, gives you a possibility to make cool validation, make data transformation, make, or lots of things. And also very interesting thing that data will be submitted on this specific endpoint.
And on that end point, we are adding, let's say form submission actions and it will be possible to configure the submission actions in the builder mode. They can be combined with the conditional logic and conditional logic. We also implemented. So this conditional logic can be used to. Display some modulates on the page, based on some conditions, based on our data model, a conditional logic is working based on a data model.
If you have something in data you can make condition based on this. This form submission actions, they can be. At it more than once submission action can be added and they can edit with conditions. So if a user looked in, I want to use this form submission action. If not, I want to use another.
And I can create different chains of this submission. So this is almost done. And a yes, in our roadmap, we wrote that we wanted to add functionality of custom posts, adding custom fields adding. Yes, because we found that in our release one, we have everything re. And we want to export this to from staging server, to the production server.
We have a gap that on the production server, probably there are no such fields created. I dunno, maybe by ACF or method books, and we should accept our release theme. We need to export something else. And theoretically. There is problem that you accept our release. You should do some other operations of the production server in order to get this design in the release working.
So in order to fix this, we want to, we need to add custom post creation and custom fields creation in side of build areas and be responsible for. And after we add this functionality, everything you need to. For the production, Sarah will be in this release config.
[00:49:45] Nathan Wrigley: Yeah. That's an amazing road map.
I think you've done a remarkable job of trying to describe in words, what is significantly easier to understand in practice? The complexity here. Just breathtaking, essentially if you want to be able to manipulate every single bit of what's on your website and you don't want to be constrained by what the theme gives you or what the page builder gives you, then this is going to be a really good tool in your arsenal.
The. It's also going to cut down, hopefully on the sort of bloat of your webpage, you're going to be only processing the things and displaying the things that you really want to show, which I guess in these days of core web vitals and things like that, this can only be for the better the question I have around.
The pricing model and the way it is structured. I don't really have much understanding of, you mentioned a sort of pro version, but I don't know if that's already in existence and what the pricing model is or what you're intending to do around pro. So let's just, w we'll round off the podcast with the discussion about what the pro version may look like or what it, in fact is.
[00:50:58] Volodymyr Denchyk: Profession it is not visible to everyone and it's 99% ready. And the next step will be demo site where it will be possible to play with the pro version, but without possibility to buy it and download it to your web. Okay, next step, because we want to Polish it and we wanted to make it cool.
And when it will be possible to buy it we want to eat to be worth to buy. Let's say like this about their pricing model. Now I can, we were thinking about this. Just one thing I can tell that we will have lifetime deal, but this lifetime deal will not be for unlimited site. Sites will be for fixed sites and this another option.
It will be that it will be possible to buy just necessary amount of licenses, which you need. To not be some limitation. So you can buy five sites, you can buy a license for 50 sites, or you can buy lice for 100 sites, right? So if you need seven licenses can do this. If you use this seven licenses.
And after that you need another. Five or three licenses, you will be able to extend your license to the number of licenses you need. And as many licenses as you buy the price for one license per one, license will be decreased, and decreased. Okay. I'll just this I can tell right now.
[00:52:45] Nathan Wrigley: That's okay. It doesn't exist yet. It's okay. It's fine. It's a work in progress. So if any of this has captured your imagination, if you've been interested by this and you feel, wow, that sounds like the complicated stuff that I want to be getting involved in, then head over to build areas.io, B U I L D E R U S dot I O.
Just as a final question. Volodymyr what is a good way to get in touch with you or anybody else to do with build areas? Where's the best way to reach out to you?
[00:53:21] Volodymyr Denchyk: We have yeah, thanks for the question because I forgot about this. I think the best way is to join our Facebook group. We have we have Facebook group.
It is we have also our YouTube channel. We have our website, there is a. Or just the right ass on the email, support the at build areas, IO so like this, but I think the best way to, to watch for for the build areas is to join our Facebook group. Okay. And the old news we published that there.
[00:54:05] Nathan Wrigley: You can find links to the Facebook group on the docks, I believe dot stun the
[00:54:12] Volodymyr Denchyk: dogs on the main website and the,
[00:54:15] Nathan Wrigley: and actually just before we finish it, I would like to point out that there is a lot of documentation that the guys have. Added. You may find that you don't actually need to reach out to support.
If you go to docs.build areas.io then you're going to be, you're going to be shown a whole load of documentation videos, and text-based and image-based tutorials on how to get yourself up and running. It starts at the very beginning of installing and terms, glossary and then getting into the more complicated things.
So that's maybe a good place to go. I will link to that. In the show notes. Volodymyr so yeah, build areas really interesting project, really fascinating. I hope that in the future, we get to chat once more and talk about the new features that have been added in. But for now, Volodymyr thank you so much.
Thank you. I really hope that you enjoyed that. It's always fascinating to talk about brand new WordPress products and services. And this certainly is a bit different, quite a difficult topic to get over in a podcast because there's so much stuff that you need to see visually. So maybe go and check out the build areas website.
There are going to be links on the post and you can find [email protected] and go and search for episode number 278 in our archives menu.
The WP Builds podcast was brought to you today by goDaddy Pro the home of managed WordPress hosting. That includes free domain SSL on 24 7 support. Bundle that with The Hub by GoDaddy Pro to unlock more free benefits to manage multiple sites in one place, invoice clients, and get 30% off new purchase. You can find out more by going to go.me forward slash WP Builds, that's go.me forward slash WP Builds. And we do thank GoDaddy Pro for their support of the WP Builds podcast.
Okay. We will be back next week as it was an interview. This week, I'll be chatting with David Wamsley next week. We'll be doing another in our WordPress, a business boot camp series. I hope that you join us for that. If not, maybe we'll see you on Monday for the live show. And don't forget if you want to keep updated WP Builds.com forward slash subscribe.
So until next week stay safe. I'm going to fade in some cheesy music. Bye-bye for now.