e6800c80c6
Layout handling in travis-web was implemented in a dynamic way, so we could change a main layout from any of the routes. This needed a `rerender` call which was making things harder and needed some hacks. It also broke a few transitions when upgrading to 1.8.1. After examining our usage of layouts I've noticed that we don't need to change the entire layout dynamically and instead we can set layout on root routes (like "index", "profile" and other root routes).
78 lines
3.5 KiB
Handlebars
78 lines
3.5 KiB
Handlebars
<div id="getting-started">
|
|
<h3>Welcome to Travis CI!</h3>
|
|
|
|
<h2>Hey, it looks like you're new around here and have yet to set up your first<br>repository on Travis CI. We're here to help you get started, it's easy!</h2>
|
|
|
|
<div class="getting-started-row">
|
|
<div class="column">
|
|
<img src="/images/getting-started/project-switch.png">
|
|
</div>
|
|
|
|
<div class="column-right">
|
|
<span class="steps">Step 1: Enabling your projects</span>
|
|
<p>
|
|
Start by going to your {{#link-to "profile"}}profile{{/link-to}} and enable one of your projects. We've been
|
|
synchronizing all repositories you have administrative access to. Pick one and flip the switch next to it.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="getting-started-row">
|
|
<div class="column">
|
|
<img src="/images/getting-started/first-build.png">
|
|
</div>
|
|
|
|
<div class="column-right">
|
|
<span class="steps">Step 2: Adding Travis</span>
|
|
<p>
|
|
Once you've enabled one of your projects, add a <a
|
|
href="http://about.travis-ci.org/docs/user/build-configuration/#.travis.yml-file%3A-what-it-is-and-how-it-is-used"><code>.travis.yml</code></a> to your project, push some code, and we'll start processing your builds. Wait a
|
|
whee while and reload the page, and your newly setup and built project will show up on the right.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="getting-started-row">
|
|
<div class="column">
|
|
<img src="/images/getting-started/build-email.png">
|
|
</div>
|
|
|
|
<div class="column-right">
|
|
<span class="steps">Step 3: Wait for your build to finish</span>
|
|
<p>
|
|
We'll be sending you an email once the build has finished. Then, it's up to you to do the happy dance.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="getting-started-row">
|
|
<span class="after-steps steps">Build Configuration</span>
|
|
<p>
|
|
We use sensible defaults for <a href="http://about.travis-ci.org/docs/">most languages</a>, but you can customize
|
|
both the <a href="http://about.travis-ci.org/docs/user/build-configuration/">build process</a> and the <a
|
|
href="http://about.travis-ci.org/docs/user/build-configuration/">build
|
|
environment</a> to fit your project's needs.
|
|
</p>
|
|
|
|
<span class="steps">Notifications</span>
|
|
<p>
|
|
You can also configure how you want to be notified of build results. Email is only one channel you can use. We
|
|
support <a href="http://about.travis-ci.org/docs/user/notifications/#Campfire-notification">Campfire</a>, <a
|
|
href="http://about.travis-ci.org/docs/user/notifications/#HipChat-notification">HipChat</a>, <a
|
|
href="http://about.travis-ci.org/docs/user/notifications/#Flowdock-notification">Flowdock</a>, <a
|
|
href="http://about.travis-ci.org/docs/user/notifications/#IRC-notification">IRC</a>, and <a
|
|
href="http://about.travis-ci.org/docs/user/notifications/#Webhook-notification">webhooks</a>. To avoid
|
|
exposing any private credentials, you can shield them from the public using <a
|
|
href="http://about.travis-ci.org/docs/user/build-configuration/#Secure-environment-variables">encrypted
|
|
configuration settings</a>.
|
|
</p>
|
|
|
|
<span class="steps">Questions</span>
|
|
<p>
|
|
Should you have any questions or issues, have a look at <a href="http://about.travis-ci.org/docs/" location="_top">our
|
|
documentation</a>, <a href="https://github.com/travis-ci/travis-ci/issues/new" location="_top">open an issue</a> or
|
|
<a href="mailto:support@travis-ci.com">send us an email</a>.
|
|
</p>
|
|
</div>
|
|
</div>
|