Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP][www] Sidebars à la reactjs.org (accordions, scrollspy) #6076

Closed
wants to merge 1 commit into from

Conversation

fk
Copy link
Contributor

@fk fk commented Jun 21, 2018

WIP, has some issues with properly highlighting some active menu items in "Tutorial" due to some last-minute changes. Will fix and provide more detail here tomorrow.


This ports sidebar navigation accordions and „scroll spy“ behavior from the ReactJS docs, with a few adjustments:

  • closely stick to the current yml format
    • instead of mixing user-defined id and href values, stick to the existing link
    • opt in to setting a „directory“ (think „baseUrl“ for all item links in yml) — makes
    • generate an id for every yaml navigation item

I had to bump gatsby-remark-prismjs from 1.2.23 to 2.0.4 after I — all of a sudden — ran into the Uncaught TypeError: Cannot read property 'tokenizePlaceholders' of undefined error.

This ports sidebar navigation accordions and „scroll spy“ behavior from the ReactJS docs, with a few adjustments:

* closely stick to the current `yml` format
  * instead of mixing user-defined `id` and `href` values, stick to the existing `link`
  * opt in to setting a „directory“ (think „baseUrl“ for all item links in `yml`) — makes
  * generate an `id` for every `yaml` navigation item (as opposed to

I had to bump gatsby-remark-prismjs from 1.2.23 to 2.0.4 after I — all of a sudden — ran into the `Uncaught TypeError: Cannot read property 'tokenizePlaceholders' of undefined` error.
@KyleAMathews
Copy link
Contributor

Hey! Sorry to do this to you but we're not making any more substantive changes to v1 version of gatsbyjs.org — this branch should mostly merge cleanly into master so could you do that and create a new PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants