diff --git a/app/components/landing-row.js b/app/components/landing-row.js deleted file mode 100644 index 87e7711b..00000000 --- a/app/components/landing-row.js +++ /dev/null @@ -1,10 +0,0 @@ -import Ember from 'ember'; -import { githubCommit as githubCommitUrl } from 'travis/utils/urls'; -import TravisRoute from 'travis/routes/basic'; -import config from 'travis/config/environment'; - -export default Ember.Component.extend({ - tagName: 'li', - classNameBindings: ['repo.lastBuildState'], - classNames: ['landing-row', 'row-li'] -}); diff --git a/app/styles/app/pages/landing.sass b/app/styles/app/pages/landing.sass index 8f72749f..d8bd33db 100644 --- a/app/styles/app/pages/landing.sass +++ b/app/styles/app/pages/landing.sass @@ -138,44 +138,6 @@ text-align: left padding: 0 0 0 12% - .recent-builds - background-color: #f6f6f6 - min-height: 44rem - - .recent-builds-text - text-align: center - h2 - color: #db4141 - text-align: right - margin: 0 - - a - color: #828282 - - p - text-align: right - margin-top: 0.5em - margin-bottom: 2em - - img - margin-bottom: 20px - - ul - padding-left: 0 - - li - background-color: #fff - border-radius: 4px - color: #828282 - font-weight: 400 - margin-bottom: 20px - list-style-type: none - position: relative - height: 120px - width: 100% - padding: 10px 0 0 60px - text-align: left - .free-for-oss text-align: center @@ -459,20 +421,6 @@ .navigation-nested background-color: white -.landing-rows - list-style: none - margin: 0 - @media #{$small-only} - padding: 0 - -.landing-row - .two-line - padding-left: 2rem - h2 - padding-left: .5rem - font-size: 18px - - .landing, .landing-pro background-color: white diff --git a/app/templates/components/landing-row.hbs b/app/templates/components/landing-row.hbs deleted file mode 100644 index ba598235..00000000 --- a/app/templates/components/landing-row.hbs +++ /dev/null @@ -1,108 +0,0 @@ - -
Easily sync your GitHub projects with Travis CI
and you’ll be testing your code in minutes!
Easily sync your GitHub projects with Travis CI
and you’ll be testing your code in minutes!
Over 200k open source projects
and 126k users are testing on Travis CI.
Some pretty awesome companies
and projects are using us.
Seriously. Always. We like to think of it as our way of giving
back to a community that gives us so much as well.
Travis CI for private repositories has
plans for every size project.
Login with GitHub, tell Travis CI to test a project, and then push to GitHub. Could it be any simpler!
+Make sure your code runs against all versions of your favorite language without breaking a sweat.
+Make sure every pull request to your project is tested before merging.
+Updating staging or production as soon as your tests pass has never been easier!
+You push your
code to GitHub
GitHub triggers
Travis CI to build
Hooray!
Your build passes!
Travis CI deploys
to Heroku
Travis CI tells the
team all is well
A pull request
is created
GitHub tells Travis CI the build is mergeable
+Hooray!
Your build passes!
Travis CI updates the PR that it passed
+You merge in
the PR goodness
Travis CI makes it so much easier for us to coordinate the thousands of commits and contributors that flow through the Rails code base. The test suite for such a large project is vast, and we wouldn’t be catching issues as quickly or smoothly without the help of Travis.
+Creator of Ruby on Rails
Over 200k open source projects
and 126k users are testing on Travis CI.
We love Travis CI at @TwitterOSS and use it for the majority of our open source projects on GitHub. Travis CI is simple to use, we love their API to build tooling and adore the new container infrastructure for speedier builds.
+Head of Open Source at Twitter
Some pretty awesome companies
and projects are using us.
Here are just a few projects
currently running on Travis CI
Seriously. Always. We like to think of it as our way of giving
back to a community that gives us so much as well.
Travis CI for private repositories has
plans for every size project.
Login with GitHub, tell Travis CI to test a project, and then push to GitHub. Could it be any simpler!
-Make sure your code runs against all versions of your favorite language without breaking a sweat.
-Make sure every pull request to your project is tested before merging.
-Updating staging or production as soon as your tests pass has never been easier!
-You push your
code to GitHub
GitHub triggers
Travis CI to build
Hooray!
Your build passes!
Travis CI deploys
to Heroku
Travis CI tells the
team all is well
A pull request
is created
GitHub tells Travis CI the build is mergeable
-Hooray!
Your build passes!
Travis CI updates the PR that it passed
-You merge in
the PR goodness
Travis CI makes it so much easier for us to coordinate the thousands of commits and contributors that flow through the Rails code base. The test suite for such a large project is vast, and we wouldn’t be catching issues as quickly or smoothly without the help of Travis.
-Creator of Ruby on Rails
-We love Travis CI at @TwitterOSS and use it for the majority of our open source projects on GitHub. Travis CI is simple to use, we love their API to build tooling and adore the new container infrastructure for speedier builds.
-Head of Open Source at Twitter
-Not only is Travis CI the best way to test your software, it is the right way. rm -rf jenkins && touch .travis.yml
-PyPy and Python Core Team Member
-Not only is Travis CI the best way to test your software, it is the right way. rm -rf jenkins && touch .travis.yml
+PyPy and Python Core Team Member