by
Joop Laan
5 (2 reviews)
Inline Context – Footnotes, Tooltips & Glossary Notes
Footnotes, tooltips and glossary notes for the block editor. Click a term to reveal context inline — no page jumps.
Inline Context ranks #22,217 among WordPress.org plugins with 40+ active installations, a 5/5 rating from 2 reviews, and was last updated Oct 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v2.10.0
Current Version v2.10.0
Updated 2 weeks ago
Last Update on 21 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Top 50% by installs
Downloads -28.6% this week
Actively maintained
Rank
#22,217
—
No change
Active Installs
40+
+14.3%
KW Avg Position
31.8
0.6 worse
Downloads
1.7K
+1 today
Support Resolved
100%
—
No change
Rating
100%
Review 5 out of 5
5
(2 reviews)
Next Milestone 50
40+
50+
2,207
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 5 more installs to reach 50+
Rank Changes
Current
#22,217
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
2 reviews
Overall
100%
5
2
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
1
Resolved
0
Unresolved
100%
Resolution Rate
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.10.0
- Last Updated
- Oct 21, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Joop Laan
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 2
- Support Threads
- 1
- Resolved
- 100%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Inline Context – Footnotes, Tooltips & Glossary Notes
All three - they are the same feature with different settings. Inline mode reads as a sidenote, tooltip mode as a glossary pop-up, and without JavaScript every note is numbered as a footnote at the end of the post. Reusable notes give you a glossary you edit in one place, and the Glossary block puts that same set of notes on a page readers can browse.
Create a page, add the Glossary block, and publish. By default it lists your reusable notes grouped by first letter, with an A-Z jump bar. In the sidebar you can group by category instead, restrict it to chosen categories, include one-off notes, hide notes nothing links to yet, and show links to the posts each note explains. Those links go to the note's own place in the article, not the top of it, and the note opens as the reader arrives. If you would rather not use the block - in a widget, a template, or the Classic Editor - [inline_context_glossary] takes the same options: group_by="letter|category|none", categories="definition,source", only_reusable="true", show_usage="false", hide_unused="false", show_icons="true", show_jump_bar="true" and heading_level="2". Every term gets its own id, so you can link straight to one: /glossary/#glossary-your-term.
Not for writing the notes into your text. Attaching a note to a phrase is a Block Editor format, and it has no Classic Editor equivalent - that part needs Gutenberg. The rest does work. The Notes Library runs on a classic edit screen by design, so reusable notes can be written and organised there, and [inline_context_glossary] renders wherever a shortcode does, Classic Editor posts included. So a Classic Editor site can keep a glossary page; what it cannot do is anchor a note to a phrase mid-sentence.
Notes are created in the block editor, so you cannot insert one from a page builder's own editing screen. Notes already in your content display normally on the front end, whatever renders the page, and [inline_context_glossary] works in any builder that accepts shortcodes.
Yes. If notes jump to the bottom of the page instead of opening, you are on a version before 2.8.2, where a plugin that delayed or deferred JavaScript could stop the script running. Update, or exclude inline-context/build/frontend.js from JavaScript delay and defer.
Nothing is lost. The note text stays in the post and comes back when you reactivate. If you uninstall, the uninstaller can optionally strip the markup and leave your text clean.
Yes. Triggers are operable by keyboard with full ARIA state and Escape to close, and focus returns to where it started. If JavaScript does not run, the notes appear as a numbered endnote list at the foot of the post, each linking back to its place in the text.
No. A note's content is stored with the post, so showing one costs no extra database queries.
Yes. Notes accept rich text, links, and images from the Media Library. Images can be switched off under Settings if you want text-only notes.
Yes. Mark it reusable and edit it once - every post that uses it updates.