Roadmap / feature requests

[leonstafford]

This serves as a roadmap, so you can see what's coming up.

Something missing? Add your feature request as a comment below.

Need a new feature in a hurry? Contact [email protected] to sponsor a feature and have it fast-tracked

Roadmap

TODO: migrate existing from https://forum.wp2static.com

Deployments

• option to rewrite forms to Netlify, Formspree, Basin, etc
• deploy to Digital Ocean spaces (new add-on) Add DigitalOcean Spaces deployment option #256
• deploy to Microsoft Azure
• deploy to Google Cloud Engine
• deploy to Zeit Now
• deploy to Rackspace Cloud
• support for instance profiles in S3/CF deploys Support for instance profile #253
• Netlify full register/create, diff-based deploys via OAuth API (new add-on)
• option to crawl only / depoy only via UI, like with WP-CLI
• increase debug logging across deploy methods besides GH/S3
• post-deploy 404 checker
• option to use custom GitLab instances New feature for export pages to custom gitlab instance #312
• custom zip name for ease of workflow integrations Custom ZIP Name #233
• add cachebuster to visit deployed site link add cachebuster to visit deployed site link #225
• option to delete files removed since last subdir deploys Export to File system does not remove deleted pages/css/images etc. #251

Crawling

• "Aggressive mode" - 4 x workers to process queues / spawn more processes. For large sites
• Allow user to choose which post types are detected for initial crawl list Allow user to choose which post types are detected for initial crawl list #219
• verify working: detect URLs for posts that span multiple pages detect URLs for posts that span multiple pages  #277
• allow crawling on an internal address / specifying WP Site URL / Home vs breaking on WP-CLI when it's been set via $_SERVER['HTTP_HOST'] or such

Generating

• "Landing Page" mode - set specific page as homepage
• Add Permalinks structure to Debug Logging Add Permalinks structure to Debug Logging #278

General

• call to action to buy license for commercial usage
• rewrite views to prevent other plugin/theme's notices appearing mid-screen
• support multiple configurations / option sets
• warn user when WP site is publicly accessible, point to docs on how to secure
• upon failure in GUI, prompt to re-run with Debug Mode on
• upon failure, display which phase of the generate/deploy failure occurred on
• licensing: embed license code in downloads via wp2static.com if detected, add to wp settings, present on screen else show prompt to buy commercial license (mask all but first n chars)

Housekeeping / Leon's TODO's

• ./library -> ./plugin, ./library/{FTP,CSSParser,URL2} -> ./plugin./vendor/, ./powerpack -> ./plugin/deployers, ./library/StaticHtmlOutput/ -> ./library/WP2Static/
• ./provisioning/tests -> ./tests
• check phpunit dependency in ./provisioning/run_unit_tests.sh
• basic style guide in docs (indents for PHP/JS/Templates, follow phpcs.xml
• fix up translations files (use enqueue_{style,script})
• migrate docs over from https://docs.wp2static.com
• update header images, plugin description, readme inline with https://wp2static.com tagline
• reduce multiple calls seen in Debug Mode, shift rewrite rules to global settings, share between HTML/TXT processors
• issue templates, etc https://github.com/leonstafford/wp2static/community

[mrpatg]

How about a post processing action?

I want to trigger a CircleCI build when everything is done uploading to github (for instance). Or shoot out a notification or what have you. Right now you could do it by piping in the email to a script, but it would be handy to have.

Thanks

[Retrospector]

It would be great to be able to deploy the Static files to Minio, which is a self hosted, Amazon S3 compatible Object Storage, but free, open source and self-hosted.

Thanks a lot for a possible consideration!

[davidlevy247]

Just an ease of use suggestion for the processing tab options.
Rewrite Links in source code
Rename Exported Directories

1. having perhaps more clear/consistent directions
   eg see ,inc/ in renames example has a backslash while the other lines do not, this is confusing

2. a more "smart" Rewrite/Rename options setup if you will, where your plugin detects the common folders and leaves boxes for what we wish to change them to, with an additional field for changing uncommon folders for the more advanced.
   This suggestion is essentially intended to dummy proofs the two Rewrite/Rename options in processing.

[szepeviktor]

Methods supported by WP_Filesystem() should be part of the plugin as Deploy methods

• direct file write
• FTP
• SSH

and implementing other protocols such as Google Cloud Engine could be implemented as WP Filesystem

[leonstafford]

review object store options here for add-on contenders https://www.lowendtalk.com/discussion/137353/object-storage

[meredevelopment]

Hi, we have an immediate need for S3/CF profiles support. Pleased to see it on the list!
If you want it tested please let me know. If it's not planned for a while, do you have any pointers for adding a profile string to the invalidation request manually?

[dbutcheratrenet]

Please show the the log file modification dates/times to the right of the log file dropdown so it's easier to see when the most recent logs were created (the date/time of the last successful run, essentially). On a system with multiple users this makes it easier to see how current everything is. Thanks.

[gwhitelaw]

We use your great plugin for deploying to a staging site first, then to our live site.
I see you have the feature we are keen for: support multiple configurations / option sets. This would mean you need to have a separate cache for each deployment.

Right now we empty the cache between deploys, otherwise we get crazy behaviour.
Therefore I think a feature to "Disable cache" would be great.

Another thought would be easy roll-back- perhaps with versioning ZIPs. We're looking to do this manually but perhaps it's something you would benefit from adding?

[davidlevy247]

It's been really quiet for about 2+ months, is he still developing this product? I'm a license holder.

[leonstafford]

Hi @davidlevy247 still here and still seeing issues and responding to support requests. Not able to focus on development 100% at the moment, unfortunately, but still progressing. Sorry for the delays and thanks for your continued patience. Cheers, Leon

[leonstafford]

@gwhitelaw - unfortunately, I've had to drop multiple configs from first cut of version 7, as per new roadmap put here a few days ago: https://wp2static.com/support/roadmap/

There will still be ways to handle staging/production or multiple deployment environments without requiring re-crawling or processing, ie using relative URLs and git branching or such to determine where to deploy. With new way that crawling/post processing and deployment work, if you did need to re-run, the crawl caching would still be of benefit and the plugin would only need to re-process the generated static files for a different export URL, which will still be a lot faster than now.

[gwhitelaw]

Thanks for that @leonstafford - the website makes it clear.

The git branching and deploying is what we were planning on building. Is that something you're planning on doing?

You've made such a great app man - really appreciated.

[leonstafford]

Thanks for that @leonstafford - the website makes it clear.

The git branching and deploying is what we were planning on building. Is that something you're planning on doing?

You've made such a great app man - really appreciated.

Thanks, I'm excited for future versions, a lot planned that I hope you'll like!

I plan to put some guides in docs on how to do such workflows. I started with a concept of "Staging and Production" environments as 1st class concepts in the app, but then removed, both due to it making things a bit more confusing for the users who don't code and would be using mostly via UI, but also due to it requiring added complexity around the caching mechanisms, which, being caching, already have enough complexity involved!

Git branching or Netlify's staging functionality would be workflows I can add guides for.

Basically, like this for a git-based workflow:

• set URLs to all relative, ie /mypath/myfile.jpg
• deploy to git branch, staging
• run CI tools against this branch, which can include deploying to a server and optionally running automated tests against it
• when approval has been done on staging (manual or automated), merge into master, create a tag, etc

How does that sound for your desired workflow?

[leonstafford]

^ whilst that should work with current v6 and WP-CLI, I'm not confident in the relative URL rewriting at the moment. And, it will be a lot nicer with coming features to only crawl/process/auto-deploy newly updated content in WordPress