Project

General

Profile

Actions
Copy link

Feature #72876

closed

AMP support?

Added by Christoph Werner about 8 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Could have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2016-01-21
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Hi!
Just want to through this in: Google is working on https://www.ampproject.org/how-it-works/
Could be big thing (maybe), wordpress is allready involved. Maybe something to think about.

Best,
Chris

Actions
Copy link
 #1

Updated by Benni Mack about 5 years ago

  • Status changed from New to Needs Feedback

Hi Chris,

thanks for your valuable input. We've implemented some "basic" functionality already for TYPO3 v9 to add the <html amp> tag optionally via TypoScript.

On top, we're still looking to add webp support for core (separate issue). For the rest of the amp functionality, we'll probably release this as a custom "amp" extension in the near future. Check out @david.steeb on slack for more information.

My company's website (b13.com) actually runs TYPO3 v9 with amp natively already. You should also check out "http/2" extension (see https://github.com/b13/http2)

All the best,
Benni.

Actions
Copy link
 #2

Updated by Benni Mack about 4 years ago

  • Status changed from Needs Feedback to Rejected
I will close this ticket now with the following reasons:
  • With TYPO3 v10.3 we now are able to inject only CSS which is needed (see AssetCollector Feature).
  • However, we've been in contact with the creators of AMP and they can never guarantee their API to be stable enough for TYPO3 to be using while keeping a 3-6 year compatibility on non-breaking changes. This means - we don't have a reliable API for that.

So in the end, TYPO3 is prepared to use AMP by default with a custom theme or distribution out-of-the-box, but shipping AMP is currently a no-go.

Actions
Copy link

Also available in: Atom PDF