@matigo Heh! My blog post workflow I s far less complex than it used to be [github.com] Jason. :)
These days I create a post[1337. Working Copy iOS.] and push it to appear at my GitHub Pages blog. [bazbt3.github.io] I copy the text and paste into the 10C post window, update any links for 10C (very few for me), and then post. Anywhere a IFTTT recipe can't directly post a 'published' notification I simply copy and paste the 10C URL with a brief description. Inefficient, yeah.
My GitHub repo [github.com] is essentially an unconnected series of posts with very few links to media such as podcasts, images. I'm pretty sure the basic site design wasn't meant to work with GitHub Pages, it's more sensible, quicker to build locally (Jekyll) and…
I'd much rather 10C did the heavy lifting; the space at GitHub is limited without paying for more. In fact I was about to say I don't care much about the underlying structure at 10C as long as it works and I can find stuff without much pain. Then @jws rolled up and I read @ed3d's reply as I was creating this monologue. :)
Single assets folders for at least images and sounds would be my preference. Heck, I'm even happy to create, for example, a podcast post at 10C (the infrastructure is setup for the purpose) and absorb the tiny effort required in creating what might look like a duplicate post at my GitHub repo.
Interested now, and good timing as I'm currently failing to grasp how to create webhooks. :)
// @ed3d