This repo houses the 18F website. We use the Draft U.S. Web Design standards as a front end framework. The site is built and served through the Federalist platform.

A detailed history of the work that went into developing this redesign can be found at 18F/beta.18f.gov. An archived copy of the original website can be found on a Federalist preview.

Run each of the following steps to get the site up and running.

1. git clone [email protected]:18F/18f.gsa.gov
2. cd 18f.gsa.gov
3. bundle install
4. ./serve

To enable the ability to search and see all pages related to the blog, you can run bundle exec jekyll serve instead of ./serve for the server start command. This will slow down rebuild times dramatically, so use this command with discretion.

To enable the ability to see the most recent posts, you can run ./serve-blog. This takes longer than ./serve, but significantly less time than building the entire site.

You should be able to see the site at: http://127.0.0.1:4000

Using Docker can make dependencies management easier, but can also slow down your build time. You can find out more in this discussion

To try this out on MacOS:

1. Install Docker Toolbox.
2. Make sure Docker is running and cd into your project folder
3. Run docker-compose build to build the docker image and its dependencies. You only need to build once, but if there was an error with the build , rebuild using the --no-cache option like so docker-compose build --no-cache to avoid using the old version of the docker image.
4. Run docker-compose up. Note: if you want to run a single command and bypass your Dockerfile for debugging purposes, you can do like so docker-compose run app <COMMAND> (for instance, you can run bundle docker-compose run app bundle install)
5. Visit http://192.168.99.100:4000 in your browser.

The site is a static website with HTML, CSS, and Javascript. Deployments are done through the Federalist platform.

1. Federalist runs in its own organization and space in CloudFoundry
2. Federalist Admin: https://federalist.18f.gov/
3. Using the Federalist editor that requires GitHub Oauth and writes commits as auth'd GitHub user, changes are then passed through a webhook back to Federalist
4. Federalist uses a CloudFoundry S3 service to write to the bucket, the Federalist instance only derives S3 credentials from the CloudFoundry S3 service and can only read/write to federalist.18f.gov/*
5. Federalist responds to a webhook on GitHub and runs Jekyll to generate static web files and puts them in an S3 bucket
6. We map 18f.gsa.gov URL to the S3 bucket

• We use Cloudfront to map 18f.gsa.gov to an S3 endpoint
• Federalist, and Cloudfront do not support the following HTTPS implementations:
  • HSTS Headers
  • HTTP/2
  • OSCP Stapling