@westonruter do you need anything else for the blog integration?

OK, so right now the blog is doing:

#searchTriggerOpen,
.ap-o-burger-menu-label {
	display: none;
}

This styling could be removed with this deployed?

@westonruter Is there a way to test this before deploying?

Is there a dev URL for this change that we can point the blog to?

@sebastianbenz OK, so apparently this was deployed? So this can be tested now… and it breaks:

The issue appears to be that the fragment being pulled in is using optimized AMP, which the AMP plugin does not allow as input, causing them to be stripped out by the sanitizer:

It's currently not broken on https://blog.amp.dev, but it is broken on a https://test-amphtml-blog.pantheonsite.io/ presumably because the cached header.html hasn't expired yet, but within a week it will be broken once the transient expires.

I'll preemptively add .ap-o-search-container { display:none } to blog.amp.dev to prevent the breakage from showing up.

For some reason the [src] attribute on amp-list is getting dropped when the https://amp.dev/shared/header/ fragment is imported, and this is causing what @mattludwig pointed out:

The reason for the AMP validation error is that the validator is not properly accounting for data-amp-bind-src as being an alias for [src]. I've filed a bug: ampproject/amphtml#24661

For a quick fix, I've just stripped out the div#searchLayer until this is resolved.

@sebastianbenz What CSS specifically does this new search component require? It seems like frontend/scss/components/organisms/search.scss. Anything else?

@sebil, can you confirm adding /css/components/organisms/search.css to the blog's CSS is enough to successfully render search for the blog?

@matthiasrohmer there is also /components/molecules/search-trigger.css which is included via the header markup. Besides that it should be enough, yes.