Micheal0424Q: I want to ensure I've got this right.
I often update my websites using Divi. How exactly would this process work with your approach? As I understand it, I would access the existing Divi site, export it through your plugin to a new host that supports the static site.
If I need to make updates after the static site is live, I can't directly edit it, right? Instead, I'd return to the original WordPress site with Divi, make edits there, and then what? Do I need both a WordPress site with Divi and a separate static site running concurrently?
Could you break it down for me, as if you're explaining it to an elderly person?
Thanks!
Patrick_SimplyStatic
Jun 27, 2024A: > Could you break it down for me, as if you're explaining it to an elderly person?
Haha, I will try my best! đ
The most straightforward setup would look like this:
1) You move your WordPress installation to a subdomain and use it as a staging environment (wp.domain.com).
Here, you can keep editing the site, publishing new posts, creating new pages, testing plugins, and so onânothing will affect your "live website."
2) Your static website will be available at domain.com.
Each time you modify something at wp.domain.com, you can push these changes with Simply Static to domain.com.
OPTIONAL:
You can also use something like LocalWP/MAMP to manage WordPress on your local computer and then push the static version online.
We have tons of tutorials and documentation about that, I just wanted to mention it here.
Got it, so it is like back in the day when we would build the website on the computer and upload it, except now we are bounding from a WP site and pushing changes to the static website. Thank you for clarifying that, I figured that is what it was but wanted to make sure. So if the WP site gets a virus the virus will not be pushed to the static website correct?
Verified purchaser
> So if the WP site gets a virus the virus will not be pushed to the static website correct?
EXACTLY đ