Plan działania projektu AMP
The ongoing development of AMP is conducted in working groups, each with knowledge or interest in a specific area of AMP.
To make their work visible to the community all groups provide regular status updates with details of what they have accomplished and what's up next.
All of the updates listed here are available as issues on GitHub and we'd love you to join the conversation there!
Select working groups
AMP for Email
Status Update Wed Mar 04 2020Highlights
- A lot of consensus on standardization efforts
WG Meeting Notes (12/13, 1/10, 2/13)
- Unified sender registration form still in review across providers
- Consensus on allowing CSS attribute selectors in spec
- Consensus on banning
AMP-Redirect-To
feature inamp-form
- Consensus on standardizing
meta
-based whitelists (https://github.com/ampproject/amphtml/issues/27094) - Consensus on allowing
input[type=button]
in spec, links withtel:
URI scheme - Reviewed process proposal for incremental adoption of new AMP components
- Discussed optional enforcement of email CSS rules in validator
- Discussed standardizing enforcement of DMARC
- Discussed standardizing email "hyper-collapsing"
- Discussed standardization of MIME tree corner cases
- Continued reviewing new email auth proposal
- Created new "AMP for Email Ecosystem" group and Slack channel
Focus areas
- Standardizing AMP for email behavior across providers by using AMP4EMAIL spec as single source of truth
AMP for Email
Status Update Wed Dec 04 2019Highlights
- Held email mini-summit at ACS 2019 in NYC
- Outlook.com launches AMP for Email to developer preview
- VerizonMedia merged an OSS Java implementation of the AMP validator
- Gmail rolls out AMP for Email to Android
WG Meeting Notes (9/12, 10/17, 11/8)
- Working on unified sender registration process (shared form in review)
- Received feedback on proposed shared HTML/CSS whitelist standards
- Consensus on standardizing max email size (200KB), max template SSR size, etc. (#4)
- More discussion on "CORS for email" proposal (#7)
- New proposal for email sender authentication (ecosystem-friendly replacement for proxy assertion tokens)
- Discussed AMP validator versioning and mitigating version skew across providers
- Consensus on allowing limited CSS attribute selectors (e.g. useful for
amp-selector
) - Proposed new component in AMP4EMAIL spec:
amp-autocomplete
- Self-hosting AMP JS and rollout patterns
- New outreach channels for email senders and ESPs
Focus areas
- Standardizing AMP for email behavior across providers by using AMP4EMAIL spec as single source of truth
AMP for Email
Status Update Thu Aug 01 2019Highlights
- Planning in-person meeting at ACS 2019 in NYC
- Microsoft and VerizonMedia implementations still in progress
WG Meeting Notes (6/14, 7/12, 8/9)
- Expanded wg-amp4email GitHub membership
- Progress on alignment across provider-specific HTML/CSS whitelists and AMP4EMAIL spec
- Consensus on deprecating proxy assertion tokens to avoid senders potentially only supporting large providers
- Documented AMP viewer implementation guidelines
- Consensus on approach for shared sender registration/whitelisting (with long-term goal of not having a sender whitelist at all)
- Discussions on a new CORS mechanism specifically for AMP4EMAIL (#7)
- Discussions on standardizing AMP MIME part expiry, max size, and max number of AMP elements (#4)
Focus areas
- Adapting the AMP4EMAIL spec to avoid potential ecosystem fragmentation
/cc @jasti
AMP for Email
Status Update Wed May 01 2019Highlights
- Launched in Gmail in March!
- Commitment from Microsoft, Yahoo, and Mail.ru
- AMP Conf '19: "AMP for Email: Pushing the boundaries of email with AMP"
- Early Gmail partner results are promising: 2x CTR for one, 60% higher CTR and 60% higher conversions for another.
WG Meeting Notes (5/10)
- Shared goal: AMP4EMAIL spec is the source of truth for rendering compatibility in email providers
- Corollary: Shared sender tooling that works across providers
- Corollary: Migrating provider-specific whitelists (HTML/CSS) to AMP4EMAIL spec
- Implementation details of provider adoption e.g. integrating a production-grade AMP validator
- @ampproject/wg-caching is investigating open-sourcing internal C++ validator
- Discussed 3P authentication with proxy assertion tokens
- Discussed wg-amp4email GitHub membership
Focus areas
- Cross-provider compatibility per AMP4EMAIL spec (above)
- Allowing more components in AMP4EMAIL e.g. amp-animation, amp-analytics
/cc @jasti