/* So you like the style of impress.js demo? Or maybe you are just curious how it was done? You couldn't find a better place to find out! Welcome to the stylesheet impress.js demo presentation. Please remember that it is not meant to be a part of impress.js and is not required by impress.js. I expect that anyone creating a presentation for impress.js would create their own set of styles. But feel free to read through it and learn how to get the most of what impress.js provides. And let me be your guide. Shall we begin? */ /* We start with a good ol' reset. That's the one by Eric Meyer http://meyerweb.com/eric/tools/css/reset/ You can probably argue if it is needed here, or not, but for sure it doesn't do any harm and gives us a fresh start. */ html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video { margin: 0; padding: 0; border: 0; font-size: 100%; font: inherit; vertical-align: baseline; } /* HTML5 display-role reset for older browsers */ article, aside, details, figcaption, figure, footer, header, hgroup, menu, nav, section { display: block; } body { line-height: 1; } ol, ul { list-style: none; } blockquote, q { quotes: none; } blockquote:before, blockquote:after, q:before, q:after { content: ''; content: none; } table { border-collapse: collapse; border-spacing: 0; } /* Now here is when interesting things start to appear. We set up styles with default font and nice gradient in the background. And yes, there is a lot of repetition there because of -prefixes but we don't want to leave anybody behind. */ body { font-family: 'Oxygen', sans-serif; min-height: 740px; } .body-default { background: rgb(251, 251, 251); } /* Now let's bring some text styles back ... */ b, strong { font-weight: bold } i, em { font-style: italic } /* ... and give links a nice look. */ a { color: inherit; text-decoration: none; padding: 0 0.1em; background: rgba(255,255,255,1); text-shadow: -1px -1px 2px rgba(100,100,100,0.9); border-radius: 0.2em; -webkit-transition: 0.5s; -moz-transition: 0.5s; -ms-transition: 0.5s; -o-transition: 0.5s; transition: 0.5s; } a:hover, a:focus { background: rgba(255,255,255,1); text-shadow: -1px -1px 2px rgba(100,100,100,0.5); } /* fix list items */ li { list-style: square; overflow-wrap: normal; overflow: visible; } li.check { list-style: none; margin-left: -1em; } pre { overflow: hidden; font-family: courier; font-size: 20px; } /* Because the main point behind the impress.js demo is to demo impress.js we display a fallback message for users with browsers that don't support all the features required by it. All of the content will be still fully accessible for them, but I want them to know that they are missing something - that's what the demo is about, isn't it? And then we hide the message, when support is detected in the browser. */ .fallback-message { font-family: sans-serif; line-height: 1.3; width: 780px; padding: 10px 10px 0; margin: 20px auto; border: 1px solid #E4C652; border-radius: 10px; background: #EEDC94; } .fallback-message p { margin-bottom: 10px; } .impress-supported .fallback-message { display: none; } /* Now let's style the presentation steps. We start with basics to make sure it displays correctly in everywhere ... */ .step { position: relative; width: 900px; padding: 40px; margin: 20px auto; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; -ms-box-sizing: border-box; -o-box-sizing: border-box; box-sizing: border-box; font-family: 'Oxygen', georgia, serif; font-size: 48px; line-height: 1.5; } #prezlink { font-family: "Oxygen"; font-size: 24px; position: absolute; bottom: 0; left: 0; } #backgroundscene { position: absolute; width:100%; height:100%; } /* ... and we enhance the styles for impress.js. Basically we remove the margin and make inactive steps a little bit transparent. */ .impress-enabled .step { margin: 0; opacity: 0.25; border: 1px solid transparent; -webkit-transition: opacity 1s; -moz-transition: opacity 1s; -ms-transition: opacity 1s; -o-transition: opacity 1s; transition: opacity 1s; } .impress-enabled .step.active { opacity: 1 } /* These 'slide' step styles were heavily inspired by HTML5 Slides: http://html5slides.googlecode.com/svn/trunk/styles.css ;) They cover everything what you see on first three steps of the demo. */ .slide { display: block; width: 900px; height: 700px; padding: 40px 60px; background-color: white; border: 1px solid rgba(0, 0, 0, .3); border-radius: 10px; box-shadow: 0 2px 6px rgba(0, 0, 0, .1); color: rgb(102, 102, 102); text-shadow: 0 2px 2px rgba(0, 0, 0, .1); font-family: 'Oxygen', Arial, sans-serif; font-size: 30px; line-height: 36px; letter-spacing: -1px; } .slide q { display: block; font-size: 50px; line-height: 72px; margin-top: 100px; } .slide q strong { white-space: nowrap; } /* And now we start to style each step separately. I agree that this may be not the most efficient, object-oriented and scalable way of styling, but most of steps have quite a custom look and typography tricks here and there, so they had to be styles separately. First is the title step with a big

(no room for padding) and some 3D positioning along Z axis. / #start { padding: 0; font-family: "Sonsie One"; overflow: visible; width: 1000px; margin: 0; opacity: 0; } #start .withsalt { font-size: 64px; color: #00A0D9; text-shadow: -1px -1px 1px rgba(100,100,100,0.9); } #start .maintitle { font-size: 80px; color: #00A0D9; text-shadow: -1px -1px 1px rgba(100,100,100,0.9); } #start .footnote { font-family: "Oxygen"; font-size: 28px; position: absolute; bottom: -4em; left: -1em; } #start .footnote a { padding-left: 54px; background: transparent url('../media/twitter-icon.png') left no-repeat; } #start.present { opacity: 1; } div#backgroundscene { opacity: 0; -webkit-transition: opacity 1.5s; -moz-transition: opacity 1.5s; -ms-transition: opacity 1.5s; -o-transition: opacity 1.5s; transition: opacity 1.5s; } div#backgroundscene.samurai-background { background: url(../media/samurai_figurines.png) no-repeat bottom right; background-size: 40%; opacity: 1; } div#backgroundscene.merlin-background { background: url(../media/sword-disneyscreencaps.com-4303.jpg) no-repeat bottom right; background-size:100% 100%; opacity: 1; } div#backgroundscene.merlin-background p { opacity: 0; } #backgroundscene p { opacity:0; position: absolute; bottom: 0px; right: 50px; color: #555555; -webkit-transition: opacity 1s; -moz-transition: opacity 1s; -ms-transition: opacity 1s; -o-transition: opacity 1s; transition: opacity 1s; } / classes suitable for smaller blocks of text, like explanations, tips, etc / .smaller { font-size: 70%; } .verysmall { font-size: 50%; } .tip { display: inline-block; font-size: 80%; position: absolute; bottom: -4em; right: 0em; -webkit-transition: 0.5s; -moz-transition: 0.5s; -ms-transition: 0.5s; -o-transition: 0.5s; transition: 0.5s; } #concept { padding:0; overflow: visible; color: #353535; } #concept.present { color: #353535; -webkit-transition: color 0.5s; -moz-transition: color 0.5s; -ms-transition: color 0.5s; -o-transition: color 0.5s; transition: color 0.5s; } #concept span.line { overflow: visible; text-align: center; font-family: "Open Sans"; font-weight: 800; font-size: 100px; text-transform: uppercase; line-height: 130px; margin:0; padding:0; } #line1 { letter-spacing: 0.15em; } #line1b { letter-spacing: 0.83em; } #line2 { letter-spacing: 0.03em; } #line3 { letter-spacing: 0.14em; } #line4 { letter-spacing: 0.06em; } #concept.present .rotating { -webkit-transform: rotate(10deg); -moz-transform: rotate(10deg); -ms-transform: rotate(10deg); -o-transform: rotate(10deg); transform: rotate(10deg); -webkit-transition-delay: 1.25s; -moz-transition-delay: 1.25s; -ms-transition-delay: 1.25s; -o-transition-delay: 1.25s; transition-delay: 1.25s; } #bigpictureoverlay { display: none; } #bigpictureoverlay.past { display: block; } #bigpictureoverlay.present { display: block; } .awesome { bottom: 0em; right: 7em; } #aboutsalt.present .appearing { -webkit-transform: scale(1.3); -moz-transform: scale(1.3); -ms-transform: scale(1.3); -o-transform: scale(1.3); transform: scale(1.3); -webkit-transition-delay: 1.25s; -moz-transition-delay: 1.25s; -ms-transition-delay: 1.25s; -o-transition-delay: 1.25s; transition-delay: 1.25s; -webkit-transition-timing-function: ease-out; -moz-transition-timing-function: ease-out; -ms-transition-timing-function: ease-out; -o-transition-timing-function: ease-out; transition-timing-function: ease-out; } div.step.option2 { width: 980px; } div.step.present pre { overflow: visible; } #eventsReactors { border-top: 1px solid #ff39b8; } #ribbon { position: absolute; right: 20px; top: -5px; } a.redis { background: url(../media/redis.png) no-repeat left; padding-left: 40px; overflow: visible; } a.saltstack { background: url(../media/salt-icon-32.png) no-repeat left; padding-left: 40px; overflow: visible; } #eventsOverview { width: 950px; } / hide / #end.future, #end.past { display: none; } #end.present { display: block; } #qa { font-size: 600%; letter-spacing: 0.1em; } #thanks { overflow: visible; position: absolute; bottom:-1em; right:0; } @keyframes oscillate { from {rotation: 10deg; } to {rotation: 350deg;} } .option1.present, .option1.past { border: 1px solid #4bd646; } .option2.present, .option2.past { border: 1px solid #ffa308; } .option3.present, .option3.past { border: 1px solid #f20090; } li.option1 { color:#4bd646; } li.option2 { color: #ffa308; } li.option3 { color:#f20090; } p.center { text-align: center; } / We also make other steps visible and give them a pointer cursor using the `impress-on-` class. / .impress-on-overview .step { opacity: 1; cursor: pointer; } / And as the last thing there is a workaround for quite strange bug. It happens a lot in Chrome. I don't remember if I've seen it in Firefox. Sometimes the element positioned in 3D (especially when it's moved back along Z axis) is not clickable, because it falls 'behind' the element. To prevent this, I decided to make non clickable by setting pointer-events property to `none` value. Value if this property is inherited, so to make everything else clickable I bring it back on the #impress element. If you want to know more about `pointer-events` here are some docs: https://developer.mozilla.org/en/CSS/pointer-events There is one very important thing to notice about this workaround - it makes everything 'unclickable' except what's in #impress element. So use it wisely ... or don't use at all. / .impress-enabled { pointer-events: none } .impress-enabled #impress { pointer-events: auto } / There is one funny thing I just realized. Thanks to this workaround above everything except #impress element is invisible for click events. That means that the hint element is also not clickable. So basically all of this transforms and delayed transitions trickery was probably not needed at all... But it was fun to learn about it, wasn't it? / / That's all I have for you in this file. Thanks for reading. I hope you enjoyed it at least as much as I enjoyed writing it for you. */