So, my past two entries were composed and posted "AO3" style. I write locally in a Markdown text file, I convert it to HTML via pandoc, I check it locally in my browser, I post it in the HTML mode input box. This has worked great on AO3, but I didn't think to double-check my entries here until replying to comments this morning. And discovered my entries were ugly. Raw line breaks (not br codes, just text file breaks) in the HTML were preserved rather than being wrapped. The paratransit entry had huge gaps in the blockquotes. The blockquotes were italicized.
The first two problems are now fixed, by my checking [Disable Auto-Formatting] and re-saving the entries. The blockquote italics I assume are part of the ornate style I chose to use for this journal, and I guess I get to question that decision now.
Auto-Formatting isn't all bad. This entry was written the old way, as simple text typed directly into the HTML mode box (notice the asterisks) (Edit: never mind, see below.) Without Formatting it would be one big paragraph, rather than (so far) three. (Why don't I use Rich Text? I dunno, never liked it much.)
Anyway, if the Pyrrhic and Paratransit entries looked painful to read, they should be better now.
Edit: I noticed a Markdown option on comments, and then found text format documentation and the Beta page. With Beta Create Entries, I could compose Markdown right here! Huh. Plus an option for making up my own entry links? Fascinating.
Yeah, so if you leave Entry Link blank then your entry URL will be the (digits).html style, but if you enter anything, then it will be (year)/(month)/(day)/(text).html style. You can have human-readable post URLs!
And if you update an older post to the new link style, the old links will still work, I tested it. So you won't break old bookmarks.