=== Simply Static === Contributors: kennu, codeofconduct Donate link: https://github.com/kennu/simply-static-s3 Tags: simply static, html, static, static site, static site generator, performance, fast, optimization, availability, scaling, scalability, cdn, security, secure, zip, hardening Requires at least: 3.8 Tested up to: 4.3 Stable tag: 2.0.0 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html
Create a static copy of your WordPress site that you can serve on your favorite web server.
== Description ==
Do you love working with WordPress but wish it was easier to keep your site safe from hackers? What if you could set up your site to protect it from hackers and, as an added bonus, also make it load faster? Meet Simply Static.
Simply Static creates a static copy of your WordPress site. Keep your WordPress installation private and publish your static site for everyone else. And your static site will be incredibly fast since it's just collection of files with no server-side code or database to slow it down.
== Installation ==
or
simply-static
folder to the /wp-content/plugins/
directory.== Frequently Asked Questions ==
= Who should use Simply Static? =
Simply Static is great for sites with no user interactivity, such as blogs (with comments disabled) or brochure-ware sites for small businesses (with no forms).
= What does Simply Static do? =
Simply Static generates static (HTML) copies of your WordPress pages. It works a bit like a web crawler, starting at the main page of your website and looking for links to other pages to create static copies of. It also includes any images, CSS & JS files, and any other files that it can find a link to.
As Simply Static is creating the static pages, it will automatically replace the URL for the WordPress installation with the URL for the site that you're going to have hosting the static files. So if WordPress is hosted at wordpress.example.com and your static site will be at www.example.com, all instances of wordpress.example.com will be replaced with www.example.com.
= How do I set up Simply Static? =
Let's assume you presently have WordPress hosting a site at www.example.com, and that's where you'd like to have your static site instead. Your first task is going to be to move your WordPress installation to a subdomain, such as wordpress.example.com. Once that is complete, you'll set up www.example.com to receive your static files.
If www.example.com is on the same server as your WordPress installation, you can have Simply Static copy the static files to the directory that www.example.com is serving files from. If www.example.com is on a different server, you can download a zip of your static files and then upload them to www.example.com.
In the future we'll add more ways to transfer your files to other servers, such as FTP, SFTP, and SCP, and add support for specialty destinations like Amazon S3.
= Will this plugin interfere with other plugins? =
Simply Static's output is just a collection of static files: HTML, CSS, JS, images, etc. Any functionality that would require PHP in order to function will not work. That includes, but is not limited to: blog post comments, contact forms, forums, membership areas, and eCommerce.
Note that you can achieve some of this functionality by using plugins that interact with third-party services. For example, for blog post comments you could use Disqus and for forms you could use Wufoo.
= How is Simply Static different from cache plugins? =
Cache plugins -- such as W3 Total Cache or WP Super Cache -- make your existing WordPress site faster by caching pages as they're visited. This makes your site much faster, but still leaves your WordPress installation accessible to the outside world. Unless you keep on top of updates, your WordPress installation can become vulnerable to hackers due to security vulnerabilities that are found over time.
Simply Static creates a copy of your WordPress site that is intended to be used completely separately from your WordPress installation. Your WordPress installation lives on one server and your static site is served on a different server. Or, they're both on the same server, but your WordPress installation is restricted to only allow access from certain ip addresses or with an additional username/password requirement. Your static site is just a collection of static files with no server-side code or database -- nothing for hackers to hack -- while your WordPress installation remains safe and secure.
== Screenshots ==
== Changelog ==
= 2.0.0, December 6, 2015 =
= 1.1.2, October 22, 2015 =
= 1.1.1, October 9, 2015 =
= 1.1.0, October 6, 2015 =
= 1.0.2, October 4, 2015 =
= 1.0.1, September 29, 2015 =
= 1.0.0, September 21, 2015 =
== Upgrade Notice ==
n/a