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

Question: hierarchy of "landing pages" #679

Closed
ghost opened this issue Jan 25, 2017 · 1 comment
Closed

Question: hierarchy of "landing pages" #679

ghost opened this issue Jan 25, 2017 · 1 comment

Comments

@ghost
Copy link

ghost commented Jan 25, 2017

Great ecosystem -- I'm really enjoying working with Slate!

I'm trying to implement a "hierarchy of landing pages", along the lines of the discussion in issue 553 (#553). I added my comments/questions there, but realized that because it's a closed issue, it's unlikely to get any eyeballs :-). So apologies for the repeat; here're my questions:

I'd like things to match the desired example (https://www.fullcontact.com/developer/docs/). I'm using El Capitain on a MacBook Pro, Chrome 55.0.xxxxx, and current (downloaded last week) versions of slate, ruby, middleman, gem, etc.

  • Where in the layout.erb file should the <div id="toc"> go? I've tried putting it in several places within the <div class="tocify-wrapper">, but the results are always the same: The footer info appears at the top of the left column, then the "sub-folders/sub-items" appear, and then the primary content of the parent's index.html.md.

  • As well, the ToC entries are dark blue underlined (changing to purple underlined after visiting) instead of inheriting the standard styling (which I tweaked for font size and, per https://github.com/lord/slate/wiki/Deeper-Nesting, added more ToC levels).

  • When I click any of the sub-folders/sub-items, the middle pane correctly shows the contents, but the left nav-pane changes to show only the sub-folders/sub-items. That is, the regular "parent" headings and the footer info disappear. Then the only way to get them back is to use the browser's back button.

Thanks very much for hints and help!

@lord
Copy link
Member

lord commented Feb 2, 2017

It's not built yet, but would a solution similar to the one in #138 help? If you want to futz with the ToC, I suspect you'll need to make changes in the actualy ToC javascript if you haven't already.

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

No branches or pull requests

1 participant