Footnote support in editor

I have the same problem. Every post I’d like to change to use the new editor has footnotes :confused:

Guys how are you suggesting that they add a feature for footnotes, when it’s already there? Like Kevin explained, you just use a superscript and then you can make a table of links at the bottom of the post?

Because the hoops you have to jump through to add some footnotes is just crazy! It was a smooth user-experience in 1.x and got horrible in the 2.x version.

The way ghost handles it is way inferior compared to almost every other solution out there.

By the way ^something^ does not work. Neither does ^[something]^
How do I get text to show up in superscript? :thinking:

€: OK… I got it. Using an HTML-block and writing vanilla HTML…

2 Likes

Let me explain to you. I had this problem too, with code pieces on my website.
You have to follow a sequence for the superscript to happen. It appears to be a problem with foreign keyboards, where the ^ does not appear immediatly.

  1. Press shift + ^ symbol
  2. Enter superscript
  3. Press shift + ^ symbol again
  4. Press your spacebar, so the symbol appears.

This is how the editor is designed to work. You can not do double ^^ and then enter in between.

In fact, you have to start off with a single ^ and then write something in there and always finish off with a ^ and then hitting the spacebar afterwards.

E.g. press these keys in sequence

  1. ^
  2. [1]
  3. ^
  4. SPACEBAR

EDIT: You don’t even need the HTML editor, you can do it inline! Just like I explained :slight_smile:

2 Likes

The problem is that now there is a hacky manual workaround when markdown used to support it automatically and seamlessly.

That is the problem. We would rather like our markdown support for footnotes back, because it was both useful and important.

2 Likes

Things might have worked better then, I wasn’t around. But I cannot see how this is hacky, I think it’s very well-made - and it works great too.

I suppose I don’t see the annoyance in doing this ^[1]^ and then writing the reference at the bottom? Isn’t that the fastest way?

1 Like

I don’t understand how you don’t see this as a hacky workaround. Something that used to be generated automatically isn’t anymore.

What happens when you move paragraphs around? You need to update every link.

Also, we used to be able to give meaningfull aliases to references (in the old editor I could write “[^guardian-article]”, for example).

2 Likes

That does suck, yeah. As I stated, I didn’t know it used to be generated automatically.

1 Like

No worries, I was just surprised :slight_smile:

I guess we’d need a special type of card for references, that could check the other (markdown) cards for references.

Something similar could be done for a “table of contents” card.

I just discovered that footnotes no longer work the way they used to and have been kind of shocked by it - the footnote support was really seamless and back when I was writing more frequently I used it for essentially every post.

I do not think the current workaround is really okay at all - it’s extremely manual. I recognize that there are some deeper technical issues that would need to be addressed in order to support this feature but it is probably my single most desirable feature - I registered an account on the forums just for this.

5 Likes

Did anyone try the following extension?

1 Like

Not me. I’m using Bigfoot.

1 Like

I experienced the same problem with using footnotes without writing the whole post in markdown.
Together with a friend, I created a script which allows you to set footnotes. Your visitors can jump between a note like “[1]” inside the post to the explanation and the end of the page and back.

I created a very detailed README for the repo.
Feel free to check it out:

Here’s my 2 cents:

This looks promising, can it be used without modifying any Ghost core files?
I’m a Ghost pro user, so the only thing I can modify is the theme!

Of course, no modifying of core required — what is required is adding the JS file(s) and CSS file(s) to your theme. That being said, you’ll probably have to customise its CSS if you want things to fit perfectly. As well, seeing how this isn’t a plug-in you’ll have to manually apply every Bigfoot footnote with HTML cards. Tedious, but it does look real nice :wink:

I guess this is one of the downfalls of having a system that isn’t user-extensible. Of course that’s not reason enough alone to switch to another platform. Ghost has many great reasons for people to use it. I do hope that as part of the 4.0 there is some sort of extension system, although I wouldn’t want it to be as wild-west as ahem Wordpress, for example.

It does seem though that in this matter (footnotes) the Ghost dev team are either obtuse or just don’t care that they have taken away a really useful feature.

2 Likes
  • +1 for any footnote developments or workarounds :pray:t4:
  • footnotes are a critical component in publishing :writing_hand:t4:
3 Likes

I’m using a german keyboard and german layout. So what you suggested does not work.

Pressing shift + ^ symbol would result in a °

Just pressing ^ does add another ^ next to it the moment you hit another key (any other key btw).

So it does not work great… it does not work at all.

Yeah… actually I got the confirmation via support chat. Some things (including subscript and superscript) are just not working for users without a US English keyboard layout (on macOS … don’t know about windows or other platforms). For example a German one which has / adds “dead keys” after typing ^ or ~ (strangely ` works fine in markdown mode).

Looking at the entries and “solutions” in this forum as well as GitHub (eg. here and here) does not make me very confident that this issue es taken serious / considered important by the devs or product management.

One workaround would be to just write everything in markdown and switching your keyboard to US English layout (use the “US English Layout”, not the “(US) English International Layout” if you are on macOS as that one has the dead keys as well).

So these are my findings after spending at least an hour on this issue experimenting and chatting with support. Unsatisfied with the result but maybe it helps someone else…

2 Likes