quay/static/partials/about.html

<div class="cor-container about-us">
  <h2>
    About Us
  </h2>

  <div class="row">
    <div class="col-sm-12 about-basic-info">
      <h3>The Basics</h3>
    </div>
    <div class="col-sm-3">
      <div class="about-basic-icon"><i class="fa fa-3x fa-calendar"></i></div>
      <div class="about-basic-text">
        <b> Founded</b><br>
        2012
      </div>
    </div>
    <div class="col-sm-3">
      <div class="about-basic-icon"><i class="fa fa-3x fa-globe"></i></div>
      <div class="about-basic-text">
        <b> Location</b><br>
        New York City, NY
      </div>
    </div>
    <div class="col-sm-3">
      <div class="about-basic-icon"><i class="fa fa-3x fa-users"></i></div>
      <div class="about-basic-text">
        <b> Local Worker Bees</b><br>
        2
      </div>
    </div>
    <div class="col-sm-3">
      <div class="about-basic-icon"><img src="/static/img/coreos-globe-color-lg.png" style="height: 42px; vertical-align: bottom;"></div>
      <div class="about-basic-text">
        <b> CoreOS</b><br>
        August, 2014
      </div>
    </div>
  </div>

  <div class="row">
    <div class="col-sm-12">
      <h3>Our Story</h3>
      <p>Quay.io was originally created out of necessity when we wanted to use Docker containers with our original IDE product. We were using Docker containers to host and isolate server processes invoked on behalf of our users and often running their code. We started by building the Docker image dynamically whenever we spun up a new host node. The image was monolithic. It was too large, took too long to build, and was hard to manage conflicts. It was everything that Docker wasn't supposed to be. When we decided to split it up into pre-built images and host them somewhere, we noticed that there wasn't a good place to host images securely. Determined to scratch our own itch, we built Quay.io, and officially launched it as an aside in our presentation to the <a href="http://www.meetup.com/Docker-NewYorkCity/events/142142762/">Docker New York City Meetup</a> on October 2nd, 2013.</p>
      <p>After launch, our customers demanded that Quay.io become our main focus. They rely on us to make sure they can store and distribute their Docker images, and we understand that solemn responsibility. Our customers have been fantastic with giving us great feedback and suggestions.</p>
      <p>In August, 2014, Quay.io joined <a href="https://coreos.com">CoreOS</a> to provide registry support for the enterprise. As ever, we are working as hard as we can to deliver on the promise and execute our vision of what a top notch Docker registry should be.
    </div>
  </div>

  <div class="row">
    <div class="col-sm-12">
      <h3>The Quay.io Team at CoreOS</h3>
      The Quay.io team is composed of two software engineers:
    </div>
  </div>
  <div class="row">
    <div class="col-sm-7 col-sm-offset-3 col-md-10 col-md-offset-2">
      <h4>Jacob Moshenko<br>
      <small>Co-Founder</small></h3>
    </div>

    <div class="col-sm-7 col-md-10">
      <p>Jacob graduated from The University of Michigan with a Bachelors in Computer Engineering. From there he allowed his love of flight and mountains to lure him to Seattle where he took a job with Boeing Commercial Airplanes working on the world's most accurate flight simulator. When he realized how much he also loved web development, he moved to Amazon to work on the e-commerce back-end. Finally, desiring to move to New York City, he moved to Google, where he worked on several products related to Google APIs.</p>
    </div>
  </div>
  <div class="row">
    <div class="col-sm-7 col-sm-offset-3 col-md-10 col-md-offset-2">
      <h4>Joseph Schorr<br>
      <small>Co-Founder</small></h3>
    </div>

    <div class="col-sm-7 col-md-10">
      <p>Joseph graduated from University of Pennsylvania with a Bachelors and Masters in Computer Science. After a record setting (probably) five internships with Google, he took a full time position there to continue his work on exciting products such as Google Spreadsheets, the Google Closure Compiler, and Google APIs. </p>
    </div>
  </div>
</div>