はてなブックマーク

Do you spend hours crafting the design of your Web Story only to find that it does not quite display right on older devices or on the biggest phones?  It can be tricky to develop content in a portrait-based aspect ratio and make it look great across devices. So to make testing easier, today the Web Story Team is releasing a tool that shows you the major design breakpoints of your Stories. Simply a

{{^prevUrl}} {{#result.components.length}} {{#initial}}Important Components{{/initial}}{{^initial}}Components{{/initial}} {{/result.components.length}} {{/prevUrl}} {{#result.components}}

This blog is part of a series that we are starting to share AMP’s roadmap with the wider web community. We first unveiled our vision of AMP as a Service on a spring morning in Tokyo at AMP Conf 2019, our flagship conference. We talked about how engineering teams can accelerate their workflow by using AMP. So what has changed since the last time we talked about AMP as a Service? And what does the f

Web Stories are a new, exciting medium for storytelling on the web powered by AMP. The format is based on the same concept as familiar Stories features in popular social networking apps but intended for more general purpose content from “how to apply lip gloss the right way” to a “travel guide through the Himalayas”. Importantly, Web Stories are just web pages. They have a URL on your web server,

{{^prevUrl}} {{#result.components.length}} {{#initial}}Important Components{{/initial}}{{^initial}}Components{{/initial}} {{/result.components.length}} {{/prevUrl}} {{#result.components}}

AMP now officially supports a technique called server-side rendering (SSR) which you can apply to your AMP pages to make them load even faster. Our tests show increases of up to a whopping 50% on the popular FCP metric. The Google AMP Cache has utilized this technique for a while, but now you can also use it on your own domain! Installing this extra optimization is especially important if you are

{{^prevUrl}} {{#result.components.length}} {{#initial}}Important Components{{/initial}}{{^initial}}Components{{/initial}} {{/result.components.length}} {{/prevUrl}} {{#result.components}}