Thanks for the video and interesting to see it go live and what is needed with that. Also, it would be interesting to see any and all modifications you make in the WP backend as well, permalinks etc, and any other changes from the download of WP to when you make it go live. Thanks again!
I'm glad this video was helpful. When I do tutorial on migration I will cover all the important parts that you need for making sure is migrated correctly for example database change as you need to update url in db once is migrated.
I don't know about his video and to be honest, is irrelevant because there are dozens of videos on how to create simple web designs or components for your website but it's about if the person watching has learned something and was able to understand it. I saw most videos and was hard for me to learn from them as I couldn't understand 90% of what they were saying or doing, so I decided to make videos more educational and not for the sake of views
Very interesting.. I have a few questions. You mention that you always develop a site on your localhost, but how do you then give your client access to view it? Usually there are things you want to show your client and things they want to see while building the site. Is there a cool way to just push to an online environment (like GitHub for example) or do you need to migrate it every time? Also, will themes and plugins not be outdated in the blueprint after a while? I guess that means that the sites will have outdated plugins too when you create one from a blueprint. Or is there a way that the blueprint site can keep all plugins updated automatically?
Yes, I always develop in a local environment because that is the proper way to do it. You can test code or functionality, etc. You shouldn't be doing this on a live server. There is an option to make it available to preview live by activating, and then you would just provide a password for the client. I would do a tutorial on that soon. When it comes to blueprint updates, how it works it's straight forward, when you create a blueprint, it has all the default setup or plugins you more than likely will reuse it. Before you use a blueprint on a new project, make sure everything is up to date. If you already use it on a project, then you need to update it manually on that project. If it's on a live server, then you should have a set-up to automate your updates, but before you do an update of a theme or plugin, create backup and then update it. One thing I forgot to mention on the video is, create generic username and password as you would use the same for projects that has the blueprint, once you migrate project from local to live server, change login credentials for security.
@@AJ-Pixelyze Thank you for that. Gotta look more into it. I usually develop directly on a server - I just password protect it while it's being built. That way I can have more than one person develop on it simultaneously, and it's easy to get feedback from the client. And it's not really that much faster on a localhost. Anyways, that's the proper weay for us to do it :)
If you join any Dev Agency or get hired as a developer, you be working on a local environment before project goes to production. To get multiple devs working on single project, they would use git-repo, git-hub and get-kraken. If you only planning to use a builder to make simple project that is small and won't take long to make it, then just throw it on live server and build it in couple days but the proper way is always starting from local dev not production
@@AJ-Pixelyze I’m not sure I agree. While using a local environment with Git is standard for heavy coding projects, working directly on a staging site can make perfect sense in many WordPress setups, especially for teams building with visual page builders or focusing on content. With a staging environment, you get real-time collaboration and team members can view each other's changes instantly, which is harder to do with Git because of risks of merge conflicts and delayed visibility. For complex, custom code, local development makes sense, but when the primary work is page building and content updates, staging offers a balance between safety and accessibility without over-complicating the workflow. But thanks for the video. It made me think :)
@@MortenVestergaard1 Stagging is ok for small project but if you working on Ecommerce than I wouldn't recommend, your hosting provide more than likely would say the same because when it comes to data and migrating database, it can get lost so there is a risk with staggin but small project like for example local cleaning company that might need maybe 3 or 5 pages nothing to fancy then sure. I would say go to different web agencies and see how they have it and what clients they work with then it will give you a good idea, probably best to do it.
@@AJ-Pixelyze I wonder how its working for you because I had a lot of issues with Local until I fixed them god know how :) I tried uninstalling & installing multiple times and did lots of tweaks as explained in their forums. Anyway, I played around with local when they first started and I had the same issues - that time I was on Windows 8 I believe :) Besides that, it seems very slow to work with. Is that the case for you too?
I had it issue before but that is because I haven't used it for a while and when I updated it caused confusion so I uninstalled it and installed back up and it's been working fine since than. If you experiencing slow loading, glitches, lagging etc is probably because of your device, you have to clean it from junk files, remove the garbage that is eating your ram etc. It's like a car, if you don't maintain it then it will start to break and long term it will no longer be useful.
@ That's understandable but I have a powerful PC. Local sites are my only issues 😀 They are a bit too slow to work with compared to a production site. I now keep my blueprint on local but work on staging subdomains.
Why "You can use the same blueprint for every project but is better practice to separate your blueprints based on client requirements for example, you can have one blueprint for local businesses and another for WooCommerce."? Because of the database bloat or?
No is because if for example you have a website with same layout compare to a website that need something different you would keep them as a separate blueprint same as for ecommerce. Most ecommerce have standard functionality so you can have default blueprint for that and there could be a blueprint for more advanced like a listing directory. You wouldn't want to keep all eggs in the same basket, you would have a blueprint for small local businesses that don't need much complexity compare to a local business that requires more complexity. Untimely is up to you how you setup your process that works best for you.
Great video, very clear and easy to understand. I hope to see more! Oh and I subbed 😎
I am planning next to do manual migration instead of using plugins.
Thanks for the video and interesting to see it go live and what is needed with that. Also, it would be interesting to see any and all modifications you make in the WP backend as well, permalinks etc, and any other changes from the download of WP to when you make it go live. Thanks again!
I'm glad this video was helpful. When I do tutorial on migration I will cover all the important parts that you need for making sure is migrated correctly for example database change as you need to update url in db once is migrated.
@@AJ-Pixelyze Thank You
Hi Andrzej. How is this different/main differences compared to Kevin Geary's blueprint video?
I don't know about his video and to be honest, is irrelevant because there are dozens of videos on how to create simple web designs or components for your website but it's about if the person watching has learned something and was able to understand it.
I saw most videos and was hard for me to learn from them as I couldn't understand 90% of what they were saying or doing, so I decided to make videos more educational and not for the sake of views
@@AJ-Pixelyze 👍
Very interesting.. I have a few questions. You mention that you always develop a site on your localhost, but how do you then give your client access to view it? Usually there are things you want to show your client and things they want to see while building the site. Is there a cool way to just push to an online environment (like GitHub for example) or do you need to migrate it every time?
Also, will themes and plugins not be outdated in the blueprint after a while? I guess that means that the sites will have outdated plugins too when you create one from a blueprint. Or is there a way that the blueprint site can keep all plugins updated automatically?
Yes, I always develop in a local environment because that is the proper way to do it. You can test code or functionality, etc. You shouldn't be doing this on a live server.
There is an option to make it available to preview live by activating, and then you would just provide a password for the client. I would do a tutorial on that soon.
When it comes to blueprint updates, how it works it's straight forward, when you create a blueprint, it has all the default setup or plugins you more than likely will reuse it. Before you use a blueprint on a new project, make sure everything is up to date. If you already use it on a project, then you need to update it manually on that project. If it's on a live server, then you should have a set-up to automate your updates, but before you do an update of a theme or plugin, create backup and then update it.
One thing I forgot to mention on the video is, create generic username and password as you would use the same for projects that has the blueprint, once you migrate project from local to live server, change login credentials for security.
@@AJ-Pixelyze Thank you for that. Gotta look more into it. I usually develop directly on a server - I just password protect it while it's being built. That way I can have more than one person develop on it simultaneously, and it's easy to get feedback from the client. And it's not really that much faster on a localhost. Anyways, that's the proper weay for us to do it :)
If you join any Dev Agency or get hired as a developer, you be working on a local environment before project goes to production. To get multiple devs working on single project, they would use git-repo, git-hub and get-kraken. If you only planning to use a builder to make simple project that is small and won't take long to make it, then just throw it on live server and build it in couple days but the proper way is always starting from local dev not production
@@AJ-Pixelyze I’m not sure I agree. While using a local environment with Git is standard for heavy coding projects, working directly on a staging site can make perfect sense in many WordPress setups, especially for teams building with visual page builders or focusing on content. With a staging environment, you get real-time collaboration and team members can view each other's changes instantly, which is harder to do with Git because of risks of merge conflicts and delayed visibility.
For complex, custom code, local development makes sense, but when the primary work is page building and content updates, staging offers a balance between safety and accessibility without over-complicating the workflow.
But thanks for the video. It made me think :)
@@MortenVestergaard1 Stagging is ok for small project but if you working on Ecommerce than I wouldn't recommend, your hosting provide more than likely would say the same because when it comes to data and migrating database, it can get lost so there is a risk with staggin but small project like for example local cleaning company that might need maybe 3 or 5 pages nothing to fancy then sure. I would say go to different web agencies and see how they have it and what clients they work with then it will give you a good idea, probably best to do it.
How do you get along with Local for Windows? Any issues with httpS? :)
There are no issues at all. All you have to do is set-up your project and before you open the dashboard, make sure you enable SSL and you be fine.
@@AJ-Pixelyze I wonder how its working for you because I had a lot of issues with Local until I fixed them god know how :) I tried uninstalling & installing multiple times and did lots of tweaks as explained in their forums. Anyway, I played around with local when they first started and I had the same issues - that time I was on Windows 8 I believe :)
Besides that, it seems very slow to work with. Is that the case for you too?
I had it issue before but that is because I haven't used it for a while and when I updated it caused confusion so I uninstalled it and installed back up and it's been working fine since than. If you experiencing slow loading, glitches, lagging etc is probably because of your device, you have to clean it from junk files, remove the garbage that is eating your ram etc. It's like a car, if you don't maintain it then it will start to break and long term it will no longer be useful.
@ That's understandable but I have a powerful PC. Local sites are my only issues 😀 They are a bit too slow to work with compared to a production site. I now keep my blueprint on local but work on staging subdomains.
You need to look into your setup. I don't have most powerful PC and works really good for me.
Why "You can use the same blueprint for every project but is better practice to separate your blueprints based on client requirements for example, you can have one blueprint for local businesses and another for WooCommerce."? Because of the database bloat or?
No is because if for example you have a website with same layout compare to a website that need something different you would keep them as a separate blueprint same as for ecommerce. Most ecommerce have standard functionality so you can have default blueprint for that and there could be a blueprint for more advanced like a listing directory. You wouldn't want to keep all eggs in the same basket, you would have a blueprint for small local businesses that don't need much complexity compare to a local business that requires more complexity. Untimely is up to you how you setup your process that works best for you.
@@AJ-Pixelyze Thanks Andrzej :)