TNEW Digital Content Page - Design Inspiration

Ours is fairly basic: had to use zoom-out in Chrome to screenshot the whole page:

Looks great Gawain. I like the way you have put the Behind the Scenes video in there too.

Thanks for sharing.

Very nice, Gawain. FYI, there is a Chrome extension you might like called GoFullPage that does full page captures

For each of our TNEW Digital Content pages, I have chosen to embed a page from our www site so that I can leverage our CMS to pull various bits of content from our production landing pages. This also gives me even more control over when and how the video and other components are displayed.

The screenshot below is far from our flashiest example, but you can see how it works anyway. In this case, we wanted to include some details about the show, the synopsis and cast bios, etc. Sometimes we have a chat window for live Q&As. We host our own TNEW template, so the surrounding navigation and branding is from that, but within the white area is a tall-ish and responsive-ish iframe containing a page on our www site with the relevant content. This might be confusing -- happy to answer more questions about it!

I've crammed in some CSS to allow us to use this functionality for some restricted resources.

We use the TNEW Quick Start Template and can't access any "real" styling spots, so creativity was essential. Some of what you can see is from Styles written and stored in the Source view of the Digital Content Heading field*; some is adding the QST classes to things (e.g. the buttons). Everything you can see--assuming the screenshot ends up being legible--is ultimately just a link to content elsewhere, be it hosted PDFs, YouTube Playlists, a Tag page on our blog, etc.

* This is admittedly not a great place to store the code. Even though I've adjusted everything I can, the source code is appearing as part of the Page Title. I need to get it moved elsewhere, but have not managed to loop back to resolve this properly since confirming the problem with Support. It's not immediately visible in the tab (which is why it's not moved to higher priority), but it's there if someone mouses over, etc.).

Thanks Christian and Jamie. Really interesting to see what others are doing. Love the way you have implemented these designs.

These are great looking examples and quite inspiring! 

Have you all set up your /content viewing page before putting your content on sale? I'm asking because I'm unsure of how to go about testing the content of the page without making it visible to everyone who has already purchased it. We have our first digital production coming up and I want to confirm it's working before flipping the "available" switch in TNEW. 

You can work in your QA system and then Select All Copy Paste when you're ready. Or you can select a random (test) Production Season you want in your Live Environment, work everything out while looking at something no one else will see, and then Paste it all over to the real thing. You'll be on the wrong url and you may end up willfully ignoring a Title displayed somewhere, but the part you need to review will be fine.

The other idea I've had around this (brainstorming something this summer with Chris Bisgard) is to have one set of content stored at the Production Season level and another on a specific performance. We were thinking about how to do a really quick content update during irregular hours (e.g. change the language under the embed of a live stream event once it ends at 10pm). You'd be able to do all the work ahead of time, including full proofreading and link checks, and then have the late night task be merely a quick toggle of something being on. Anyway, I don't think either of us has pursued it so that above is quite half-baked, but food for thought, no?

This all being said, while I did all my proof of concept work completely out of site to the public, I really just work live to update. It's a very specific type of page, available to very specific people, in very specific instances and I'm comfortable assuming that it's pretty unlikely someone is using the page while I'm dropping in new links. If you can manage to do most of your work well ahead of when someone is trying to pull up the content, you probably have some leeway. (And I love <!-- commmenting --> code out between getting the set up figured out and making links actually live...)