Adamdenyer (Talk | contribs) (Created page with "{{:Team:UCL/Template:htmlheader}} <html> <body class="index"> </html> {{:Team:UCL/Template:pageheader}} <html> <!-- begin #page - the container for everything but header --> ...") |
Adamdenyer (Talk | contribs) |
||
| Line 13: | Line 13: | ||
<!-- CONTENT GOES HERE --> | <!-- CONTENT GOES HERE --> | ||
| + | <div class="hero-unit"> | ||
| + | <div class="container"> | ||
| + | <h2>Read our blog</h2> | ||
| + | </div> | ||
| + | <!--close container--> | ||
| + | </div> | ||
| + | <!--close hero-unit--> | ||
| + | |||
| + | <div class="container clearfix" id="main-content"> | ||
| + | <!--begin main content--> | ||
| + | <div class="row-fluid sidebar-right"> | ||
| + | <!--begin row-fluid--> | ||
| + | <div class="span9 blog-summary primary-column"> | ||
| + | |||
| + | <!-- begin entry-post 1--> | ||
| + | <article class="entry-post"> | ||
| + | <header class="entry-header"> | ||
| + | <h3 class="entry-title"><a href="../blogposts/articlepost.shtml">Article Blog Post Example</a></h3> | ||
| + | <div class="byline"><i class="icon-pencil"></i> Adam Denyer <i class="icon-time"></i> <abbr class="published" title="Monday, October 15, 2013, 8:21 PM">October 15, 2013</abbr></div> | ||
| + | </header> | ||
| + | <!--end entry-header --> | ||
| + | |||
| + | <!--begin loop of entry-posts for summary page--> | ||
| + | |||
| + | <div class="entry-content"> | ||
| + | <figure> <a href="blog-single.html" class="hover"><img src="../images/4830134044.jpg" alt=""><span class="plus"></span></a></figure> | ||
| + | <p>Crisp is the industry leader of frictionless e-services. Is it more important for something to be cutting-edge or to be customer-defined? Quick: do you have a reconfigurable strategy for coping with new versioning metrics? We usually optimize transparent, affiliate-based, 24/7/365 60/24/7/365 structuring...</p> | ||
| + | <p class="more right"><a class="btn btn-primary" href="../blogposts/articlepost.shtml">Read More →</a> | ||
| + | </div> | ||
| + | <!-- close entry-content --> | ||
| + | |||
| + | <footer class="entry-footer"> <span class="blog date"> <span class="month">Dec</span> <span class="day">27</span> <span class="year">2013</span> </span> | ||
| + | <!--close date--> | ||
| + | </footer> | ||
| + | <!--end entry-footer--> | ||
| + | </article> | ||
| + | <!-- end entry-post 1 --> | ||
| + | |||
| + | <!-- begin entry-post 2--> | ||
| + | <article class="entry-post"> | ||
| + | <header class="entry-header"> | ||
| + | <h3 class="entry-title"><a href="../blogposts/videopost.shtml">Video Blog Example</a></h3> | ||
| + | <div class="byline"><i class="icon-pencil"></i> Adam Denyer <i class="icon-time"></i> <abbr class="published" title="Monday, October 15, 2013, 8:21 PM">October 15, 2013</abbr></div> | ||
| + | </header> | ||
| + | <!--end entry-header --> | ||
| + | |||
| + | <!--begin loop of entry-posts for summary page--> | ||
| + | |||
| + | <div class="entry-content"> | ||
| + | <div class="video-wrapper"> | ||
| + | <iframe width="600" height="400" src="http://www.youtube.com/embed/zIeWZjmeGxg"></iframe> | ||
| + | </div> | ||
| + | <p>Think clicks-and-mortar. But don’t think all three at the same time. It seems unclear, but it’s entirely completely realistic! The infomediaries factor can be summed up in one word: killer. What do we integrate? Anything and everything...</p> | ||
| + | <p class="more right"><a class="btn btn-primary" href="../blogposts/videopost.shtml">Read More →</a> | ||
| + | </div> | ||
| + | <!-- close entry-content --> | ||
| + | |||
| + | <footer class="entry-footer"> <span class="blog date"> <span class="month">Oct</span> <span class="day">15</span> <span class="year">2013</span> </span> | ||
| + | <!--close date--> | ||
| + | </footer> | ||
| + | <!--end entry-footer--> | ||
| + | </article> | ||
| + | <!-- end entry-post 2 --> | ||
| + | |||
| + | <!--end loop of entry-posts for summary page--> | ||
| + | |||
| + | </div> | ||
| + | <!-- close .span9 . primary-column .blog-summary--> | ||
| + | |||
| + | </html> | ||
| + | {{:Team:UCL/Template:blog-rhnav}} | ||
| + | <html> | ||
| + | </div> | ||
| + | <!--close row-fluid--> | ||
| + | </div> | ||
| + | <!--close .container id="main-content" --> | ||
</html> | </html> | ||
{{:Team:UCL/Template:pagefooter}} | {{:Team:UCL/Template:pagefooter}} | ||
Crisp is the industry leader of frictionless e-services. Is it more important for something to be cutting-edge or to be customer-defined? Quick: do you have a reconfigurable strategy for coping with new versioning metrics? We usually optimize transparent, affiliate-based, 24/7/365 60/24/7/365 structuring...
Think clicks-and-mortar. But don’t think all three at the same time. It seems unclear, but it’s entirely completely realistic! The infomediaries factor can be summed up in one word: killer. What do we integrate? Anything and everything...
"
