We've had our eye on Agent of User's great ipfs-deploy tool (now in the IPFS Shipyard Github) for a while now. It is a quick way to get a static website served up through a regular Web2 domain name. It automates both IPFS uploading / pinning as well as updating DNS.
Now that we've got our own web API that supports IPFS, we have a PR to add Fission support to ipfs-deploy. Thanks Daniel for taking this on!
"Adding support prompted us to add another feature to our web api: manipulation of InterPlanetary Linked Data (IPLD) nodes." – Daniel Holmgren
Right now we're using this ourselves for some website experiments, leaning on the Cloudflare integration in ipfs-deploy to automate DNS updates. DNS Automation is something that we're building into the Fission Suite directly, as part of our "batteries included" approach.
As well, ipfs-deploy specifically works without a local IPFS node. The direction we're going with the Fission tools is going to assume that we can run a local IPFS node everywhere that our CLI can be installed, so we'll be leaning into "native" IPFS protocol functionality. We'll be release an alpha of our Fission CLI shortly so you can check out our approach.
Read Agent of User's Complete Beginner's Guide to Deploying Your First Static Website to IPFS for the full run down on using ipfs-deploy.
Skipping to the end, you can use your Fission credentials & Cloudflare API keys to run this one liner:
ipd -p fission -d cloudflare