Note: This transcript was auto generated then some poor soul sat and listened to it, and followed through correcting any mistakes they spotted. Please however expect human error and shout if you spot an issue. Email: lee [fancy curly symbol] trailblazer.fm.
Verbatim text
Lee Matthew Jackson:
Welcome to the WPInnovator podcast, the podcast for web designers and design agencies exploring the world of WordPress and online business. And now your host, Lee Jackson. Hi, and welcome to episode number 51 of the WP Innovator podcast. This is your host, Lee. And today it is just you and me. I should. Should have been a rapper. Or maybe not.
Lee Matthew Jackson:
Okay, today we’re going to be talking about our WordPress website build process. So we’re going to break down all of the different stages, tell you what we get up to, talk to you about the different things that we kind of need to remember and make sure that we cover essentially so that we don’t hit a point during that process where we either get screwed over or we miss something and everything just falls apart. All right, so we’re going to break every single step down. And what this will form a part of is for the future will be an online course that you guys will be able to get access to and we’ll be able to follow through the steps. We’re going to be giving really cool documentation as well to help the process. Basically, we’ve got all sorts of checklists internally that we really need to prettify, make look really nice, and then put into some sort of online downloadable course. So this is one of those things that we said is going to come up soon. In the meantime, let me just, for the next 20, 30 minutes, however long this takes, just tell you what we get up to and hopefully you will be able to pick up some brilliant things from our process that you guys can apply to yours.
Lee Matthew Jackson:
And you know what, if you think we do something a little bit skew, if y, then why don’t you tell us, head on over to the Facebook group leejacksondev.com group and let us know. Hey, guys, have you ever thought of doing this? Or hey, why do you do that then? Have you not thought of doing it there? We would love the feedback. We’re a great community of designers, we’re a great community of WordPress developers, so let’s help each other out. This process is something that we’ve evolved over time. It works for us. There’s probably things that we could do better we’d love to know and hopefully what we’re getting up to will be able to help you. Now, we’ve built so many websites over the last eight to 10 years, both in other agencies and also with Lee Jackson Dev. So this is definitely a tried and true process for us.
Lee Matthew Jackson:
Let’s rock and roll. All right, so we always are going to hit in there with the briefing process. So we’re going to receive some form of a brief and depending on that brief, we then need to take some actions. So first of all, if you’re going to receive a brief that is, you know, two paragraphs long and very, very vague, first alarm bells ring for us. We know we need to get a more detailed brief. So at that point what we will do is encourage the client to get involved in some sort of paid discovery process where we will talk to them about what their needs are and create a full brief for them. Okay, so that would be the first range. Now if we’ve received a brief that is pretty good and pretty much meets everything that we would need to know for the quoting of a WordPress website, then what we will do is we will reverse brief that in our own words.
Lee Matthew Jackson:
So that means we will take that brief, be that brief text document from them, and some conversations with some notes, and we will then put back to them a document not too long, maybe two or three pages long with maybe a couple of diagrams of our reverse brief, what we believe they want, including anything and everything that we need to cover, maybe like data sets, etc. So that reverse brief would go to the client, they will read through that and they will give us a thumbs up based then on that and maybe some other conversations. What we might do is then list out in a little bit more detail all of the pages or layouts that we might need. So that would be things like we’re going to need a homepage, we’re going to need a blog section, we’re going to need a search page, we’re going to need a contact page, we’re going to need a team page, and we’re going to need a portfolio page. There you go. I think I’ve described pretty much every theme on ThemeForest, but you know, that’s the example. We would list those out, those sections, etc. And possibly even go as far as capturing what sort of fields they might need as well.
Lee Matthew Jackson:
So sometimes in a brief we might actually be given a spreadsheet of data, which is super useful. So we will then make sure that we have got a list of those fields. Even if it’s a case of we will say on our reverse brief that we will cap each data type at a certain amount of fields. So we might say we’re going to give you the portfolio post type and we’re going to allow you to have up to 10 fields. So we’re going to cap those fields at 10 and we might even say of any of the following data types as well. So it might be a select box, it might be a relationship, etc. Just so that we’re controlling what the client can expect. We don’t want the client to try and come up with some complicated multi select field that integrates with all sorts of different areas, etc.
Lee Matthew Jackson:
So we’re trying really well in this reverse brief to capture everything they want and also cover ourselves when it comes to the quoting process and the delivery process. All right, so we’ve got this reverse brief. People are happy with it. We have kind of a shared agreement that this looks like it’s the way that the client wants to go. We’re going to use this then to, to quote. So during the quoting process, what we will do is we will break it down into line items. We don’t necessarily need to put prices on those line items, but we will certainly put specific kind of steps or milestones into the quote where we’re breaking down that reverse brief. So that reverse brief document becomes a part of the quote package.
Lee Matthew Jackson:
We will then have lines in the quote that says, you know, we will build the base theme, we will create this data type, we will create the following fields. We will design and code so many layouts. Here are the layouts as in listed, etc. So that we’ve got a full breakdown of everything that would be required. Then accompanying that quote. What we’ll also do is provide a Gantt chart. So we will come up with some sort of time estimate of how long we think everything’s going to take. So that will start from things like contract award, going through to the design process, QA sign off of that, then moving on to the coding process and testing and training and all of that sort of stuff.
Lee Matthew Jackson:
And that Gantt chart really helps the client visualize what they can expect, how long they can expect the entire project to take. And it gives them that, you know, it gives them that realism of, okay, this website is not going to be live in two weeks, because that is just insane. But also they can see that they are going to be looked after through a really good process. So they can see when everything’s going to kick off. And as long as everybody meets those milestones, those targets, etcetera, then they know when they’re going to go live as well. All right, so once we’ve given them this package, this quote package of the reverse brief document, the actual quote and the Gantt chart, we’re then going to go ahead and get sign off on that quote and we’ll usually do some sort of online signature, so you can use something like signable, etc. And then we’re going to ask for the 50% deposit. So as part of all of our conversations, right up from the very front, you know, we’ve been very open with our clients, explaining to them that they need to expect to pay a 50% of the bills.
Lee Matthew Jackson:
That allows us to kick off the project. Okay, now if the project is humongous, it’s like, I don’t know, a 20, 50 million pound contract, then obviously we probably couldn’t expect the whole 50%, but we might at least agree some milestones where we’ll say we’re going to take 25% deposit and then when we reach this point, there’s going to be another 25 and then another 25 and then another 25. And that could be milestone based or that could be time based. So time based means that regardless of what milestones have been reached, you could be getting your payments at specific dates no matter what, or milestone based would be that we’ll be getting those extra 25% every time a specific milestone has been reached on the overall project. All right, so that’s our initial briefing process and quoting and getting that business in and getting the deposit in. So part of the Gantt chart is that the deposit will have cleared and at that point, when that is checked on the project, we know we can then get into the next stage. And that is going to be wireframing. And wireframing is so freaking important because that allows us, in advance of even getting into Photoshop, to agree what all of the layouts are going to look like.
Lee Matthew Jackson:
It’s like the white newspaper version of how the site is going to look, feel, operate, etc. So it’s not the design, but it is at least the structure. We know where the header is going to go, we know where the menu is going to go, we know what the site map is going to be, the structure of the site, we know where the specific widgets need to be displayed, we know what’s a slider. We can wireframe the user journey from page to page. So if we do have a portfolio section, is there a portfolio grid on the homepage? And we can then wireframe what actually happens. This is interactive wireframe at this point. We can wireframe what actually happens when we click on a portfolio block and that then takes us off into a different page. And then what happens when you hover on something and there’s all sorts of tools that you can Use for that, we essentially use the online presentation tool from from Google.
Lee Matthew Jackson:
It’s brilliant and it gives you the ability to switch to a slide if you click on something. So hey, you might as well use that because it’s free. But there are also some other amazing wireframing tools as well that you can use out there. We’ll probably pop some links into the show notes as well to help you out. So the idea here is, is that we’ve now sent for review to the client an online representation of how the site will be structured, where everything is expected to be and what the behavior of everything is also expected to to be as well at this point, this allows us also to argue a specific point. So if a client says to us, yeah, but I thought it would do X, Y and Z, that allows us as the developers as well to go, well, that’s going to be really hard to code. That wasn’t what we all discussed, that’s not in our original notes and that would more than likely be a change control. So that allows you, before we’ve even got to the even more costly process of actually designing stuff and then getting to code, we can actually right from the get go say, okay, that is going to cost more.
Lee Matthew Jackson:
And that can come either from the contingency because we’ll always add some sort of contingency to the quote of say 20 or 30% contingency essentially means, oops, one of us missed something, either the client or us. And hey, there’s a contingency fund we can draw from. So we might agree that that would draw from the contingency or we might just simply agree that that is going to be something that would be a phase two item. That is the beauty of wireframing. No code has happened. We’ve not had our design team doing designs and having to change things, etc. Or we’re not leaving anything to interpretation just based on some flat JPEGs. We’ve actually created an interactive wireframe.
Lee Matthew Jackson:
Now wireframing as well is important in the back end as well as the front end. So yes, wireframing, the front end of the website and how we expect that works both in the basic mobile layout and also in the desktop layout is super important and obviously we’re going to get sign off from that before we move on to the next stage. But also wireframe wireframing backend functionality of things that are a little bit more complicated than just adding a new page. So we will very often wireframe post types that have complex relationships with each other or that have multiple fields. We’re going to wireframe what the column structure is going to be. We’re going to wireframe things like filters. We’re going to show maybe an edit page because they’re going to want some custom fields that don’t necessarily exist in say, ACF or pods and we need to create that. So we are going to wireframe that up.
Lee Matthew Jackson:
So nothing bog standard like how to add a WordPress post, that’s pretty easy. But if there is going to be something that’s got a whole load of extra custom fields and we’re going to want to show what that layout looks like before we start creating all of those meta boxes. It’s so important therefore to get that wireframed up as well and signed off. Okay, we’ve gone from the briefing process through to wireframing. We’ve got the wireframe signed off and now is the time to design. I don’t know why I keep rhyming things today. I don’t. Probably because I’m excited.
Lee Matthew Jackson:
Anyway. Design. This is the design process. So first of all, we will want to collate all of the existing brand assets. So in most WordPress builds, we’re not branding the client as well. If we were, that would have been picked up right from the get go and that would have become part of the process as well. But at this point we are simply building, designing and building a website for an existing brand. So we’re going to need all of those brand assets.
Lee Matthew Jackson:
So that would be logos, that would be the brand guidelines, any colors, pantone colors, all of that sort of stuff we want to know about so that we’ve got all of that information prepared. We’re then going to be reviewing the wireframes that we have. So as the designer, he now has both the brand assets, the brand guidelines and the layouts of from the wireframes that have all been agreed. So he knows what content he’s going to be playing with. He or she obviously knows the color schemes that he needs to be working with. He knows and understands the brand that they’re going to be working with as well. And that point they are then going to create all of those pages and layouts that have been created in the wireframe. Now again, let me stipulate here that this would only be the front end stuff.
Lee Matthew Jackson:
Anything we’ve wireframed in the administration area will simply adopt the look and feel of the WP admin because we’re going to be using standard WordPress meta boxes, fields, buttons, etc. So we don’t need to design the backend. That’s all sorted by the existing WordPress architecture. But we are designing all of the front end. And normally as well, we would be given at least some content from the client because it’s usually better to show actual content in a design that the client actually understands and comprehends versus showing them lots of lorem ipsum, you know, the Latin, the fake Latin that people show in their designs. Because with fake Latin you can’t necessarily understand the context and you may make some assumptions. So we, we will always try if possible. It’s not always possible.
Lee Matthew Jackson:
We will also always try if possible to get actual real content. And then we will lay out those pages. Usually on average there’s about five to six different pages that are laid out. And we as an agency will tend to use Photoshop because we work with other agencies. So it will more than often than not be Photoshop that everybody’s working with. And also for our design process, we may not necessarily have to do the design that actually may go back to the design agency based on the wireframing. That’s all being agreed. They will do that and then pass that back to us or we’ll have our own internal design team doing that.
Lee Matthew Jackson:
Regardless, the process for us is still the same. There is a block of design time either done by the agency or by us with our guys. Okay, so we’ve created the designs, all those layouts based on the wireframe and we’re going to do a round one review. We always limit designs to just two rounds. So round one review is those designs are going to go over as per the wireframe. Now the reason we’ve wireframed and then designed is that’s stopped us from having to create maybe three or four concepts, as it were, for a new site. We’ve already done all of that layout work in the wireframing process, so that all we’re doing here is showing the actual design based on the brand assets and the wireframing. So we’ve got round one, we send that, we then receive our amends, we do a round two review, make a list of amends, and then we then submit that those final layouts of for the final sign off by the client.
Lee Matthew Jackson:
So the client therefore knows and understands that they’ve hit the end of round two amends. If there’s some spelling mistakes, sure, obviously we’re going to fix that. But if they’re then going to say, well actually I want this moving now to over there instead and I want to change all of this other stuff, then that’s going to have to form a part of the contingency budget where we’re going to be spending a little bit of the contingency on some extra design time. And also we’re going to explain to the client as well that if they’re going to do that and that adds another week’s worth worth of design to the process, then that obviously is going to move everything else that we’re doing on by a week. So their go live date is going to shift unless we can save some time elsewhere. All right, I’m going to apologize, by the way, I have a very strange accent. If I say process or process at random, that’s exactly the same word. Just so you know.
Lee Matthew Jackson:
I guess I’m very conscious of a US audience and I have a UK audience, and half the time they’ll be like, what the hell’s he saying? What’s process? Process means process. Process means process. Okay, so. And my brain just squirts randomly out whichever one. So I apologize. All right, so we’ve, let’s recap where we are. We’ve got the briefing process, we’ve gone through, we’ve got our initial brief, we’ve taken our deposit, we’ve done the wireframing, we’ve now done the design, we’ve have. We’ve had our two amend cycles, we’ve had sign off, we’re going to hit code time now.
Lee Matthew Jackson:
So this is where we’re going to be doing all the code and we will first of all create the base theme. And that literally means absolute base theme framework. We’re not even doing any of the HTML, nothing like that. We’re just installing the base theme and then we’re getting the backend done first. So the reason we want to do the backend first and get all those fields put in and the post types, etc. And all of the logic done in the back end means that we can all test that internally to make sure that it works. If I add some data, I know those fields work. If I add a relationship, I know, I know that relationship field works.
Lee Matthew Jackson:
And I can check in the column that maybe in the portfolio column, maybe I want to be relating a post type or something to that. I can see that that also shows up so that we know that we’ve nailed all of the backend functionality. What we will then do, once all that is built is then start to bake in all of the HTML and all of the loops that we need to do, that’s WordPress loops to show all the data, etc. Into that base theme framework that we’ve done and that will then cover all of the layouts. So you’ve got your front page, you’ve got your again, your search results, your 404, your blog listings, like your archives, etc. Your actual single posts. All of those good stuff. All of that then will be done.
Lee Matthew Jackson:
And how we do this is we do this on a page per page basis. So we’ve already agreed all the layouts in the wireframes which have then been designed. What we will do, our job is to therefore create all of those page templates or that structure that will work within WordPress and then to replicate exactly how it looks with that exact content from those designs so that we can enter into a QA process. So we have a homepage, we will have the slider from the design, we will have the portfolio grid from the design with the actual content that the design had and the text, etc. So that we can get to as close to pixel perfect as we possibly can. A built designed WordPress theme that looks absolutely pukka that we know can be. Sorry, excuse me, I’ll leave that in. So that we know that whatever has been designed can be recreated perfectly inside of WordPress A by us, therefore also by the client.
Lee Matthew Jackson:
Okay, we then hit the qa. So we’ve done code QA quality assurance and we’re first of all going to do our internal qa. Internal QA means that we are going to look at all of the pages we’ve created in WordPress and compare them to the design so we can make sure that things, the paddings, heights, line heights, all of that is all as per the designer has stipulated, etc. We’re going to test that internally. There’s three of us that will do cross checks on all of the different pages. Excuse me. And then we will use freedcamp to create a list of QA issues. So for example, we might see the padding on the book button is incorrect, or we might see that the vertical alignment of some text that’s within a square image is actually maybe it’s too far down and that needs to be resolved, etc.
Lee Matthew Jackson:
So we will create all of those internal QA lists and action them internally as well. So that is something that has been accounted for on that overall project. So remember we talked about the project, excuse me, project right at the very beginning where we’ve said we are going to put down so long, so long for code, so long for QA, etc. So that has been accounted for. We will then make sure we’re testing as well on multiple devices. So we’ll normally be using browser stack for that. That allows us to replicate iPhone, Android, iPad, and also obviously multiple desktop environments to cover the major browsers. And we will be making sure that nothing looks absolutely horrific.
Lee Matthew Jackson:
And the purpose of the QA internal QA is really to avoid frustration for the client. Instead of us just building everything, thinking, yay, we’re probably good to go, and sending it to the client and letting them find everything, the internal QA allows us to find as many things that are really blatantly obvious to us and we can fix those before it then goes to the client. Disclaimer though, it’s just like reading your own work, isn’t it? If you write a sentence and then use like you read it back to yourself, sometimes you’re potentially going to read back what you think you’ve written and not spot the mistake. So, yes, the internal QA at least avoids some of the big glaringly obvious things, but there are going to be the odd thing that the client is going to pick up on. That is why we then have the client QA process. So this opens up those specific pages. We will send the page that correlates with each design and then say, hi, here is page homepage. Here is a reminder of the graphic that was signed off by you for the homepage design.
Lee Matthew Jackson:
Please can you compare and test and make sure you are happy with this look and feel. They will then obviously test that and what you will find is somebody usually has an environment that you were not anticipating. So a good example for us is someone had Internet Explorer 11 on a Citrix environment, which actually can create a minor problem. At that point we were able to push back and say, well, that’s a real edge case. We can’t support every single unique operating system setup. And actually they were able to fix the problem for themselves. It was actually an internal IT issue with regards to caching, etc. That was causing their problem.
Lee Matthew Jackson:
But at least be prepared for the odd issue which isn’t actually created by you guys. It’s actually created by some wacky setup that some clients may have. And that’s fine, they’re all fine to have those setups. But just don’t get caught up in trying to make everything work for everything. I tell you, it’s impossible. We’ve tried. Okay, so the client testing will come in and what we’ll do is we’ll open up freedcamp for them to come in works just like Basecamp for them to come in and list all of their QA issues as well. And we will then go through and close all of those QA issues.
Lee Matthew Jackson:
So it’s really important that we remind the client that they must give us all of their QA issues by the date that is stipulated on the project. So that if they’re late, that will therefore have an impact on the delivery date of the overall project. So most clients will make sure they’ve got all their QA in before their date. They need to. We will then action all of that QA and make sure that everything is fixed, everything is ready to go for the training date. So now we go into training and usually training is online. We’ve got clients all around the world. So as much as I would love to travel to San Francisco or to Australia etc.
Lee Matthew Jackson:
It’s not always doable for budgetary reasons. So we will do the training usually using Zoom US. It’s brilliant service, very much like GoToMeeting, but a snippet of the price. And we can do screen sharing. We can either share their screen and control their screen and allow them to do some sort of interactive training, or we can just simply allow them to watch and record at the same time the overall training. Now the way we do training is we’ll do a kind of train the trainer scenario in most companies. So first of all we will train the main administrator, the person who is responsible for setting up things like the users accounts and all those sorts of things and being able to set roles and all of that jazz. So we’ll make sure we train that person first, but then we will train the different departments.
Lee Matthew Jackson:
So maybe we will train the marketing department who want to keep the portfolio section up to date. And we will train the, the main person in that company or in that department who will be responsible for that department and responsible for training other people within their department. So it’s really equipping people within a company on how to do something so that they can then equip other people in their team and also new people coming in. Because one of the issues you may have is if you just do blanket training to one person, there’s going to be lots of other people within the company that don’t necessarily know what to do, that one person can’t remember how to do everything. Whereas if you’re just training the marketing person for the bits they need to do, they can easily make sure they’re training other people as well in their company. Which means if a, if A company’s got, say, a high, high staff turnover and somebody’s leaving. There are at least other people who have been trained by that trainer. Even if the trainer leaves, you’ve probably got someone to replace them, so you’re minimizing on issues.
Lee Matthew Jackson:
There’s. Okay. Once we’ve completed the training, we will also package up videos for each and every one of those sections. So we usually use Snagit, or if the client’s happy, we will actually just record the overall training and then give them a copy of that so that they can watch and rewatch that and on into the content phase. Okay, something very important about the content phase. We are now handing them access to the system. They can start to add in their content. But what we are also doing at this point is invoicing them for the final amount.
Lee Matthew Jackson:
So don’t be surprised because a lot of people tend to be. It’s really important that at the point of them entering in content, it is your time to invoice. You have delivered everything you have said you would deliver. You’ve gone through that entire process. You’ve given them the training and you’ve equipped your client to start to put content into their new website. That is the point. You can invoice and expect the full and final payment because it does not matter how long the client is getting to take to put in that content. If they take a year, that is their prerogative.
Lee Matthew Jackson:
They can take as much time as they want to enter the content. But because you have delivered what you have promised, you therefore deserve to and should be paid the full and final amount at the point of them entering in their content, et cetera. That is the beginning, not the end. Because I have seen clients take six months to a year to finish off filling in content. That’s not because they’re lazy or anything. It could just be because they’re a big company. It’s very hard for them to make internal decisions as to what sort of content needs to go in there. There could be pressure from management in other areas or people who need to sign stuff off.
Lee Matthew Jackson:
And all of that is unfortunately not our fault or our responsibility. That is the client’s responsibility. Anyway, we’ll have sent the full and final amount invoice and we’ve then handed over for the client to input all of their own content. And what we will also do is encourage them to remember, hey, look, if you can get all of the content done by this date as per the agreed project schedule, then that’s going to allow us all to make the site live on the X. Why? And everyone’s going to be happy and we’ll have met all the deadlines, etc. But now it’s over to the client. The client will start adding content. Obviously, we’re going to be on standby because there may be the odd QA item, odd bug that nobody noticed.
Lee Matthew Jackson:
We didn’t. They didn’t. And we will then quickly fix that. That is understandable. Don’t feel down if you spot the final one, but remember, if that’s fine, you can still invoice that final amount. Because with any project we’ve done, we’ll always say, of course you’re going to get a year’s warranty on the code as well. If there is a. We’re gonna solve that bug.
Lee Matthew Jackson:
So if a client finds a bug in six months time, that’s fine, we’ll fix the bug. I mean, to be honest, that doesn’t happen because we’re really, really careful on what we do. We don’t want to have to be coding for months on end fixing lots and lots of bugs. But if something does come up, because we’re all human, we’ll all make mistakes, then we’ll fix it then. But that just certainly doesn’t mean that we can’t invoice. Okay, so we’ve got our content. We are now ready for go live. Let’s at this point just do a quick recap.
Lee Matthew Jackson:
We’ve got our brief, we’ve got our initial brief. We’ve reversed, we’ve got sign off on that brief and the project schedule. We’ve taken a deposit for 50%. Check. We’ve done all of our wireframing of the front end. So that’s all of the layouts. We’ve got sign off on that. And we’ve also wireframed any complex back end functionality.
Lee Matthew Jackson:
Check. Based on that, we’ve done our design, we’ve done two design rounds and got that signed off. Check. Which then takes us into the coding process. We’ve made our base theme, we’ve done all of the backend functionality to make sure we can get that to work. We then do all of the front end beautiful look and feel, replicating the content from those designs. Check. It gets over into an internal QA tested on multiple devices.
Lee Matthew Jackson:
Check. We’re then going to send that over to the client. We get the client to do qa, we resolve any issues, get final sign off on that. Check. And enter into the training where we’re training trainers of specific departments. Check. And we hand over the actual access for them to go in and start entering their content whilst with a smile sending that final invoice saying, okay guys, time for you to pay up and please try and enter in your content as quickly as you possibly can at that point when the client has entered all of their content and obviously paid your invoice because you don’t want to make it live until that’s happened, we can now go live. Go live process is simple.
Lee Matthew Jackson:
Again, we’ve got an internal checklist because there are some things that you need to remember. But what we will do is we will then transfer that site to the live server on an agreed schedule. We will more than likely transfer it to a staging environment on their server first so there can be some more testing to make sure that there are no issues with regards to the PHP version, MySQL database version, all of that good stuff or RAM or resources that are available, and then we will flip the switch to make it live. Some things to remember though is always remember, have you unchecked the discourage from search engines? Because if you’ve transferred from a dev server to a live server, you will probably have ticked that box saying tell the search engines to go away. You want to make sure you’ve unchecked that. You also want to make sure you’ve done things like 301 redirects as well. So if there was an old site before the new site, and there was a whole ton of pages that did exist that no longer exist, you need to set up all of those 301 redirect. What we tend to do is we say here is redirection tool from WordPress to allow you to enter in all of the 301 redirects if you wish, Mr.
Lee Matthew Jackson:
Or Mrs. Client. But if the client would rather us do that, then we will charge for that and we will actually create reports of their old site, compare that to the existing site, and then we will build all of that in for them as well. Okay, we’ve flipped the switch, the site is live, we’re all happy and ready to rumble and we will make sure that we as a company are staying on standby. And this is also on our schedule to be on standby for 24 to 48 hours depending on the size of the site, just to be there in case there is an urgent issue that is spotted. Maybe there is one final bug that got past all of the gatekeepers and somebody spotted that now the site’s live. There is something that’s not quite right or maybe something goes down we’re available to be there to either roll back the old site quickly if we need to, or to be able to quickly fix a book or offer some advice, etc. And that is the entire process.
Lee Matthew Jackson:
So if you have any questions, come along to the Facebook group. It’s Lee JacksonDev.com group. Remember, if you’re in that group as well, then you’re gonna be made aware of when our course comes out where we’re gonna help people to essentially manage the whole process of building a WordPress website, giving them the sorts of documentation and checklists that they can expect to be able to hand over to their client, etc. So be in the group, even if you just want to be made aware of that. And also guys, if there are flaws in my process that you think, hey, I think we could offer you some advice here, Lee, why don’t you throw it into the Facebook group as well? All right. Also, please be aware that we have a really cool new podcast that’s come out. This is for anybody that is in the conference or expo sector and it’s all about WordPress in that sector. So if people are running expo or event websites online, go check it out.
Lee Matthew Jackson:
It’s EventEngine TV podcast. You can see the information in there. And there is also a Facebook group over there as well if you’re interested in being a part of that. So the premise, there is lots and lots of advice for people in the events industry who use WordPress. So good plugins to use good processes. We’re going to be interviewing marketers, etc. People who are in that sector. So if that tickles your fancy, head on over there as EventEngine TV.
Lee Matthew Jackson:
Share with all your friends if you’re enjoying this podcast, we’re at episode 51. Next episode is going to be episode 52, which means this podcast is going to be a whole year old. So if you have enjoyed this podcast, head on over to leejacksondev.com forward slash podcast. There was a button on any episode that says leave a review. That will take you into itunes to leave a review. That’s gonna be so helpful for us because that helps us spread the word. It helps us as well go up, build up that ongoing credibility. Alright guys, this has been me raw and unedited for at least 35 minutes.
Lee Matthew Jackson:
I hope you’ve enjoyed this. I hope you like the new artwork as well. Remember, Lee JacksonDev.com forward/group if you have any feedback, have a freaking awesome day. See ya. Oh, and keep innovating.
