Q: What if I have built my site using Breakdance, with the built in contact form, and endpoints to automate the ...
captured lead to send to Google sheets, and the form automatically sending the date to CRM? How is this handled?
How is future updates handled? For example, I want to update the structure of the website. What happens in that scenario? How do we maintain new content such as articles to have Google see that there is new fresh content.
Patrick_SimplyStatic
Jun 27, 2024A: Excellent questions!
Breakdance + built-in form:
That should work - If I understand correctly, you send the submissions directly to Google Sheets, and they aren't stored in WordPress, right?
As long as you don't actively depend on WP for the submissions, Simply Static can handle this for you.
If you need WP to handle some parts of the logic, it's still possible but a bit more complex due to CORS limitations.
Updates:
We have multiple ways to update content on your static site:
Run a new static export:
This makes sense if you changed something globally (e.g., the theme, the navigation—anything "global").
Single exports:
You can quickly publish (or update) single pages, posts (or any other CPT) - we export the post, including all the images and other assets + all pages that are related to it (the homepage, the blog page, category, and tag pages..)
Build exports:
Imagine a category available for posts, pages, and so on. You assign them to a "Build", and you can export all the assigned posts/pages with a single click.
Incremental Exports:
We are working on this right now, and it will be available in a couple of weeks as a beta.
We automatically track changes in WordPress (new posts, new pages, images uploaded, comments..) and you only export content that has changed since the last static export.
cmwwebfx
Verified purchaser
I think incremental exports would be the icing on the cake in this scenario where I will likely only update the home page one every month, then update with new posts fortnightly.
For this scenario that I've described, I am on my own VPS, but see a massive benefit to having a static site. What are your recommendations to keeping a master WP site for making updates? Do you recommend simply using the WP as a staging site, then deploying the static site to the live url? Do you have a tiered plan for 2 websites only?
Verified purchaser
@cmwwebfx
Question: For this scenario that I've described, I am on my own VPS, but see a massive benefit to having a static site. What are your recommendations to keeping a master WP site for making updates? Do you recommend simply using the WP as a staging site, then deploying the static site to the live url? Do you have a tiered plan for 2 websites only?
That's exactly what I recommend.
You use WP as a permanent staging environment on a subdomain and point your root domain to the static site.
We don't have a tiered plan for only two websites, but we will include one additional activation for staging/dev sites. Would that work for you?
If so, open a ticket at our support desk at https://simplystatic.com/support/ and tell us the URL, and we will whitelist it for you!