AMP Archives - OpenJS Foundation

Aug 13

An update on how AMP is served at the OpenJS Foundation

By Robin Ginn AMP, Blog, Project Update

When the AMP project moved to the OpenJS Foundation in 2019, our technical governance leaders shared a plan to separate the AMP runtime from the Google AMP Cache, and host the AMP runtime infrastructure at the vendor-neutral OpenJS Foundation. OpenJS is happy to report that this complex task of re-architecting the AMP infrastructure is making tremendous progress thanks to input and guidance from the AMP Technical Steering Committee (TSC) and AMP Advisory Committee, as well as thanks to the AMP Project and OpenJS teams for coming together despite the work and life challenges that were sometimes faced during the pandemic.

About AMP

AMP is a multi-stakeholder open source project used across a broad range of organizations to increase web performance. It’s a web component framework with a collection of complementary technologies that help publishers easily create websites that load quickly and predictably on different networks and devices.

Today AMP powers nearly 10 billion web pages worldwide, and is implemented by Google, Microsoft Bing, Pinterest and Pantheon, among others.

An AMP Cache is a cache of validated AMP documents published to the web, which allows the documents to be served more quickly than if they were generated by the original site each time they were displayed. Two of the largest AMP Caches are operated by Google and Microsoft, each of whom use the foundations developed by the AMP open source project to build their own commercial AMP Cache. This is a similar model to how most commercial products are built today with open source projects such as Linux and other JavaScript technologies such as Electron and Node.js.

Understanding how the AMP runtime will be served moving forward

The AMP runtime is a piece of JavaScript technology that a developer can add to their website to be able to use AMP components for building their website. By using AMP components, their pages become eligible to be hosted by an AMP cache. Some websites may choose to host the AMP runtime files themselves, while others may want to rely upon the AMP runtime soon hosted by the OpenJS Foundation to deliver the latest version of the code on demand. Ultimately, the choice is up to the developer. Please note that documents served from the Microsoft or Google AMP Caches will still download the runtime from the specific AMP Cache itself.

The AMP runtime itself is developed openly and transparently in the AMP Performance Working Group. This part of AMP will not change, as the goal in moving to the OpenJS Foundation was to ensure this work could continue under a vendor-neutral nonprofit, and this is still a high priority. What’s new is that after disentangling the AMP runtime from the Google AMP Cache, the OpenJS Foundation will manage the servers that deliver the AMP runtime files (the download server and the CDN). As planned, the OpenJS Foundation has been involved in the implementation of hosting the CDN and has been spending additional time to fully understand the technical requirements.

Hosting project infrastructure is a core service of our Foundation – it’s one of many ways we help maintainers manage the stability and delivery of their open source projects. The way OpenJS hosts the AMP runtime infrastructure will be very much like how we support the infrastructure for the popular jQuery CDN, which performs a similar function and distributes 2.2 petabytes of jQuery libraries per month. We are working with Cloudflare to host the AMP runtime CDN. OpenJS Foundation projects benefit from the goodwill of Cloudflare’s contribution to open source through its free Cloudflare Enterprise program, in addition to other CDN providers who support other OpenJS communities.

As an umbrella organization, the OpenJS Foundation has a governance model that gives a strong voice to its projects. Each of the projects are run independently at the direction of their core maintainers or Technical Steering Committees, as is this case with the AMP TSC. At the same time, OpenJS takes on the non-development aspects of the projects, ranging from infrastructure support to marketing, to help our projects grow and get better every day.

We are thrilled to be making this change to help the open source AMP Project continue to grow and diversify its contributors as they all work to make great experiences for the web.

If you have any questions about OpenJS please reach out to me at rginn@openjsf.org, or on our Slack workspaces: OpenJS Foundation or AMP. If you have any AMP Project specific questions please feel free to reach out via GitHub.

Posted by Robin Ginn, Executive Director, OpenJS Foundation

