Just a heads up that the extension does not seem to all allow for the regular markdown for footnotes using [^1]. I do not get formatted footnotes unless I use the “inline” formatting, like so:
Enabling footnotes using inline footnote formatting results in auto-numbered footnotes which then appear below the post together, while also-enabling inline expansion enables the ellipsis tooltip-like experience with no footnotes appearing below the post. If you have the inline expansion option enabled, your post preview window will look like traditional numbered footnotes, but you’ll see the inline expanded effect after publishing.
I appreciate the automatically-numbered footnotes using the inline formatting, it just took me a few tries to figure out how I should actually format the markdown and which options would get them to behave as desired. Hopefully this comment helps someone else avoid the same confusion.
Edit to add: The inline expansion option is how your footnotes will appear on mobile, regardless of whether that option is enabled (for desktop also).
When you encounter an open source group for the first time, it may be a bewildering experience. Whether posting to a mailing list for the first time, blogging about the project you’re taking on or hanging out on an IRC channel - the way people interact, and what they expect from each other is pretty different than in classroom or with friends and family.
Open source communication can vary a lot. A core value held in common is that sharing code is good. Regardless of license, language or indentation style, open source developers create, share and modify source code together.
That’s awesome! I knew you had a plan. I should have just waited, as the other thing I pointed out was, in fact, a problem that was, in fact, dealt with by someone else, and I should have just been patient since I knew you were going to hangle it. (And it’s so pretty, too!).
It’s still been less than 24 hours, so, you know, that’s pretty good too.