 Good afternoon WordCamp NYC. We have our final talk for today in the winter garden lecture. We have Marty Spellerberg and Zach Rothhauser. Marty, which one's Marty? Which one's Zach? Here we go. This is Marty and this is Zach, hooray! And so you know a little bit about them. Marty offers interactive design, development, and communications consulting to artists and museums. He's also the director of Spellerberg Projects, a cultural incubator and contemporary art gallery in Lockhart, Texas. Marty has 20 years experience in interactive design, including a decade working specifically with museums. Zach is a senior WordPress developer at WP Engine. He's worked in web development for the past six years, having spent time at several large agencies, freelancing, and now working for the marketing team at WP Engine. Hi everybody, please join me in giving a warm round of applause and welcome to Marty and Zach for their talk merging physical and digital experience, creating museum experience with WordPress, REST API, and React. We're going to walk you through the design process and some of the technology decisions and videos we asked, but it's like we're still moving along the way. We'll show you how WordPress can be used in some non-traditional projects that aren't exactly website. So yes, thanks for the introduction. Thank you, Marty. And I also want to shout out a couple members of our team who aren't here today. There was Renata Gras from a design studio in Chicago called Normal. A lot of what you're going to see is a amount of her talk, and our colleague at the Clifford Still Museum is Sarah Wommel. So this is the Clifford Still Museum in Denver. It's located right downtown in the larger district, and is adjacent to the Denver Art Museum, the first generation of abstract expressionist artists. But midway through his career, he stopped showing his work, but he didn't stop working, but he stopped showing. And when he died, it was little situated that his collection of work and his archives go to any U.S. city that would build a museum dedicated to his work, a type of shrewd caricature. It worked in Denver to put the state up on the offer and built the Clifford Still Museum open in 2011. Their collection represents about 95 percent of his entire output, and about 3,000 works created between 1929 and 1928. It was a purpose-built building designed by Allied workers. So this is the interior of the space where the digital project would live. The biggest challenge, figure out how did college students notice it against the dentist, and want to walk over to a key designer, and almost created a lot of digital and video prototypes before looking to incorporate the museum goers into the key office. The challenge is to create an experience that provides discovery while having an underlying logic to design. We should achieve this by making the interface minimal, giving it simple and unobtrusive, which allows the content to be the main guiding course in itself. So this is what we're going to cover today. I'm going to talk if you do the design process, then Zach will do the management, the CFPGI, front end, then I'll take over. So to start the project, we looked at archetypes of video presentation, Netflix models, so it's a main landing page that we recommend to video. This would be category cluster video represented in categories, and then this would be more of a sort of random discovery. This one, the main landing page, would navigate through the different videos, and that's how you could move different video topics by going up and down to the very spatial representation. There would be maybe an index. This is a tech-based index, and this ended up making it all the way through to the final build of relatively unchanging. We also looked at a thumbnail, but it didn't make it through. This is design iteration number two. This was called Immersive, and it's centered on a full-screen video, so it's playing constantly. You could pull up the navigation and it would make some out video at the bottom, and then navigate, navigate through different clips. This would pull up the navigation system, and then this was the third, was the one that we actually wide-showed, so you could either tap on the main video or tap tap the main. This is the design that evolved to the final. He asked the verticals.info or talk about why we chose WordPress for this. One of the central reasons was that WordPress is already, was already in the past, so staff and music were already familiar with WordPress, comfortable with WordPress. Also, adding videos, they're constantly shooting new videos, so they can manage the content of the kiosk without selling. On to that, WordPress was a good, it was a lot that we didn't do the file for you, so then you can download that caption file, edit it, and I'll just touch on the hardware that we ended up using. Drivers, there's a guy who makes driver for it. He seems to be the guy who makes driver for it. Touchbased.com, device driver. We did, we did look into other solutions, Windows-based. I think there was a lot of data that you were... A website in a browser? Is it an election app or what's actually running on it? Once you load the data, is that initial page load coming? Sort of, to ask more about the rest API, are there any changes or any frustrations that you had while working with the rest API or with the rest of WordPress that you would just, was it mainly for respect to the artist or like the intuitive user experience or thought process thing? How did you guys find WP Engine and end up working on this project? Like how did you think WordPress, right? Like how did you get there? Because there's so many different products that are offered, like to museums and experiential, so like how did you end up there? It's pretty clear it wasn't the WP Engine. You guys had a project, you guys worked at WP Engine, right? Okay, so I mean how did you end up with WordPress? That's what I'm saying, like how did you make that decision? Because there's so many off-the-shelf solutions that are trying to offer this kind of thing. So like what made, yeah, well how did you come to WordPress? I mean if you're a WordPress developer, right, but like how did you decide to seek out a WordPress developer? It's gonna be like a web-based, might as well be a web app.