Dec 18

Love12

AMP Project Case Study: VOGSY

By rromoff AMP, Blog, Case Study

VOGSY Improves Services Firms’ Quote-to-Cash Speed by 80% with AMP-powered dynamic emails

The full case study was originally published on the AMP website. AMP is a hosted project at the OpenJS Foundation.

VOGSY is a professional services automation solution built on Google Workspace. By offering a single source of engagement to efficiently manage projects, resources, tasks, timesheets and billing, VOGSY streamlines services firms’ business operations from quote to cash, preventing handoff delays between sales, project delivery, and accounting teams.

Challenge

VOGSY was facing challenges due to siloed departments and disparate tools. Seeing an opportunity to never drop the quote-to-cash baton, VOGSY implemented AMP For Email to send actionable workflow emails directly to its users’ inboxes.

Results

The results of using the open source project led to huge efficiency gains for VOGSY clients including an 80 percent increase in approval speed for invoices, timesheets, quotes and expenses.

To read more about the benefits for VOGSY read the full case study: https://amp.dev/success-stories/vogsy/

Oct 29

Love13

OpenJS Foundation AMA: AMP Project TSC

By rromoff AMA, AMP, Blog, Project Updates

AMP Project joined the OpenJS Foundation this past summer as a Growth project, aiming to create a more “user-first” open web experience for all. In this AMA, users were able to ask questions via Twitter (#AskAMP) and live YouTube chat. This AMA followed AMP Fest, which can be viewed here. AMP Fest focuses on content where participants could “learn about the latest ways the community is working to make the web better for everyone – publishers, platforms, advertisers, creators, and of course, users.”

Moderated by Naina Raisinghani, the AMA was a way to learn more about the project with David Strauss, Chris Papazian, Dima Voytenko, Malte Ubl, Saulo Santos, Kasiana McLenaghan, and Rudy Galfi.

Questions ranged from what project individuals were most excited about to whether there should be ramifications or praise for net neutrality or the lack thereof. The talk took a mix of inquiries from chat and preset questions.

The full AMA is available here: OpenJS Foundation AMA – AMP Project

Timestamps

0:00 Brief Introduction

1:09 Introduction

4:42 AMP Fest Recap

6:10 AMP Projects You’re Excited About?

9:50 Can TSC Share What Platforms Support AMP?

11:47 What Is The Most Critical Part of Stories?

15:25 What’s One Use Case For AMP In Email?

19:20 Does the TSC Have Any Thoughts On NYT Content Application Framework Proposal?

25:20 What Improvements Does The TSC Want To Make In The New Year?

31:35 Will Websites Need AMP and HTML To Get Picked Up By Publishing Platforms?

40:20 More Approachable Architectural Options For HTML Conversion On High Volume Sites

43:58 Do You See The Project Working On Components Or User-Built Components

48:44 Should Publishers or Companies Be Encouraged or Penalized For Prioritizing Websites?

50:45 Are There Any Updates On AMP Runtime Giving a PWA For Navigating Amongst AMP Pages. Any Update?

52:00 Any Chance That People Will Be Able to Embed>React>AMP as Opposed to Embed>AMP>React?

56:00 Closing Thoughts

Sep 16

Love4

AMP Advisory Committee 2020 election

By rromoff AMP, Blog

The following blog was originally posted on APM.dev. AMP is a growth project at the OpenJS Foundation. It was posted by Tobie Langel and Jory Burson on behalf of the AMP AC.

AMP’s development is stewarded by an open governance system of multiple working groups and two committees: the Technical Steering Committee (TSC), which is responsible for the project’s direction and day-to-day operations, and the Advisory Committee (AC), which provide valuable perspective, stakeholder input, and advice to the TSC and to working groups.

An important goal of this governance structure is to ensure that the voices of those who do not contribute code to AMP, but are nonetheless impacted by it, get heard. This responsibility is shared across all contributors and governing bodies but falls particularly on the shoulders of the AC, which has a duty to ensure its membership is as representative and diverse as possible.

The AC is opening its call for nominations. We hope you will consider joining it. The AC is looking for candidates who will bring new perspectives and insight from AMP’s various constituencies: the industries adopting AMP to deliver content to their users, such as the publishing industry and e-commerce; the tech vendors whose solutions help power these industries, such as content delivery networks, web agencies, tooling providers, or payment providers; the industry experts focusing on topics such as accessibility, internationalization, performance, or standardization; and end-users and their representatives, such as consumer advocates. This list is by no means exhaustive. All candidates are welcomed and encouraged to apply, but preference will be given to those who bring an underrepresented perspective to the AC and help broaden its horizon.

For a better understanding of the AC’s work and membership responsibilities, read the member expectations document, working mode document, and minutes of past meetings. Also have a look at its GitHub repository and in particular its project board.

The AC is fully distributed—it spans over nine time zones—working asynchronously over email and GitHub issues (although its work isn’t technical in nature). It meets every other week over video conference, and ordinarily every six months face to face (note that there are no face-to-face meetings planned for the remainder of 2020 or the first half of 2021 at this time).

If you have questions, feel free to reach out to Tobie Langel or Jory Burson, AC facilitators.

If you’re interested in joining the AC, please apply.

We will be collecting new applications until Friday, October 2 at 23:59 AoE (Anywhere on Earth). The AC will elect its new members through a consensus based process and will announce the results on Monday, October 20.

Aug 27

Love6

Project Update: Official AMP Plugin for WordPress

By rromoff AMP, Announcement, Blog, Project Update

Success with WordPress,
powered by AMP

The missions of the WordPress and AMP open source projects are very well aligned. AMP, a growth project at the OpenJS Foundation, seeks to democratize performance and the building of great page experiences, which is at the core of WordPress’ goal of democratizing web publishing.

Today the AMP team is very excited to release v2.0 of the Official AMP Plugin for WordPress! Lots of work went into this release, and it is loaded with many improvements and new capabilities in the areas of usability, performance, and flexibility. Read on to learn more, or check out the official AMP Blog for the full release notes.

AMP brings “performance-as-a-service” to WordPress, providing out-of-the-box solutions, a wide range of coding and performance best practices, always up-to-date access to the latest web platform capabilities, and effective control mechanisms (e.g. guard rails) to enable consistently good performance. AMP’s capabilities, and the guard rails it provides allow WordPress creators to take advantage of the openness and flexibility of WordPress while minimizing the amount of resources needed to be invested in developing and maintaining sites that perform consistently well.

The Official AMP Plugin for WordPress is developed and maintained by AMP project contributors to bring the pillars of AMP content publishing at the fingertips of WordPress users, by:

Automating as much as possible the process of generating AMP-valid markup, letting users follow workflows that are as close as possible to the standard workflows on WordPress they are used to.
Providing effective validation tools to help dealing with AMP incompatibilities when they happen, including aspects of identifying errors, contextualizing them, and reporting them accurately.
Providing support for AMP development to make it easier for WordPress developers to build AMP compatible ecosystem components, and build websites and solutions with AMP-compatibility built in.
Supporting the serving of AMP pages on Origin, making it easier for site owners to take advantage of mobile redirection, AMP-to-AMP linking, minimization of AMP validation issues to surfaced in Search Console, and generation of optimized AMP pages by default.
Providing turnkey solutions for segments of WordPress creators and publishers to be able to go from zero to AMP content generation in no time, regardless of technical expertise or availability of resources.

To learn more about the AMP in WordPress, please check the release post on the official AMP Project Blog. If you haven’t tried it already, download the plugin today and get started on the path of consistently great performance for your WordPress site! And, if you are interested in becoming a contributor to the AMP Plugin for WordPress, you can engage with us in the AMP plugin github repository.

AMP