Add setting up draft

[Noviny]

No description provided.

[Noviny]

@KyleAMathews

Hey, for this one, I'm trying to add setting-up as a multi-part guide, so you'll end up with paths such as /guides/setting-up/installation however it is building as guides-setting-up/installation. I changed how kebab casing was working, but it didn't do the thing I was really looking for which was nest the setting-up under the guides.

These are still drafts, but wanted to make sure this problem didn't become a blocker.

[KyleAMathews]

Oh ok. Perhaps just split the path on "/" and run kebabCase in each section then recombine?

…

On Wed, Mar 1, 2017, 8:20 PM Ben Conolly ***@***.***> wrote: @KyleAMathews <https://github.com/KyleAMathews> Hey, for this one, I'm trying to add setting-up as a multi-part guide, so you'll end up with paths such as /guides/setting-up/installation however it is building as guides-setting-up/installation. I changed how kebab casing was working, but it didn't do the thing I was really looking for which was nest the setting-up under the guides. These are still drafts, but wanted to make sure this problem didn't become a blocker. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEVh9S5EvKXenvTzqAEK7wXp8JQLTsNks5rhkOggaJpZM4MQh_p> .

[KyleAMathews]

This is live now 🎉

BTW, who needs to review this PR to get it merged? I'd rather all these doc changes live on master + the site get auto-rebuilt on Netlfy on a more official URL.

[Noviny]

🎉 indeed!

Going to try and get a clear path for this to go live today.

[KyleAMathews]

Sweet!

[Noviny]

Still don't have a definitive answer. Have a question though.

Probably going to look at making the sidebar more nested, with the ability to dig further in to topics. Is it still best to do this through yaml? Can we generate this dynamically?

[KyleAMathews]

Yeah, that's definitely doable — the markdown headings are exposed on the MarkdownRemark type.

So query that and then match the heading info with the paths & order expressed in the YAML file. The one trick would be where to query for headings. Probably the right solution would be to add support for adding graphql queries in layout components as currently they're only supported in page/template components.