This post will walk through the basics of getting spun up on BowTie, and demonstrate our recommended workflow. BowTie is designed for developers and agencies building sites and static apps for clients. We provide a git based workflow for developers and designers, and a simple and customizable cloud editor for non-technical content creators.
To work with BowTie you will need to do a bit of basic setup. You’ll need an SSH key, a file editor, the BowTie client (for working locally), and a basic understanding of git. We also allow you to design and build custom interfaces for your clients/collaborators using Jekyll collections.
For Content Creators
BowTie provides a hosted editor for creating, editing, and removing content on your site (see below). Your workflow will be provided by the developer who set up your site. If you are working with templates provided by BowTie, you can learn how to work with content in our guide on blogging, our collections guide, and our theme guide. If you would like to access your full project repository or plan to work with content locally, read on.
Publishing content on BowTie
Configuring SSH keys
Similar to GitHub and BitBucket, BowTie authenticates repository access using SSH. You’ll need to set up an SSH keypair in order to access your repository. If you already have an SSH key, copy and paste your public key into the BowTie dashboard.
Locating Your SSH Key:
For OSX systems, run
$ pbcopy < ~/.ssh/id_rsa.pub to copy the contents of your public key into the clipboard. If you’re running another system, just open the
~/.ssh/id_rsa.pub file and copy the contents manually.
Note: When debugging repository access, comparing the key fingerprints is a good place to start. To determine the fingerprint of the key on your system, you can run the following from your terminal:
ssh-keygen -l -f ~/.ssh/id_rsa.pub
Generating an SSH Key
If you’re new to SSH, or if you don’t already have an SSH key follow this process:
Open your Terminal and type:
ssh-keygen to return:
Press Enter to save the new key to the default location.
Step 2: Create a passphrase:
Step 3: After you enter a passphrase, the system returns the fingerprint, or id, of your SSH key:
Note: We configured a default key at
~/.ssh/id_rsa[.pub]. BowTie will work with an alternative key, and custom key locations. Keys must be at least 512 bits.
Adding your key to BowTie:
After locating or creating a key as detailed above, visit your BowTie Account Keys page and paste the contents of your clipboard into the “Key” field. Give the key a title that you’ll remember this machine by and hit “Save.” You’ll see a list of Keys that you’ve added to the system by their title and a fingerprint. BowTie allows access with a single key per user account.
Installing the BowTie Client
For local development, use the BowTie Client. Our client provides the same functionality as the Jekyll development server with additional features accessible by your BowTie project (backend proxy support, policy management, test payment environment etc).
To use the the BowTie Client, you’ll need to install the
bowtie-io gem on your system.
From your terminal run:
gem install bowtie-io
This should return:
Once the client is installed, you can now launch your BowTie project locally by visiting the root directory of your cloned project and running
You can run
$ bowtie --help for a full list of supported options.
Making Updates to Your Project Files
From there, start with one of our example templates, or build a static app using any of our Jekyll templates and components. We offer a number of user guides to help you get started.
If you’re unfamiliar with Git, please thoroughly read the documentation before starting development.
After creating a Project you will be returned to your dashboard. Look for your ‘SSH clone URL’ in the top middle of the page. Copy this URL, open terminal, and clone your repository to your local system using this command:
git clone email@example.com/example (Replacing
firstname.lastname@example.org/example with the Clone URL from your Project Dashboard.)
This should yield something similar to:
You’ll now have a local directory at the location specified in your clone URL. In this example it is at
The files in this directory will match the files in the master branch of your BowTie project repository. You can now access and edit those files from your local environment, and push them back to the server when you are ready to publish the site changes.
In your cloned Project’s directory, run the BowTie client with this command:
The yield will look like this:
This launches the development server at “http://localhost:4000”, which you should now be able to visit with a browser.
The BowTie client wraps the general Jekyll system, and captures requests to
/bowtie/* which BowTie’s platform will handle for you.
File changes trigger a rebuild without needing to restart the server. You will also see errors rendered in the output of the terminal.
Changes made on your local system need to be committed, then pushed up to your repo for deployment.
The process is pretty straightforward. (If you need a primer on using git commands, read this.)
Check your status to verify your branch
Add your new content to a commit, including a commit message for future reference
git add _posts/2015*
git commit -a -m "Adds Post on Lack of Sleep"
The yield should look like this:
Now, you just need to push those changes to BowTie
git push origin
Visiting your site (in this case “https://example.bowtied.io/”), shows the changes have been applied.
Project owners can invite any other BowTie user to access their project from the Dashboard. The shared project appears in each contributor’s project dropdown.
In your dashboard, visit the Team page found in ‘Settings’ > ‘Team’ and enter your desired collaborator’s email address (must be an active BowTie account) in the ‘Add Team Member’ field. If the account is found, an ‘Add to Team’ button will appear, allowing you to grant access to your project.
Both the primary Project Owner and Contributor can remove Contributor access at any time by selecting the ‘Remove’ option next to the Contributor’s name on this page.
Team members who install SSH keys will be able to access the repository from the command line. Failure to do so will result in access/permission errors.
You can access the source files of our Jekyll templates on github.
If you are new to BowTie, check out our other Getting Started guides.
Getting Started with BowTie:
- Build a Landing Page in 5 minutes
- Using the BowTie Collection Editor
- Initial Configuration
- Setting Up Custom Domains
- Customizing and Styling BowTie frontend content
- Build a website with a pay wall
- Blogging with BowTie
- Launch a simple donation site
- Using BowTie’s User Profile system
- Build a Daily Deal Site with Jekyll Collections
- Using Jekyll Data to extend your site
- Adding BowTie users to MailChimp with Zapier
To keep up to date, follow us on twitter at @bowtie_io
Questions? Please comment! Thanks for your support and feedback.