-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Gutenberg] Extend existing core blocks for AMP specific functionality #1008
Comments
See #902 (comment) |
Update On Related Work Hi @postphotos,
In #1010, @miina is now working on a block that doesn't support AMP: 'categories' with a dropdown.
That would be good for this issue. |
Just FI that started looking into this and will add a possible "prototype" of the approach for discussing (based on adding |
Awesome. I'm looking forward to seeing that! |
Created a PR with initial take on the approach: #1026. Would be great to receive some feedback before continuing. |
We've talked about this before, but as part of this we'll need to make sure that any AMP components and attributes that get added to |
Request For Testing Hi @csossi,
|
verified in QA |
As a WordPress site running Gutenberg, my core/native blocks should have extended AMP-HTML markup features.
AC1: Extend core blocks which have validation errors so that the appropriate AMP markup is output to faithfully render the block when the page is served as AMP. This would be done via some combination of the render_callback that integrates with a new block sanitizer/preprocessor.
AC2: Further extend core blocks to leverage AMP functionality, such as layout.
The text was updated successfully, but these errors were encountered: