Add footnote hover?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
The footnote references are in the guide's Markdown pages, and the payload names no specific file. Start by finding the footnote references in the citation section at the top of the page and in the Zenodo JSON section, then remove the repeated references elsewhere. Pick one approach (dropping repeats or switching to tooltips) with the maintainers before editing. Done when each footnote is referenced only at the agreed spots and the bottom footnote section still renders.
Written by the indexing model from the issue text.
Description
Perfect, with two small tweaks!
One other thing I noticed while running it locally, though, is that it has a lot of these back arrows (😅 footnote challenge), which we could adjust through some special handling (remove the bolding altogether, though they'd still be there, use a custom script to only include the one from which the user clicked, or switch to footnote tooltips which show as a little hover pop-up). Such a change would be outside the scope of this PR; we do have a few other pages with footnotes referenced twice on a page.
Probably better is to just not include the footnote each time it's mentioned; limiting to the first mention in the citation section (at the top, the suggestion) and when it's mentioned in the Zenodo JSON section is probably sufficient.
I tested the tooltip option and it doesn't change the footnote at the bottom of the page (might be nice to add them in--will open an issue).
Originally posted by @egrace479 in https://github.com/Imageomics/Collaborative-distributed-science-guide/pull/84#pullrequestreview-5342252207
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Imageomics/Collaborative-distributed-science-guide
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement good first issue
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
enhancement good first issue
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation enhancement
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
All issues in Imageomics/Collaborative-distributed-science-guide
Similar issues
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
almanac-data/climate-almanac#138 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
OceanDataTools/openrvdas#760 ·
Maintainers usually reply within 1 day
-
level/subtask type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wazuh/wazuh-virtual-machines#1091 ·
Maintainers usually reply within 1 day
-
Python: Bug: ChatMessageContent.from_element drops AudioContent and BinaryContent into raw TextContentPossibly taken @halcyon-past claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/semantic-kernel#14824 · 1 comment ·
Maintainers usually reply within 3 days
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#142 · 1 comment ·
Maintainers usually reply within 1 day