Business Sponsor and Organization

Atlas team

Feature Description

The minimal Atlas Reader will have the following features:

• Ability to render HTML builds generated in Atlas
• Ability to render EPUBs
• Ability to use existing CSS styles from a project
• Ability to apply a global theme to several projects, to theme third-party EPUB content.
• Ability to preserve JS assets that are used by interactive features in book content. These assets should be included even in book previews.
• Ability to render a “preview” of a book
• Ability to search within a book using the SOLR API
• Ability to search across all books using the SOLR API
• Implement a 1 click buy option if a user does not own the book
• Appropriate caching for performance

Non Requirements include:

• PDF rendering.  PDF will be extremely challenging to render, so we will not natively display PDF in the reader.  Instead, we will convert PDF to HTMLBook.  The reader will still be able to get the original PDF, but the reader will aid in discovery and findability.
• Social features like commenting and sharing. The initial reader will only provide the reading experience.
• Uniform styling for EPUB.  Because we cannot control the source markup provided by distribution clients, we cannot develop uniform stylesheets against their markup.  Consequently, our best option is to render content in the style they provide.  

Success Criteria

• Increased content sales and discovery
• Enable paid distribution of new content types and forms created in Atlas reader, particularly video and live code.
• Enabling user facing previews for content search project
• Enable “members only” content that is accessible to customers who have enrolled in oreilly “members only” products [TBD] 
• Increase inbound referrals and conversion rates from social media (Twitter, etc) that can take advantage of new “preview” functionality
• Enable 2-3 paid “enhanced content projects” by the end of the year.  (An enhanced project is one that includes elements that are beyond a traditional book, such as videos, live code, assessments, or other elements.)

Maximum Level of Development Effort

XLarge.  We’ll need to break this BRD down into many smaller feature requirements.

Areas of Impact

Please X all areas of functionality that will need to be changed to incorporate this feature: