This issue is for building the new Evo Web site with the agreed option 1 from our list of options. The high-level strategy (as detailed from internal docs for option 1) includes the following for the new site:

1. For component pages, it uses Fake Tabs to link to specific content pages
2. The default component page is the Evo CSS Component.
3. There is general information about the component at the top that is common to all sub-pages.
4. The page can includes the following fake tabs that link to sub-pages, but it doesn't necessarily need to have all of these (just a pattern):
   a. Structure (default, static component) - /accordion/
   b. A11y Standards - /accordion/a11y-standards/
   c. JS Component - /accordion/js/
   d. Evo-Marko - /accordion/marko-component/
   e. Evo-React - /accordion/react-component/
5. The sub-pages have the same general layout, but with the current tab and its contents activated and displayed.
6. Since the evo-css docs are so particular to structure, css, a11y, and js, it's very difficult to create a single mechanism to cater to all tab contents without significantly increasing the complexity and maintainability.
7. As such, each tab contains its own distinct content and there is no functional mechanism to swap just the language portions throughout the docs.
8. We should plan to avoid content duplication across the various tabs.