Improve organisation of pages in docs

[jacobhq]

• Automatically generate breadcrumbs, and require less boilerplate for docs pages

• Explore doing sidebar organisation based on filesystem

• Update names of pages to be more consistent

  

  As you can see here, all headings are verbs on nextjs docs. Tuono currently has a mixture:

  

  We should pick a style to use consistently. Also, we should perhaps rename Overview to Features.

• Choose between serverside and server-side, then be consistent

I'm very open to discussion and suggestions. Please let me know what you think!

[Valerioageno]

Very nice points!
I think we should definitely improve the spelling we use across the documentation. One challenge I see is how can we enforce consistency after we fixed it the first time. @nicolasgasco do you have any knowledge about keeping consistent spelling across a website?

With @marcalexiei we tried to use a spell checker on the pipelines but its maintenance was crazy complicated...

Automatically generate breadcrumbs, and require less boilerplate for docs pages
Explore doing sidebar organisation based on filesystem

For this two points I think the best would be to create a React context so that we manage the whole app state from a single place that can be accessed by any children (hence generating breadcrumbs, canonical tags, #23, etc)

[jacobhq]

For this two points I think the best would be to create a React context so that we manage the whole app state from a single place that can be accessed by any children (hence generating breadcrumbs, canonical tags, #23, etc)

I like that idea!

We tried to use a spell checker on the pipelines but its maintenance was crazy complicated...

Interesting, I've never seen that done before.