The home of policies and guidelines that make up TTS.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
_includes remove include prefix Jan 16, 2019
_layouts
_pages Use site.baseurl Feb 19, 2019
_plugins adding in jekyll_get plugin and dependencies Aug 22, 2018
images
javascripts Updates ToC to display when headers exceed 2 Jul 9, 2018
pdfs update diversity points Apr 4, 2017
stylesheets remove stray stripe Jan 18, 2019
.gitignore
.ruby-version Commit .ruby-version 2.6.0 Jan 24, 2019
CONTRIBUTING.md
Gemfile Add Ruby 2.6.0 to Gemfile Jan 24, 2019
Gemfile.lock
LICENSE.md re-create handbook repository Sep 30, 2016
README.md
_config.yml Move-Software-Page (#1101) Feb 12, 2019
favicon-16x16.png re-create handbook repository Sep 30, 2016
favicon-32x32.png re-create handbook repository Sep 30, 2016
favicon.ico re-create handbook repository Sep 30, 2016
go Remove more commands from go script; move instructions to README (#1075) Jan 30, 2019
nav-tips.md

README.md

TTS Handbook CircleCI

The TTS Handbook documents the mission, values, structures, policies, tools, and guides that shape our team. This is a living document and is updated regularly. If you have questions, comments, or suggestions, please open an issue. If you want to add content to the Handbook, please submit a pull request or ask in #tts-handbook.

Note: If you're changing any kind of process, please let #wg-onboarding know so we can keep the handbook, new hire messages, and checklists up to date.

What can't be included

For TTS staff, keep in mind that the handbook website and repository are public, so we can't include information that shouldn't be public. We already get training on this, but here are a few reminders about things we shouldn't include here:

We avoid including information that can easily go out of date and is already published somewhere else in a useful format. This includes:

  • People's phone numbers, even if public information (such as their GSA work number). Link to the public GSA staff directory or the access-controlled 18F contact spreadsheet instead of including phone numbers in the handbook.
  • Information that is already well-covered on GSA InSite. Link there instead of reproducing it.
  • Specific TTS org chart info (such as lists of names of supervisors and facilitators). Link to the TTS org chart, the internal 18F org chart, or the internal OPP org chart instead.

We're careful about publishing information collected during research; learn more and ask #research for guidance first.

Development

Install dependencies:

bundle install

Serve the site:

bundle exec jekyll serve

Fork or branch?

Forking and branching are two ways of submitting pull requests to edit the Handbook.

If you are using the GitHub website built-in editing features, you do not have to choose: GitHub will make the correct choice for you.

If you are using your Terminal / local git to edit:

  • TTS teammates: Please use branching to submit pull requests. Federalist Preview sites will only be built from a branch, and continuous integration can only succeed for PRs created from branches.

  • External contributors: Please use forking to submit pull requests, since non-TTS contributors do not have write access. Unfortunately, we won't be able to run Federalist Preview sites for your pull request; please build and serve the site locally to test instead.

If you have any questions, feel free to ask in #tts-handbook.

Thank you so much for your contributions! 🎉

Travel guide development

To add additional images:

  1. Add an image to the images/travel directory.
  2. Link the image on the travel page, with folding HTML: <img src="/images/travel/filename.png" class="travel-guide-hide">.
  3. A show/hide link will automatically be created.

To create a new page:

  1. Create a markdown file in the _pages/policies/travel directory.
  2. Include a title and links to the "Travel Guide TOC" (see existing pages for reference).
  3. Update the page content.
  • Update the Travel Guide TOC _pages/policies/travel/travel-guide-table-of-contents.md with a link to your new page.