WordPress.org
Get WordPress

Plugin Directory

Changeset 1339037


Ignore:
Timestamp:
01/29/2016 04:38:25 PM (10 years ago)
Author:
pagefrog
Message:

update to readme

File:
1 edited

Legend:

Unmodified
Added
Removed

  • pagefrog/trunk/README.txt

    r1339025 r1339037  
    88License URI: http://www.gnu.org/licenses/gpl-2.0.html
    99
    10 PageFrog helps you easily publish and manage content for mobile formats such as Facebook Instant Articles and Google AMP HTML.
     10Easily publish and manage your content directly from Wordpress to Facebook Instant Articles and Google AMP HTML.
    1111
    1212== Description ==
    1313
    14 PageFrog helps you easily publish and manage content for mobile formats such as **Facebook Instant Articles** and **Google AMP HTML**.
    15 
    16 PageFrog offers powerful plugins that integrate directly into content management systems, allowing publishers to easily optimize content for native mobile formats such as Facbeook Instant Articles and Google AMP HTML. From live previews to managing ad units, PageFrog plugins include a full suite of tools for managing publications across different mobile apps and platforms including Facebook, Twitter, LinkedIn, Google, Apple News, Snapchat, Flipboard, Feedly, and more.
    17 
    18 
    19 
    20 = PageFrog Features =
    21 
    22 * **Support Every Platform** - Launching with Facebook Instant Article and Google AMP support, we're committed to bringing support for your content to every platform and ecosystem.
    23 
    24 * **Content Optimization** - Rather than following documentations to build a custom layout from scratch, PageFrog automatically takes an existing website and optimizes the page structure to fit the requirements of Instant Articles and AMP HTML.
    25 
    26 * **Quality Assurance** - PageFrog offers real-time previews of how content will appear on various mobile formats. This allows publishers to write and see the end result in real-time, ensuring that the content always appears professional across all platforms and formats.
    27 
    28 * **Branding and Styling** - Each mobile format enforces its own unique styling restrictions. Rather than building custom layouts for each format, PageFrog allows publishers to handle all branding and styling customizations within the writing interface.
    29 
    30 * **Analytics** *(coming soon)*
    31 
    32 * **Ad Management** *(coming soon)*
    33 
    34 * **Integrations** *(coming soon)*
    35 
    36 * **Article Builder** *(coming soon)*
    37 
    38 Create the most engaging content by leveraging advanced features made possible with native mobile formats. Use PageFrog to build articles and include custom elements such as audio captions, tilt-to-pan photos, interactive maps, and more.
     14The PageFrog plugin allows you to easily publish and manage your content directly from Wordpress for Facebook Instant Articles (FBIA) and Google Accelerated Mobile Pages (AMP).
     15
     16**What are Facebook Instant Articles and Google Accelerated Mobile Pages?**
     17
     18FBIA is a new mobile format developed by Facebook, which can be served to visitors accessing your content from the Facebook mobile app. AMP is a new mobile format developed by Google, which can be served to visitors accessing your content from Google, Twitter, LinkedIn, and Pinterest mobile apps.
     19
     20**Why should I optimize my content for FBIA and AMP?**
     21
     22The FBIA and AMP formats are built to load instantly on mobile devices and designed for higher engagements, resulting in improved News Feed Ranking and greatly benefits Search Engine Optimization.
     23
     24*Increase traffic and discoverability*
     25
     26Search engine optimization and social media discovery are extremely important when it comes to generating traffic. Both Facebook Newsfeed Ranking and Google PageRank rely on performance metrics such as page load times and visitor engagements to rank articles.
     27
     28Native mobile formats such as FBIA and AMP offer unprecedented advantages when it comes to page performance. These mobile formats preload content and cache media files, allowing articles to load instantly for readers on mobile devices.
     29
     30*Boost engagements and shares*
     31
     32FBIA and AMP offer opportunities for true mobile experiences to captivate and engage readers. These formats allow for a number of advanced features specifically designed for mobile content such as audio captions, interactive maps, tilt-to-pan photos, and more.
     33
     34These formats are deeply embedded into mainstream mobile apps such as Facebook, Twitter, LinkedIn, and Pinterest. FBIA and AMP offer specific layouts designed to maximize social engagements such as Likes and Comments.
     35
     36
     37**What can I do with the PageFrog plugin?**
     38
     39*Content Optimization*
     40
     41Rather than following FBIA and AMP documentations to build custom layouts from scratch, PageFrog automatically takes your existing content and optimizes the page structure to fit the requirements of FBIA and AMP.
     42
     43*Quality Assurance*
     44
     45PageFrog offers real-time previews of how your content will appear on FBIA and AMP. This allows you to write content and see the output as you’re writing, ensuring that your content will always appear professionally on FBIA and AMP.
     46
     47*Branding and Styling*
     48
     49FBIA and AMP enforce their own unique styling restrictions. Rather than building custom layouts for each format, PageFrog allows you to handle all your branding and styling needs within the WordPress interface.
     50
     51*Analytics and Insights*
     52
     53PageFrog allows you to connect multiple third party analytics to your FBIA and AMP pages using Google Analytics, Chartbeat, Parse.ly, and more. PageFrog can also display your analytics data from Facebook Insights directly within WordPress.
    3954
    4055== Installation ==
    4156
    42 1. Upload the folder to the `/wp-content/plugins/` directory
    43 1. Activate the plugin through the 'Plugins' menu in WordPress
    44 1. Enable Facebook Instant Articles and/or AMP through the PageFrog Settings
     57**From your WordPress dashboard**
     58
     591.  Visit ‘Plugins > Add New’
     601.  Search for ‘PageFrog’
     611.  Click Install Now
     621.  Activate 'PageFrog from your Plugins page
     63
     64**From WordPress.org**
     65
     661.  Download PageFrog (.zip file)
     671.  Go to your WordPress dashboard and visit ‘Plugins > Add New’
     681.  Click ‘Upload Plugin’ and upload the PageFrog (.zip file)
     691.  Activate PageFrog from your Plugins page
     70
     71**Once Activated**
     72
     731.  Visit ‘Mobile Formats > Setup’
     741.  Follow on screen instructions to configure FBIA and AMP
     75
     76**Once Configured**
     77
     78* You can enable or disable FBIA or AMP for each individual post at any time. To do this, simply edit a post and use the checkboxes to turn it on or off.
     79* You can preview your posts in FBIA and AMP as you’re writing. When creating or editing a post, the Mobile Preview panel offers a preview in real-time. Use the dropdown to preview different formats.
     80* You can customize your branding and style your posts under ‘Mobile Formats > Styling’. Follow the on screen instructions to customize your posts.
     81* You can connect third party analytics under ‘Mobile Formats > Analytics’. Select the platform you’d like to connect and follow the on screen instructions to integrate it.
    4582
    4683== Frequently Asked Questions ==
    4784
    48 = Why optimize content for Instant Articles and AMP HTML? =
    49 
    50 Learn more about [Facebook Instant Articles](https://instantarticles.fb.com/) or [Google AMP HTML](https://www.ampproject.org/)
    51 
    52 *Increase Traffic*
    53 
    54 Search engine optimization and social media discovery are extremely important when it comes to generating traffic. Both Facebook Newsfeed Ranking and Google PageRank rely on performance metrics such as page load times and visitor engagements to rank articles.
    55 
    56 Native mobile formats such as Facebook Instant Articles and Google AMP HTML offer unprecedented advantages when it comes to page performance. These mobile formats preload content and cache media files, allowing articles to load instantly for readers on mobile devices.
    57 
    58 *Boost Engagements*
    59 
    60 Facebook Instant Articles and Google AMP HTML offer opportunities for true mobile experiences to captivate and engage readers. These formats allow for a number of advanced features specifically designed for mobile content such as audio captions, interactive maps, tilt-to-pan photos, and more.
    61 
    62 These formats are also deeply embedded into social media apps such as Facebook, Twitter, and LinkedIn. Available layouts and design options are designed to maximize social engagements such as Likes and Comments.
    63 
    64 
    65 = Why use PageFrog to manage mobile content? =
    66 
    67 *Format Restrictions*
    68 
    69 Building for native mobile formats is nothing like traditional mobile optimization. Publishers cannot simply create a responsive layout adapting to different screen sizes. In order to publish content to each of these formats, the code structure must follow a set of special rules and requirements.
    70 
    71 Rather than studying the documentations and building custom layouts from scratch, PageFrog offers simple plugins designed to help publishers instantly and easily publish content to mobile formats such as Facebook Instant Articles and Google AMP HTML.
    72 
    73 *Quality Assurance*
    74 
    75 Content can appear very differently on desktop computers than on mobile devices. Moreover, content on Instant Articles can look very different than content on AMP HTML as well. Previewing your content on an increasing number of mobile formats can be time consuming.
    76 
    77 PageFrog plugins offer live previews directly within content management systems, allowing publishers to ensure that articles will display appropriately across various platforms. Intelligent notifications and warnings are also delivered whenever published posts contain certain elements leading to suboptimal mobile display.
     85= What is Instant Articles? =
     86
     87Instant Articles is a tool for news publishers to distribute fast, interactive articles to their readers in the Facebook app.
     88
     89= How do Instant Articles work? =
     90
     91Rather than loading an article using a web browser, which takes over 8 seconds on average, Instant Articles load using the same fast tools we use to load photos and videos in the Facebook app allowing articles to load as much as 10 times faster than standard mobile web articles. Beyond just speed, Instant Articles allow publishers to provide the same high quality, fluid experience and interactivity that people expect from a mobile app. Instant Articles has been designed with extensive feedback from news publishers. Publishers can serve their own ads and keep that revenue, track readership in real-time and with comScore, and customize the presentation of articles to match their brand.
     92
     93= Will Instant Articles be required for publishers on Facebook moving forward? =
     94
     95No. Publishers have the option to participate in the Instant Articles program. Participating publishers retain full control of their content and publishing schedule, including how much to publish to Facebook. Standard article links will remain accessible from Facebook via the standard mobile browser for publishers that decline to participate. Our expectation is that people on Facebook will appreciate the enhanced accessibility of Instant Articles content, while publishers will see greater engagement for their content as a result.
     96
     97= Why would publishers want to participate in Instant Articles? =
     98
     99There are several benefits for publishers. Faster article loading allows readers to get to content as quickly as possible. Facebook’s experience with other media formats, such as auto-play video, has been that more rapid content loading generates increased content consumption and sharing. We believe Instant Articles will help publishers grow their businesses on Facebook.
     100
     101= Do publishers need to create original content for Facebook? =
     102
     103No. Instant Articles is simply a faster, mobile-optimized way to publish and distribute stories on Facebook, and it supports automated content syndication using standards like HTML and RSS. Content published as Instant Articles will also be published on the publishers’ websites.
     104
     105= How much effort is required for publishers to reconfigure their content for Instant Articles? =
     106
     107It’s a straightforward process for publishers to publish their articles in the Instant Article format because it uses HTML and RSS, standard ways for authoring articles on the web. Facebook translates articles authored for the web in HTML into the Instant Articles format. We also provide tools for publishers to preview articles prior to publication and make sure they display as they intended. Publishers who wish to embrace new elements like interactive maps and auto-play videos can use simple, well-documented HTML tags to enhance their content with rich-media features.
     108
     109= What types of articles work best for this format? =
     110
     111Instant Articles work for any type of article, from daily spot-news coverage to in-depth, longform features.
     112
     113= Do Instant Articles change how publishers or people share on Facebook? =
     114
     115No. Nothing about link-sharing changes. Publishers and readers link to articles just as they always have; there is no need to link or post an Instant Article differently. Each Instant Article is associated with a link, so when a friend or page shares a link in News Feed, readers see the Instant Article version if it is available.
     116
     117= Are Instant Articles available to everyone on Facebook? =
     118
     119For the moment, Instant Articles are only available to people who use Facebook’s iPhone app.
     120
     121= What happens if a reader is not on a device that supports Instant Articles? =
     122
     123People on a desktop computer or other device that doesn’t support Instant Articles will continue to link to the mobile web version of the article.
     124
     125= How will Instant Articles influence referral traffic? =
     126
     127Instant Articles display within the Facebook app, so readers no longer redirect to the publisher’s website. Facebook worked with publishers and comScore to enable Instant Articles views in Facebook’s app to count as traffic to the original publisher, just as they do on the mobile web.
     128
     129= Can publishers sell their own advertising on Instant Articles? =
     130
     131Yes. Publishers can sell in their articles and keep the revenue, or they can choose to use Facebook’s Audience Network to monetize unsold inventory.
     132
     133= How do publishers enroll to use Instant Articles? =
     134
     135Facebook is currently testing Instant Articles with a small set of publishers.  The Instant Articles program will expand to more publishers in the future. If would like to participate, please tell us about yourself and we’ll keep you updated.
     136
     137= What is the Accelerated Mobile Pages project? =
     138
     139The Accelerated Mobile Pages (“AMP”) Project is an open source initiative that came out of discussions between publishers and technology companies about the need to improve the entire mobile content ecosystem for everyone — publishers, consumer platforms, creators, and users.
     140
     141Today, the expectation is that content should load super fast and be easy to explore. The reality is that content can take several seconds to load, or, because the user abandons the slow page, never fully loads at all. Accelerated Mobile Pages are web pages designed to load instantaneously — they are a step towards a better mobile web for all.
     142
     143= What are the benefits of Accelerated Mobile Pages? =
     144
     145Speed matters and instant is the ideal. Research shows that the bounce rate can be as high as 58% for web pages that take nearly ten seconds to load. Using the AMP format will make it far more compelling for people to consume and engage with more content. But this isn’t just about speed and performance. We also want to promote enhanced distribution so that publishers can take advantage of the open web’s potential for their content to appear everywhere quickly — across all platforms and apps — which can lead to more revenue via ads and subscriptions.
     146
     147= How do Accelerated Mobile Pages work? =
     148
     149Accelerated Mobile Pages are just like any other HTML page, but with a limited set of allowed technical functionality that is defined and governed by the open source AMP spec. Just like all web pages, Accelerated Mobile Pages will load in any modern browser or app webview. AMP files take advantage of various technical and architectural approaches that prioritize speed to provide a faster experience for users. The goal is not to homogenize how content looks and feels, but instead to build a more common technical core between pages that speeds up load times.
     150
     151In addition, AMP files can be cached in the cloud in order to reduce the time content takes to get a user’s mobile device. Under this type of framework, publishers continue to control their content, but platforms can easily cache or mirror the content for optimal delivery speed users. Google has stated that it will provide a cache that can be used by anyone at no cost, though the cache (Google’s or otherwise) is not required. Other companies may build their own cache as well.
     152
     153In summary, the goal is that that the combination of limited technical functionality with a distribution system built around caching will lead to better performing pages, and increased audience development for publishers.
     154
     155= Why does the Accelerated Mobile Pages Project take an open source approach? =
     156
     157The initial companies involved in this early preview of the project want to make the mobile web work better for all — not just for one platform, one set of technologies, or one set of publishers. Making the project open source enables people to share and contribute their ideas and code for making the mobile web fast. This preview is just the beginning of that journey and we look forward to other publishers and technology companies joining along the way.
     158
     159= When will Accelerated Mobile Pages launch and what is the rollout plan? =
     160
     161On October 7th, 2015, the Accelerated Mobile Pages Project announced the release of the initial technical specification which will appear on GitHub, a broadly used repository for open-source content. We are also providing an early developer demo of what a faster mobile web can look and feel like with Accelerated Mobile Pages. More features and functionality will be added over the coming weeks, including functional support for subscription models as well as vendor support for advertising functionality. As more of this functionality becomes commonly available, we hope to see more and more major consumer platforms integrating AMP pages into their apps and services.
     162
     163= Who will be able to use Accelerated Mobile Pages? =
     164
     165The project is open to all players in the ecosystem – publishers, consumer platforms, and creators. In this early stage of the project, a group of publishers and platforms have come together to demonstrate how Accelerated Mobile Pages can transform the mobile web experience. They include platforms like Twitter and Google, tech players like ChartBeat and WordPress.com and publishers like Vox, The New York Times, The Guardian and Globo.
     166
     167= What type of content will work best using Accelerated Mobile Pages? =
     168
     169The goal is for all published content, from news stories to videos and from blogs to photographs and GIFs, to work using Accelerated Mobile Pages.
     170
     171= As a publisher, will making my content work for Accelerated Mobile Pages entail more work? =
     172
     173In short, not much. Since “AMP HTML” is built entirely out of existing web technologies, the development process mirrors the one publishers are already using today. Publishers can familiarize themselves with the AMP HTML specification on GitHub. For those used to the current process, we don’t expect a significant learning curve.
     174
     175= How can a publisher get content into AMP HTML? =
     176
     177Publishers and Content Management System (CMS) providers can develop an integration with their CMS to generate AMP content. We hope that all content management systems will add support for AMP HTML pages. For example, WordPress.com has announced that it will integrate the AMP framework. In addition to WordPress.com, we hope other commercial CMS providers will support the project in the weeks and months to come.
     178
     179= How can a consumer platform get involved in Accelerated Mobile Pages? =
     180
     181The project is open to all players, and existing members of the project are very enthusiastic to engage with consumer platforms on the initiative. Google will also open its cache for use for free by anyone, including to consumer platforms that would like to display AMP content in their environment.
     182
     183= How can an advertising or technology vendor get involved in Accelerated Mobile Pages? =
     184
     185Though we cannot guarantee that all vendor technology will function perfectly inside AMP files, over time we expect to release new functionality in the specification that will make it easier for your technology to integrate with the format.
     186
     187= How will advertising work on Accelerated Mobile Pages? =
     188
     189A goal of the Accelerated Mobile Pages Project is to ensure effective ad monetization on the mobile web while embracing a user-centric approach. With that context, the objective is to provide support for a comprehensive range of ad formats, ad networks and technologies in Accelerated Mobile Pages. As part of that, those involved with the project are also engaged in crafting Sustainable Ad Practices to insure that ads in AMP files are fast, safe, compelling and effective for users.
     190
     191= Will publishers be able to sell their own ad inventory? =
     192
     193Yes, as with their existing websites, publishers control their ad inventory and how they sell it.
     194
     195= How will subscriptions and paywalls work with Accelerated Mobile Pages? =
     196
     197It is a core objective of the Accelerated Mobile Pages project to support subscriptions and paywalls. Publishers and technologists will work together to build the best solutions for readers and publishers.
     198
     199= How are analytics being handled in this AMP format? =
     200
     201Ensuring publishers are able to get robust analytics insight is a core design goal for the project. While the analytics support in the demo release is very limited, the spec is expected to have support for collection of analytics information, and integrating with 3rd party systems without compromising the AMP file speed or size. Chartbeat and Parse.ly, two publisher analytics providers, are participants in the project.
     202
     203= Do publishers receive credit for the traffic from a measurement perspective? =
     204
     205Yes, an AMP file is the same as the rest of your site – this space is the publisher’s canvas.
     206
     207
     208== Screenshots ==
     209
     2101. Publish and manage your content for FBIA and AMP
     211
     2122. Write with a live preview of your content on FBIA and AMP
     213
     2143. Customize your branding and styling for FBIA and AMP
     215
     2164. Connect your analytics to track posts on FBIA and AMP
    78217
    79218
    … …  
    87226
    88227= 1.0.3 =
    89 *Release Date - January 28, 2016*
    90 
    91228* Launch release
    92229* Facebook Instant Articles Support (beta)
    93 * Accelerated Mobile Pages (AMP) Support (beta)
Note: See TracChangeset for help on using the changeset viewer.