Skip to:
Content

BuddyPress.org

Opened 8 years ago

Closed 8 years ago

#6927 closed idea (wontfix)

Support AMP (Accelerated Mobile Pages)

Reported by: slaffik's profile slaFFik Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Core Keywords:
Cc: espellcaste@…

Description (last modified by slaFFik)

See this: http://thenextweb.com/dd/2016/02/24/wordpress-goes-all-in-with-googles-speedy-pages-project-enabling-it-for-everyone/ :

Automattic, the company behind WordPress.com, said today that it’s enabling AMP by default for all WordPress blogs. That means that hosted WordPress users will get super-fast page loads when visitors come to their sites from Google results and they don’t need to change anything.

There is an Automattic plugin for that: https://wordpress.org/plugins/amp/
AMP Project page: https://www.ampproject.org/

I propose to consider adding support for this into BP core. That will provide both faster page loads and a small boost from search engine. Everyone loves search engines. We have to :(

Change History (9)

#1 @slaFFik
8 years ago

  • Description modified (diff)
  • Summary changed from Support AMP to Support AMP (Accelerated Mobile Pages)

#2 @slaFFik
8 years ago

  • Description modified (diff)

#3 @slaFFik
8 years ago

  • Type changed from defect (bug) to idea

#4 @r-a-y
8 years ago

  • Component changed from Not sure to Component - Core
  • Milestone changed from Awaiting Review to Future Release

Specs here:
https://www.ampproject.org/docs/get_started/create_page.html

Bare minimum required:

  • Start with the doctype <!doctype html>.
  • Contain a top-level <html ⚡> tag (<html amp> is accepted as well).
  • Contain <head> and <body> tags (They are optional in HTML).
  • Contain a <link rel="canonical" href="$SOME_URL" /> tag inside their head that points to the regular HTML version of the AMP HTML document or to itself if no such HTML version exists.
  • Contain a <meta charset="utf-8"> tag as the first child of their head tag.
  • Contain a <meta name="viewport" content="width=device-width,minimum-scale=1"> tag inside their head tag. It’s also recommended to include initial-scale=1.
  • Contain a <script async src="https://cdn.ampproject.org/v0.js"></script> tag as the last element in their head (this includes and loads the AMP JS library).
  • Contain the following in their <head> tag: <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
  • Replace <img> tags with <amp-img>
  • Add amphtml meta to <head>: <link rel="amphtml" href="https://www.example.com/url/to/amp/document.html">

Most of the things listed above are theme-related, so it doesn't make much sense for BuddyPress to make those changes.

I'm thinking we just create a supplementary addon to whatever WordPress AMP plugin becomes the standard. This shouldn't be a BP core thing unless WP rolls AMP support into core.

On our side, the amphtml and canonical meta links are what we would need to add. Plus, there are also styling implications for our bundled template packs:
https://www.ampproject.org/docs/get_started/create/presentation_layout.html

#5 @hnla
8 years ago

All CSS must be inline and size-bound

Well that's not 'Inline' that's 'Embedded' not that that makes it better. Probably guilty of skimming over the docs and overreacting but this just got me cursing! Not sure I'll personally look further at this project and frankly not sure how one would implement for a standalone WP site with all that comes with those sites i.e BP.

#6 @espellcaste
8 years ago

  • Cc espellcaste@… added

@r-a-y Is there any goal in the near future of integrating AMP support into WordPress core?

Last edited 8 years ago by espellcaste (previous) (diff)

#7 @DJPaul
8 years ago

  • Milestone changed from Future Release to Under Consideration

#8 @r-a-y
8 years ago

Is there any goal in the near future of integrating AMP support into WordPress core?

I couldn't find a ticket on WP Trac for this.

Given what I stated in comment:4 and the diversity with themes in general, I could see why this would not be a core thing. For example, not all themes use the <!doctype html> header, which is required for AMP.

#9 @DJPaul
8 years ago

  • Milestone Under Consideration deleted
  • Resolution set to wontfix
  • Status changed from new to closed

No, we're not going to do this. This is Google's version of Apple's News, or Facebook's Instant Articles. It's aimed at big media publishers, and I'm not sure social content would fit into it nicely.

I've been doing some AMP work recently and there are significant restrictions around Javascript, which - at least - would pose a difficulty for our cropper tool. Not to mention, we'd need to distribute new templates, which is troublesome all by itself.

Note: See TracTickets for help on using tickets.