We should allow publishers to specify arbitrary custom content to be shown in a sidebar. The API and documentation should make it clear that every platform has the ability to display or not display this content. The sidebar can contain both runtime-specified content (configurable by viewer) and publisher-specified content.
Some examples:

We can automatically show an affordance in the system layer:

I would love it if we could find a way to use <amp-sidebar>'s API (with some restrictions on validation when used within <amp-story>) to make this happen.
I think it may also make sense to introduce some concept like an <amp-story-system-layer> element that encapsulates custom system components like this, with the understanding that all custom system components are subject to be removed by the platform that is embedding the story.
I'm hoping @addieachan might have some bandwidth to take this on after her work on #15562.
This is a high priority issue but it hasn't been updated in awhile. @newmuis Do you have any updates?
@addieachan will be taking this on, and is currently in the process of designing this feature.
This is a high priority issue but it hasn't been updated in awhile. @addieachan Do you have any updates?
Hey @newmuis ,
How is this sidebar feature coming ? Really excited to see this.
Hi @psdtomanythings, #17836 has the implementation, but there are still some outstanding API decisions to be made. Due to the AMP contributor summit next week, this might not be decided until the following week, then the changes will take ~two weeks to roll out.
@newmuis - What are the plans for the AMP Sidebar's look and feel in desktop ?
@psdtomanythings on desktop, the plan is to place this next to the share pill in the top right corner:


Looks pretty cool.
Hey @newmuis ,
Can we just write the code for complete amp sidebar (i.e. HTML) or is there gonna be an API that automatically create a sidebar using some kind of JSON object ?
The plan is currently to allow amp-sidebar usage as it exists in AMP generally, with the exceptions that:
<body>, it will be somewhere within the <amp-story><amp-story>, so the only way to open the sidebar is the menu icon added automatically by the system.This is a high priority issue but it hasn't been updated in awhile. @addieachan Do you have any updates?
This is a high priority issue but it hasn't been updated in awhile. @addieachan Do you have any updates?
This is a high priority issue but it hasn't been updated in awhile. @addieachan Do you have any updates?
This is a high priority issue but it hasn't been updated in awhile. @addieachan Do you have any updates?
This went live with @bramanudom's #19540.
In AMP-story you are allowed to ad a SideBar but in doing so it appears there is no control over the i-amphtml-story-opacity-mask if you use an _on="tap:sidebar-right.close"_ . the mask stays in place when the sidebar closes and the user has to tap again on the mask to remove it.
The only option I found was to use [class*="i-amphtml-story-opacity-mask"] {display:none!important;} but the AMP does not like the !important so it does not pass verification.
Are there any parameters I am missing?
@JohnAJarboe this is a bug: #21050
Until that fix lands, your can still use sidebar without an explicit close control, and users can tap outside of the sidebar to close it
Yes, however the clientele we solicit are more in the 34-65 age bracket and prefer the obvious and tapping anywhere is not obvious. Users are more comfortable with explicit instructions. I have clients that are not aware that the three pancake stack is the icon for the menu.... anyway thanks and look forward to an options to "turn the mask off"
Most helpful comment
The plan is currently to allow
amp-sidebarusage as it exists in AMP generally, with the exceptions that:<body>, it will be somewhere within the<amp-story><amp-story>, so the only way to open the sidebar is the menu icon added automatically by the system.