Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Reinstate "microsites" #172

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

Closed
sanscontext opened this issue Oct 29, 2019 · 5 comments · Fixed by #192
Closed

Reinstate "microsites" #172

sanscontext opened this issue Oct 29, 2019 · 5 comments · Fixed by #192
Assignees

Comments

@sanscontext
Copy link
Contributor

In the original version of the docs, we had several "microsites", meaning places where the left nav updated to only show items from in that section. This is currently not working, and the paths that should have their own nav are just part of "main". I flagged this on October 8th, flagging again now.

These paths should render their own left nav:

  • legal
  • partners
  • glossary
@jedrzejchalubek
Copy link
Contributor

I think this wasn't predicted on designs :) What items have to have new legal and partners menus?

@sanscontext
Copy link
Contributor Author

Here's a hacked-together version of what it should look like for Partners:
image

@sanscontext
Copy link
Contributor Author

Hey @jedrzejchalubek , the Legal and Partners menus are just everything that's in that src/legal and src/partners paths, omitting anything that's hidden:true.

@jedrzejchalubek
Copy link
Contributor

omitting anything that's hidden:true.

We would need to have this information inside _data files as we cannot easily determine this when looping on data files only at this point

@sanscontext
Copy link
Contributor Author

@jedrzejchalubek you're right - we don't want to use the hidden: flag anymore, just want to manually omit it from the nav. Sorry about that, I was thinking of the update utility script. I think we're good to close here.

bot-docsteam added a commit that referenced this issue Jan 14, 2022
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 a pull request may close this issue.

2 participants