* Hit save
* Let Hugo/Jekyll/Pelican/whatever compile
* FTP/SCP onto a server
* It's a blog, nobody needs a CDN for that
Where? On my iPhone?
* Hit save
Where does it save it to?
* Let Hugo/Jekyll/Pelican/whatever compile
Where does that happen? If I want to write on my phone it won't compile on my phone.
* FTP/SCP onto a server
From my phone? Also I specifically don't want to run a server, or more specifically, I don't want to pay for a server to run all the time.
* It's a blog, nobody needs a CDN for that
If you're writing about high scalability, it's a bit embarrassing and ruins your credibility if your site isn't speedy worldwide.
Ok that part's easy.
> commit to git
How? I've never seen a good git client for the phone
> have some CI build it and deploy.
Step one, draw a circle. Step two, draw the rest of the owl. :)
While this might be a fun exercise, it's more involved than deploying some code to Lambda.
That coupled with Working Copy could be a pretty good mobile workflow.
For me, this was much easier than deploying Lambda code and managing How all of that worked together. Using Github Actions wasn’t much more than setting up a deploy script.
Managing posts also sucks. I can pre-date posts but I can't at a glance get a list of posts with data about each one. Instead I just get a file listing and have to open each file and read its headers to see its metadata (date, title). Publish vs unpublished also suck. I have folders for my posts and another folder for drafts but moving something from one to the other is no fun compared to just checking a box in wordpress.
* load a web page
* write words
* hit submit
* this triggers a lambda function that generates a static website and puts it on s3
* this triggers another lambda function that pokes the CDN and expires anything that changed
By self-hosted I mean I control all the parts. I can change the generation code, the CDN upload/expiration code, I can change the output, I can view the logs, all within my own account.