Docs structural changes

[tlancina]

With multiple frameworks and now Capacitor and Cordova both being first class solutions, there are some ways we can improve the current docs to be more user friendly.

• Allow setting docs-tabs component state from query param, instead of localStorage

Guide:
The content in the Angular and React sections is similar, let's consolidate so they share the same URL and use something like the docs-tabs component.

• Hook up framework switcher to Guide content
• Combine content from React and Angular sections
• New docs-tabs-like component with no visible tabs, to render framework specific content

[perrygovier]

Let's hold off on docs-tabs-like component with no visible tab for now. I'm not sure we're thinking the same thing when it comes to the implementation there.

I think first things first is to set up a better state management system to keep track of the currently active framework and platform.

Could we rename this to be that first step?

[perrygovier]

I shared this w/ @dwieeb in slack

[perrygovier]

Related

• Create <stateful-content framework="react"> style components #1204 Create <angular-only> & <react-only> style components
• Framework specific page redirects #1205 Framework specific page redirects
• Markdown parser: Framework/Platform "tabs" at the top of the page if necessary #1206 Markdown parser: Framework/Platform "tabs" at the top of the page if necessary

[perrygovier]

One of the things I think we're still unclear on.

If the page is entirely different and we're using the "framework redirect" approach, I think they should be different Markdown files entirely. So in in the docs there would be a navigation folder and then react.md, angular.md, and presumably others. If they're significantly different to begin with, I don't think finding some way to merge them in to one file is worth the added complexity.