Hi Adam, I should start off by saying that I am also enjoying the barebones situation we’re in here, with respect to weblog.lol features. Some other minimal features I would find helpful are
drafts, with autosaving, so I don’t lose my work, and I can keep editing the next day without relying on the tab not getting accidentally closed.
post previews, I find this helpful for reviewing writing progress, or making sure that I’ve got some bit of md / html the way I intend. But it can get fiddly and distracting from actual writing, the same way that template editing can. So maybe it’s just a rendered view at the bottom of the page (not even respecting the template/css)?
scheduling posts to publish at some future time, that would be really helpful for queueing up some future articles. Not that I am actually having to deal with this particular hypothetical problem myself at the moment. I did find in the past (on micro.blog) that setting something to publish in the future was helpful for finding some of those errors that you only notice after pushing publish. Once it’s scheduled, it’s “done”, and there is a ticking clock going for when it’s really out there, so my mental editing focus switches from creating to revising, I guess.
Anyway, great work on this, I’m using it just as is, even w/o these features. Thanks!
A couple of these are already available! You can make a post a draft by adding Status: draft to the post metadata, and preview it with the button in the UI or by manually appending ?preview to the URL.
I learned a bunch from the 25 Days of omg.lol and blogged about some of my setup, but there have been quite a few more new things added over the past few weeks. I keep an eye on feature-request-complete tag here. There is also the more updated and complete quick start guide by mph that might have something you didn’t know about too.
Awesome list of suggestions! As @anniegreens pointed out, drafts are supported (though the autosave feature is a very nice idea), and the ?preview query string handles previews of draft content (which otherwise wouldn’t be visible due to its draft status).
Scheduled posts are also already supported currently! It’s as easy as setting the date on your post to a future value. If someone tries to access the post before that date/time, it won’t render; after the date/time, it will. This is another area where ?preview comes in handy, since future-dated posts are also otherwise inaccessible.
just removing it does it. Other things I would suspect that might work: remove ‘draft’ and leave it empty, set it to ‘published’ or any other string that isn’t ‘draft’. But I haven’t tried any of those.
