Browse files

Some website layout tweaks.

  • Loading branch information...
Luke Redpath
Luke Redpath committed Feb 3, 2011
1 parent 3c143fc commit 37a1bad2b7c4b4ce3b8506a75059ed1919e37f57
Showing with 22 additions and 1 deletion.
  1. +6 −0 Rakefile
  2. +3 −1 website/_config.yml
  3. +9 −0 website/css/layout.css
  4. +4 −0 website/index.markdown
@@ -97,6 +97,12 @@ namespace :website do
task :upload_website => [:generate] do
system("rsync -avz --delete website/_site/{SITE_ROOT}")
+ task :dev do
+ Dir.chdir("website") do
+ system("jekyll --auto")
+ end
+ end
# BetaBuilder tasks for testing
@@ -2,6 +2,8 @@ auto: false
lsi: false
server_port: 4000
pygments: true
-markdown: rdiscount
+markdown: kramdown
+ parse_block_html: true
permalink: /:title.html
@@ -45,6 +45,15 @@ footer p {
color: #666;
+.callout {
+ background: #eee;
+ padding: 10px;
+.callout h3 {
+ margin-top: 0;
#navigation {
list-style: none;
margin: 30px 0; padding: 0;
@@ -35,6 +35,7 @@ Now, back to the terminal. Run `rake -T` to view a list of the available tasks.
The task descriptions should be fairly self-explanatory, but you can consider them analogous to the following Xcode operations:
+<div class="callout" markdown="1">
### `beta:build`
This will build your app just as if you had hit **Build** in Xcode, using the `xcodebuild` utility.
@@ -45,6 +46,7 @@ You can also configure BetaBuilder to automatically archive each build to avoid
### `beta:package`
This builds your app and packages it in an IPA file. It is the same as exporting a build from Xcode Organiser and choosing **Save to Disk**.
# Distributing your app
@@ -75,6 +77,7 @@ If you now run `rake -T`, you'll see some new tasks:
rake beta:prepare # Prepare your app for deployment
rake beta:redeploy # Deploy the last build
+<div class="callout" markdown="1">
### `rake beta:deploy`
This one is self-explanatory. It will build and package your app and deploy it using your configured deployment strategy.
@@ -84,6 +87,7 @@ This one is self-explanatory. It will build and package your app and deploy it u
If your chosen deployment strategy has an intermediate step, this task will perform that step without actually deploying. The Testflight strategy (see below) has no preparation step.
For the web strategy, this will create the "payload" ready to upload to your server (the IPA, manifest and index page) but it won't actually do the upload. This is useful if you do not have SSH access to your server and need to upload the package manually (for instance, via FTP or Dropbox).
## Deploying to TestFlight

0 comments on commit 37a1bad

Please sign in to comment.