Main nav should be page title, not derived from filename

[matryer]

• Get the first H1 from the document and use that as the title in the navigation
• If there aren't any - then use the filename

[mazondo]

This would require me to parse it out on data loading, otherwise I'd have to pull all the pages down completely which would be huge. Right now I only pull the filepath to generate the menu and then I load the page body when someone clicks on the link.

[matryer]

How is the nav stored?

On Jan 23, 2014, at 2:05 AM, Ryan notifications@github.com wrote:

This would require me to parse it out on data loading, otherwise I'd have to pull all the pages down completely which would be huge. Right now I only pull the filepath to generate the menu and then I load the page body when someone clicks on the link.

— Reply to this email directly or view it on GitHub.

[mazondo]

There is no nav, really, that's why the markup for it gets so deep. I have an array of file paths to work with, and I generate the nav from there. It needs to be pre-rendered and dropped on the page, really. But either way, no access to the page content until they load the page.

[matryer]

You could improve this:

• Parser script maintains an in-memory nag
• Nav is posted to Stretchr as a single resource /nav/main
• Nav is then loaded that describes the whole thing

This would be nice because you could actually provide other features later too. Like only show this item if debug=true or something.

On Jan 23, 2014, at 11:19 AM, Ryan notifications@github.com wrote:

There is no nav, really, that's why the markup for it gets so deep. I have an array of file paths to work with, and I generate the nav from there. It needs to be pre-rendered and dropped on the page, really. But either way, no access to the page content until they load the page.

— Reply to this email directly or view it on GitHub.

[mazondo]

can now edit titles on your own. Defaults to page title.