I am a WP designer and a current user of HardyPress, so I understand static sites and how they work and such. My biggest complaint with HardyPress and Shifter is that they require naked domain names and require domain registration with a small group of registrars that can provide these specialized configurations. When clients come to me with already-registered domains, it can be a real pain to move them to one of these special registrars.
I'm exploring a more DIY approach, contemplating creating my clients' websites using WP and then flattening them with your plugin, hoping that the deploying of these artifacts is as easy as clicking a single button from the WP dashboard, as it is with HardyPress.
Anyway, forgive my ignorance on this subject, but you indicate that your plugin will auto-deploy to a list of sites, all of which I've visited and explored. These sites are not normal in the sense that they don't seem to offer website space in a traditional way, like what I'm used to. Heck, BunnyCDN seems to offer only CDN services and GitHub is a software development platform. How are these and the other possible sites supposed to host the HTML websites I'd be deploying after using WP2Static?
- 1 replies
- Leon Stafford @leonstafford2019-01-26 02:07:06.996Z
Thanks for reaching out and this is cool to hear of people using HardyPress and Shifter.
It's a 1-click process... 90% of the time :) There are too many variables for me to guarantee clean exports for every hosting environment, plugin, theme, custom code combination possible with WordPress.
The way we get to host on these free, like Netlify, hosts is by publishing out as static HTML, no moving parts. You're already experiencing the end results of this perhaps with HardyPress, Shifter, Strattic type setups (I haven't looked into the tech too deeply). With WP2Static, you're in control of the WP to static site conversion and deployment.
This has pros and cons vs a hosted solution.
Pro - it's free! You can host your WordPress site on your own server or 100 client sites on a public, but password-protected server. Let the plugin, crawl and generate the static HTML, then deploy it to Netlify, GH Pages, etc.
Cons - you (currently) need to sort out the contact form situation. The WP Serverless Forms plugin by Shifter is very easy with this and Contact Form 7 together, else adding a line of code to your theme should do it.
The other benefit is that you can choose from the fastest hosting methods in the world. Netlify is blazing fast. Any CDN is usually uber-fast. Any of these you can stick CloudFlare in front of and define full site caching via Page Rules.
Best to give it a try with a few sites, let me know any issues you encounter and see if it suits you.