A new home for the City of Austin's Innovation Office. Forked from 18f.gsa.gov
Clone or download
Pull request Compare This branch is 25 commits ahead, 2294 commits behind 18F:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
_cards
_data
_includes
_layouts
_plugins
assets
deploy
pages
script
.about.yml
.cfignore
.gitignore
.gitmodules
.ruby-gemset
.ruby-version
.travis.yml
CONTRIBUTING.md
Gemfile
Gemfile.lock
LICENSE.md
README.md
Staticfile
_config-deploy.yml
_config.yml
favicon.ico
go
manifest.yml
robots.txt

README.md

18F's Homepage

This repository contains 18F's website, https://18f.gsa.gov.

Writing a blog post for 18F? You must read our blog publishing guide.

Deployment and workflow

  • The staging branch is automatically deployed to our staging site.
  • The production branch is automatically deployed to our production site.

All development and pull requests should be done against the staging branch.

Deployments to production will be done by site admins, using pull requests from staging to production.

We occasionally use various subdomains of 18f.gov to demo work in a way that others can see it. These deployments are manual and require a little bit of extra configuration. See the readme file in the "deploy" folder for more information on how this works.

Getting your picture and bio on the site:

If you're a new teammate, follow these steps and the #18f-site team will take care of it:

  1. Upload your photo to the appropriate Google Drive folder.
  2. Fill out the bio form.
  3. Get in touch with the site team in #18f-site; we'll handle it from there!

NOTE: Bios and pictures are scheduled to be added at the end of each month.

You do not need to edit the team.json or authors.yml files in this repo, we'll find it in team-api.18f.gov.

If you get stuck, or have any other questions, feel free to reach out to anyone on the 18f-site team in channel #18f-site.

Helpful tips:

Publishing a blog post

For a guide to how 18F manages blogging, and technical guidelines for getting your blog post into the site, see the 18F Blogging Guide.

Developing the site

This is a Jekyll website. Install Jekyll through Rubygems (you may need sudo), Bourbon, and Jekyll Sitemap:

./go init

Prerequisites: A few of our gems require a C++ compiler (XCode on the Mac). For the time being you will also need Node to be installed, because Jekyll 2 couples a CoffeeScript runtime. This will eventually be removed.

So yes: this project requires Ruby and Node (for now). Aren't static site generators the simplest?

Launch with Jekyll:

./go serve

The site will be visible at http://localhost:4000.

Before submitting a pull request, please ensure ./go ci_build runs and exits cleanly.

Deploying the site

You don't need to worry about deployment stuff for normal development -- any pushes to staging and production branches will auto-deploy.

But to dig into our deployment setup and code, visit deploy/ for more details.

Public domain

This project is in the worldwide public domain. As stated in CONTRIBUTING:

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.