You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, another thing I just noticed with the footnotes are return characters at the end of each footnote. These are links to each reference in the file above. Kind of nice to have, but they weren't obvious to me that they were intentional. Also, since it creates one of these characters for each reference, things look weird if you use the same reference more than once. Furthermore, each character added gets its own supscript number except the first one which gets nothing! Screenshot below.
Another note, we use these footnotes class for whenever we do markdown with the [^tag]: [Title](URL). We also use this class in the _includes/events/event-authors.html include file (although currently we've never used the metadata keywords that seem to use this file.) We'd have to generate a dummy event with the right keywords to test how the size/style changes would affect events.
What do people think is the best way to approach resolving the size? That is easy to do by making the change @lparsons suggested (I'd suggest 0.95 because 0.9 still seemed a bit small to me). However, this doesn't resolve the, in my opinion, awkward return characters. Do we care about them? If so, do we make that a separate issue?
Notice there are 4 references to footnote 2, but only the 1st doesn't contain a superscript at the bottom.
The footnote font size is set to
0.75em
which ends up being rendered too small to read comfortably (at least for me). Could we perhaps increase it to0.9em
or similar? See an example here: https://us-rse.org/2023-06-05-pride-spotlight-sophie-wilson/#fn:chm1The css that sets the size seems to be in reboot.css: https://github.com/USRSE/usrse.github.io/blob/1d5baeca95d8463792e081c075bb99bc344a6350/assets/css/reboot.css#L3858C39-L3860
I'm not very familiar with jekyll and themes, however, so I'm not sure of the preferred way to override this.
The text was updated successfully, but these errors were encountered: