draw-er reader music-er knitter nature-er sleeper cook-er

🪱

everyone is inherently valuable--that means you

🪱

i'm a little goblin
enjoying the little things in life


ewie
@ewie

if you post a lot on cohost it’s almost certainly because you have it saved on your home screen and the work needed to make a new post is open the app and tap the compose button. you gotta make it just as easy to post on your own site! you’re not gonna use it as much if you don’t! it’s okay to spend way too much work up front ensuring the actual posting process is as seamless as possible, but it’s gotta be easy in the moment for you to go from dumb joke to posted dumb joke


esoterictriangle
@esoterictriangle

I was able to parse it enough to see I could basically just drop a .md into a github folder and it would Post

This, of course, means no preview (or uh. rather. everyone gets to preview) when I do it from my android phone, but proofreading the formatted version is only for certain kinds of post, imo. I'm planning on setting some css for <img> so adding images will have a consistent enough look/I'll know what to expect for them and markdown around them accordingly.

This is still, in many ways, harder than a chost, but it is an acceptable compromise for me.1 I hope everyone can find a solution that works for them; I am honestly shocked my coding skillset has expanded enough to accomplish what's happening on my site right now, and floored I was able to read thru 11ty's docs and be able to go "uhm, yeah, ok, I think this means I can do x, y??? and maybe z????" and be correct.


  1. it's leveraging what I already had as the start for many of my posts: the pre draft quickly typed notes to self in the samsung notes app, plus my skill in markdown and one-off html tags. Which all balances out the rest of the steps being more work


You must log in to comment.

in reply to @ewie's post:

I was just thinking about this!

I was planning to quickly put together a stub of a blog and publish it before the site goes down and was wondering how much of a priority it would be to write the post composer. As in, to put together a placeholder page, the dashboard of the database would suffice for content management, but just how quickly will I become sick of it

Right now it doesn't but yeah it could have one. I've resisted the temptation of having a CMS of any kind to keep it ""simple"" but maybe it's worth adding code complexity to reduce friction on this one.

I am probably going to eventually set up a GitHub workflow to build and deploy my static blog, then I can use Working Copy to pull the site down on my phone, and either make a new Markdown post directly in Working Copy or do it in a Markdown editor like iA Writer before pushing it back up to GitHub to publish.

Having said that, I kind of like the idea of not posting all the time. It’s very retro, when you had to get on your computer to post :eggbug-relieved:

For now I’ll probably just write my posts during the day using Obsidian and then copy them over to my site repo on my computer in the evening.