Add sidebar nav to jquery.com pages
@Krinkle is already working on this.
Since Jun 10, 2026.
- Dominant language
- HTML
- Stars
- 79
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
We have the pages directly on jquery.com. See also https://jquery.com/wp-sitemap-posts-page-1.xml.
| Page | Primary navigation | Secondary |
|---|---|---|
| Browser Support | Browser Support |
.. |
| Download | Download |
.. |
| Meetups | .. | .. |
| Upgrade Guides | .. | Linked from Version Support, Linked from API Documentation: Home, Linked from API Documentation: Category Version 4.0 |
| Upgrade Guide: 1.9, 3.0, 3.5, 4.0 | .. | Linked from Upgrade Guides |
| License | .. | .. |
| Team | .. | Top > OpenJS > jQuery Team |
| Support | Main nav > Version Support |
Top > Support > Chat |
| History | .. | .. |
The "License", "Team", "Support", and "History" pages were recently imported from jquery.org per https://github.com/jquery/jquery.org/issues/139.
While "Support" was added to the main nav (as "Version Support"), several of the above are hard to discover. Requiring either browsing the Top nav, or finding it indirectly via other pages, or via typeahead search suggestions.
I suggest we enable the sidebar on these pages. This is similar to what we do on other jQuery sites (api.jquery.com, blog.jquery.com, and learn.jquery.com). And for jQuery UI, it was always done on the main site as well (e.g. https://jqueryui.com/about/).
For jQuery UI, while the sidebar has always been enabled there, including on these kinds of meta pages, those meta pages were not themselves linked from that same sidebar. I fixed that in https://github.com/jquery/jqueryui.com/pull/229 a few months ago.
Once we have a solution for navigating to these pages (whether the proposed sidebar, or something else), I'd be interested in importing a "Brand Guidelines" page of sorts as well, after which we could potentially phase out https://brand.jquery.org/. I did this for QUnit at https://qunitjs.com/brand/.
Thoughts?
Preview
This is an example of what it might look like:
| Page | Screenshot |
|---|---|
| API (unchanged) | |
| Blog (unchanged) | |
| Support (after) | |
| Support (before) | |
| Team (after) | |
| Team (before) |
Note that the default page layout is already mobile-friendly. It renders similar to before on mobile when above the fold (except left-aligned instead of centered, and with a bit more room for content on mobile). The sidebar is an appendix in mobile.
| Before | After |
|---|---|
Contributor 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.
Assessment
This issue has not been assessed yet.