📖 [Story sidebar] Removed sidebar from docs (ampproject#35616)

mszylkowski · web-flow · commit 2106624c692d · 2021-08-11T17:13:54.000-04:00
* removed sidebar and bookend docs

* removed unused import

* revert test removals

* Add newline on visual test html
diff --git a/extensions/amp-sidebar/0.1/amp-sidebar.md b/extensions/amp-sidebar/0.1/amp-sidebar.md
@@ -2,9 +2,7 @@
 $category@: layout
 formats:
   - websites
-  - stories
   - email
-  - stories
 teaser:
   text: Provides a way to display meta content intended for temporary access such as navigation, links, buttons, menus.
 ---
@@ -261,55 +259,6 @@ When using `<amp-sidebar>`, keep in mind that your users will often view your pa
 
 For this reason, we recommend that affordances to open the sidebar are not placed in a fixed, full-width header.
 
-[filter formats="stories"]
-
-### Sidebar for Stories
-
-Use of `amp-sidebar` is supported within the `amp-story` [component](https://www.ampproject.org/stories/).
-
-#### Behavior
-
--   The `<amp-sidebar>` must be a direct child of `<amp-story>`.
--   The sidebar defaults to the "end" side, meaning right for left-right languages and left for right-to-left languages.
--   The `<amp-sidebar>` has default background color of white and is overridable in CSS.
--   Default width of `<amp-sidebar>` is `75%` of the viewport up to `360px`, on and `25%` up to `600px` for desktop experiences. Width can be overriden using the CSS `width` property, but has to be contained within these intervals.
--   A 'hamburger' style button that opens/closes the sidebar will appear on the story UI.
-
-There are certain restrictions on what attributes and features are allowed in order to provide a consistent UI experience across the story platform. The following are allowed attributes and features of an `amp-sidebar` within an `amp-story`.
-
-#### Allowed Attributes
-
--   [layout](#layout)
--   [data-close-button-aria-label](#data)
--   [common attributes](#common)
-
-_Example: Basic Sidebar in a Story_
-
-The following example shows a simple `amp-sidebar` within an `amp-story`.
-
-```html
-...
-<body>
-    <amp-story standalone>
-      <amp-sidebar id="sidebar1" layout="nodisplay">
-        <ul>
-          <li><a href="https://www.ampproject.org"> External Link </a></li>
-          <li>Nav item 2</li>
-          <li>Nav item 3</li>
-        </ul>
-      </amp-sidebar>
-      <amp-story-page id="cover">
-        <amp-story-grid-layer template="fill">
-          <h1>Hello World</h1>
-          <p>This is the cover page of this story.</p>
-        </amp-story-grid-layer>
-      </amp-story-page>
-      ...
-  </body>
-```
-
-[/filter]<!-- formats="stories" -->
-
 ## Attributes
 
 ##### side
diff --git a/extensions/amp-story/amp-story-analytics.md b/extensions/amp-story/amp-story-analytics.md
@@ -124,7 +124,6 @@ The `story-open` trigger is fired when opening a drawer or dialog inside a story
 -   Page attachment (`<amp-story-page-attachment>`)
 -   Share dialog (`<amp-story-share-menu>`)
 -   Info dialog (`<amp-story-info-dialog>`)
--   Sidebar (`<amp-sidebar>`)
 
 To use it, specify the trigger on your `"triggers"` property of your analytics configuration, accompanied by the `"tagName"` of the element you want to track.
 
diff --git a/extensions/amp-story/amp-story.md b/extensions/amp-story/amp-story.md
@@ -493,38 +493,11 @@ Example:
 </a>
 ```
 
-#### Integration with sidebar for stories
-
-`amp-story` supports the use of `amp-sidebar` with a few limitations and caveats. See the [Sidebar for Stories documentation](https://amp.dev/documentation/components/amp-sidebar?format=websites#sidebar-for-stories) for more details.
-
-By using branching and `amp-sidebar`, you can create stories that have a table of contents. To do this, make use of URL fragment parameter.
-
-The following example demonstrates a table of contents inside of an `amp-sidebar`. The table of contents has a link to a specific story page, and and out-link to a different website.
-
-```html
-<amp-story id="story" standalone>
-  <amp-sidebar id="sidebar1" layout="nodisplay">
-    <ul>
-      <li><a href="#page=bacon-page"> Bacon page </a></li>
-      <li><a href="https://www.amp.dev"> External Link </a></li>
-    </ul>
-  </amp-sidebar>
-
-  <amp-story-page id="bacon-page">
-    <amp-story-grid-layer>
-      <p>Bacon, of course!</p>
-    </amp-story-grid-layer>
-  </amp-story-page>
-  ...
-</amp-story>
-```
-
 #### Other components usable in AMP stories
 
 The following are other components usable in AMP stories that require some story-specific caveats.
 
 -   [amp-consent](https://amp.dev/documentation/components/amp-consent#prompt-ui-for-stories)
--   [amp-sidebar](https://amp.dev/documentation/components/amp-sidebar#sidebar-for-stories)
 -   [amp-twitter](https://amp.dev/documentation/components/amp-twitter)
 
 For more generally usable components see the [list of allowed children](https://amp.dev/documentation/components/amp-story#children).
@@ -847,7 +820,7 @@ With branching, AMP Stories now supports URLs in the form of:
 https://www.mydomain.com/good-story/#page=<page-id>
 ```
 
-where `page-id` refers to the unique id of an `amp-story-page`. You can also use the fragment parameter and the `page-id` value like an anchor link in some use cases. See [Integration with Sidebar for Stories](#integration-with-sidebar-for-stories) for an example.
+where `page-id` refers to the unique id of an `amp-story-page`. You can also use the fragment parameter and the `page-id` value like an anchor link in some use cases.
 
 ## Localization
 
