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
i'm literally nicky
- they/them
- nickyflowers.com/
musician, image maker, BBS sysop, game boy user, pretend meteorologist, baseball watcher...
Was (@)yiffpolice on twitter (RIP 2013-2023)
Will always be @nicky from cohost (2022-infinity)
new music forever!
nickyflowers.bandcamp.com/bluesky (lol)
bsky.app/profile/nickyflowers.bsky.sociali love to make film & video!
www.youtube.com/@NickyFlowersi do stream sometimes, it's fun!
www.twitch.tv/nickyflowersi even make games WOW!
nickyflowers.itch.io/e-mail, why not!
hello (at) nickyflowers.com
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
i think priority number one should be getting it up before october, but once it’s up, absolutely put in the work to grease those posting wheels!
Yep, totally agree. Thankfully, I am pretty sure I can do at least this much. For once having a deadline may even help with procrastination somewhat
definitely yeah, this is foremost in mind as i think about future posting avenues.
honestly yeah. I don't really have a clue about how I could go about making my current blog "stack" (Astro) easier to use but I gotta figure it out.
if it’s static then the goal is to make committing to the repo fast and easy. if it’s got a cms then you’re just hooking into that
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.
great point. having just gotten my SSG connected, idk how exactly i'll do this...
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 
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.