When it comes to publishing reports online, organizations have two basic options: they can post a PDF online and promote downloads on their site via search, social media, and syndication strategies. Alternately, organizations can develop the report online in HTML, which allows them to supplement content with a number of interactive elements that can deepen engagement and impact. Each approach has pros and cons as it relates to workflow, cost, accessibility, design experience, and analytics. Part 1 of this series explored the traditional PDF-first approach, and how organizations large and small can push their PDF reports to do more. This article explores the pros and cons of the HTML-first approach, and then considers best practices for some common applications.
The HTML-first approach is growing in popularity, both among shorter publications and longer publications with high value audiences. At its core, the approach simple: rather than post a PDF of your report to your website, your website is the report. That digital experience often means deeper scrolling sites, and the structure could be anything from a single-page site to a multi-page mini-site broken down by chapter and section. There are a lot of benefits to this publishing workflow, especially when it comes to accessibility and flexibility—but there are some drawbacks as well.
Benefits of HTML-first Reports
Ready for anything. Perhaps the biggest difference between PDF-first and HTML-first online reports is that the latter is designed to be consumed online and can be responsive. That’s critical, given that the majority of our time is spent on mobile devices, which have historically been a poor user experience for consuming PDF content.
Deeper searchability. In addition to being more accessible to humans, HTML-first reports are also more accessible to machines. Not only are they easier to index and navigate, but mobile-friendly sites and content typically ranks higher for popular search engines like Google.
Open standards. When it comes to ADA compliance (see section 508), though PDFs have made great strides in accessibility, mobile-friendly web content still offers a superior opportunity for accessibility. What’s more, support for screen readers and other assistive technologies are built right into operating systems like iOS and Android.
Always up to date. One drawback of online PDFs is that once they are released, they’re out there; users download once and that’s generally it. With HTML reports, content can be updated and refreshed, providing a more natural environment for living content and continued audience engagement.
End-to-end analytics. With PDF reports, the download represents the final trackable event for audience engagement; with online reports, technologies like Google Analytics and Clicktale can get valuable insights throughout content consumption process, so you know who’s interacting with what report content and for how long. That’s an invaluable feedback mechanism for publishers, and can also provide extensive insight into how reader-focused initiatives like social media campaigns might influence engagement and other goals.
Drawbacks of HTML-first Reports
HTML-first requires an investment. While most publishing teams can easily support a PDF-first workflow, HTML-first can be a bit of an adjustment. It requires authors to think as web designers and structure their content around an engaging user experience, rather structure a pleasant PDF-based experience around the content. Until the team gets up to speed with a new workflow, the HTML-first approach can mean greater overall effort, time, and budget than creating an equivalent PDF-based experience.
Long, sophisticated reads are more challenging online. Online users have notoriously short attention spans—most readership drops precipitously after about 500 words. Longer reads can compound the cognitive load, especially when the sophistication of the content requires information to be processed contextually. The best way to counter any adverse effects on the user experience is to chunk content into bite sized pieces, create a navigable and intuitive structure, and offer callouts and takeaways to create a more visually robust presentation.
Printable PDFs feel more permanent. There is a persistent perception that while anyone can post anything content online, PDFs are official and somehow more permanent. Even when the content is exactly the same, PDFs are the defacto digital hard copy, and that probably won’t go away anytime soon.
Given these pros and cons, many organizations would be well served by the HTML-first approach. It’s an excellent option for organizations with smaller and simpler publications who can adapt well-designed graphics to web layouts and complement them with web-only formats like video. It’s also a great option for organizations who publish longer reports for large audiences that could benefit from robust interactive elements and analytics, such as the IPCC’s National Climate Assessment. While the rationale for adopting the HTML-first approach may be different for each organization, but there are clear best practices that allow any organization can adopt to maximize the impact and engagement their reports generate with their audiences.
Best practices for HTML-First
- Break your content down into bite sized pieces. How do you eat an elephant? One bite at a time, of course. Chunk your reports into small pieces; make them as appealing as possible by offering provocative graphics, pull-quotes, and other visual devices. The public has a voracious appetite for online content— we just need to make it easier for them to nourish themselves.
- Embrace the familiar. Common mental models and content structures can help decrease the cognitive load and help users focus on what matters most. When in doubt, it’s hard to beat the standard three-act structure to ensure your reports have a beginning (setup), middle (confrontation), and end (resolution).
- Set your content free. Great content wants to be shared; make it easy to share your content by creating content blocks for images, stats, pullquotes, charts, and other graphics. Off the shelf technologies like ShareThis provide an easy way to configure sharing for multiple media platforms, and provide a fairly robust analytics layer so you can see how these resources are performing beyond your website.
- The user is always right. While the HTML-first approach has great value for mobile users and the publishing organization, some readers simply prefer PDFs and print. Make it easy for them by providing prepackaged PDF versions of the report and make sure that they do justice to the HTML version; there’s nothing worse than making users feel like second-class citizens based on their format preference.
- Nudge users towards preferred behaviors for continued engagement. Speaking of preferences, don’t forget that a well-placed call to action can bridge the gap between audiences who are merely informed and those who advocate. With a PDF report, the best you may get is to have someone pass the report on; with an HTML report, you can have users share content through social media and directly with contacts; they can sign petitions, contact stakeholders, and make donations to drive impact for your cause.
Of course, there are ways to make the HTML-first report approach work even better for you. If you’d like to explore how we can help your particular organization, please get in touch!
Projects & Insights
Decoding the Website Design Process
Not sure what to expect from the website redesign process? Confused by intimidating j
World Cocoa Foundation
Incorporating Concept Boards into Our Design Process
About a year ago, we started incorporating concept boards into our design process as