├── _pages ├── shared-data │ ├── cor.md │ ├── igce.md │ ├── ix.md │ ├── ia-part-a.md │ ├── ia-part-b.md │ ├── tts-ocfo.md │ ├── infra-lead.md │ ├── ncr-commissioner.md │ ├── tts-finance.md │ ├── 18f-director.md │ ├── ncr-ogc.md │ ├── opp-finance.md │ ├── tts-commissioner.md │ ├── tts-ogc.md │ ├── ncr-dep-commissioner.md │ ├── tts-acq-director.md │ ├── executive-summary.md │ ├── tts-acq-dep-director.md │ ├── opp-director.md │ ├── tts-assistant-commissioner.md │ ├── ncr-pm.md │ ├── ncr-cs.md │ ├── kanban-lead.md │ └── ncr-co.md ├── backup │ ├── external-clients.md │ ├── add-a-new-page.md │ ├── index.md │ ├── update-the-config-file │ │ └── understanding-baseurl.md │ ├── add-images.md │ ├── add-a-new-page │ │ └── make-a-child-page.md │ ├── github-setup.md │ ├── post-your-guide.md │ ├── update-the-config-file.md │ └── advanced-features.md ├── internal-buys │ ├── internal-buys.md │ ├── qa.md │ ├── award.md │ ├── bizdev.md │ ├── drafting.md │ ├── intake.md │ ├── proposals.md │ ├── staffing.md │ ├── agreements.md │ ├── evaluation.md │ ├── onboarding.md │ ├── release-rfp.md │ ├── acq-package-review.md │ ├── co-team-assigned.md │ ├── infrastructure-review.md │ └── solicitation-scoping.md ├── images.png ├── external-clients │ ├── external-clients.md │ ├── infrastructure-review.md │ ├── onboarding.md │ ├── award.md │ ├── release-rfp.md │ ├── proposals.md │ ├── solicitation-scoping.md │ ├── staffing.md │ ├── intake.md │ ├── co-team-assigned.md │ ├── acq-package-review.md │ ├── bizdev.md │ ├── evaluation.md │ ├── qa.md │ ├── agreements.md │ └── drafting.md └── internal-clients │ ├── release-rfp.md │ ├── internal-clients.md │ ├── proposals.md │ ├── staffing.md │ ├── onboarding.md │ ├── evaluation.md │ ├── solicitation-scoping.md │ ├── co-team-assigned.md │ ├── award.md │ ├── acq-package-review.md │ ├── qa.md │ ├── infrastructure-review.md │ ├── agreements.md │ ├── intake.md │ └── drafting.md ├── .gitignore ├── assets └── css │ └── styles.scss ├── .travis.yml ├── images ├── 18f-pages.png ├── description.png ├── gh-webhook.png ├── gh-add-guide.png ├── gh-branches-link.png ├── gh-default-branch.png └── gh-settings-button.png ├── Gemfile ├── CONTRIBUTING.md ├── LICENSE.md ├── go ├── Gemfile.lock ├── README.md └── _config.yml /_pages/shared-data/cor.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /_pages/shared-data/igce.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /_pages/shared-data/ix.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /_pages/backup/external-clients.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /_pages/shared-data/ia-part-a.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /_pages/shared-data/ia-part-b.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /_pages/internal-buys/internal-buys.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | _site/ 2 | .sass-cache/ 3 | .DS_store 4 | .*.swp 5 | .jekyll* 6 | -------------------------------------------------------------------------------- /assets/css/styles.scss: -------------------------------------------------------------------------------- 1 | --- 2 | --- 3 | 4 | @import "guides_style_18f"; 5 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | script: bundle exec jekyll build 2 | 3 | language: ruby 4 | rvm: 5 | - 2.2.0 6 | -------------------------------------------------------------------------------- /_pages/images.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/_pages/images.png -------------------------------------------------------------------------------- /images/18f-pages.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/18f-pages.png -------------------------------------------------------------------------------- /images/description.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/description.png -------------------------------------------------------------------------------- /images/gh-webhook.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/gh-webhook.png -------------------------------------------------------------------------------- /images/gh-add-guide.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/gh-add-guide.png -------------------------------------------------------------------------------- /images/gh-branches-link.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/gh-branches-link.png -------------------------------------------------------------------------------- /_pages/backup/add-a-new-page.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | This is a page about external clients. 6 | -------------------------------------------------------------------------------- /images/gh-default-branch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/gh-default-branch.png -------------------------------------------------------------------------------- /images/gh-settings-button.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/18F/acqstack-journeymap/18f-pages/images/gh-settings-button.png -------------------------------------------------------------------------------- /_pages/shared-data/tts-ocfo.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: TTS Office of Chief Information Officer 3 | --- 4 | 5 | The current representative for TTS in OCFO is: ???. 6 | Email: ??? -------------------------------------------------------------------------------- /_pages/shared-data/infra-lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | The Current TTS Commissioner is: Rob Cook. 6 | Email: rob.cook@gsa.gov 7 | Slack: @robcook 8 | -------------------------------------------------------------------------------- /_pages/shared-data/ncr-commissioner.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR Commissioner 3 | --- 4 | 5 | The current TTS Commissioner is: Houston Taylor. 6 | Email: houston.taylor@gsa.gov 7 | -------------------------------------------------------------------------------- /_pages/shared-data/tts-finance.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | The Current TTS Commissioner is: Rob Cook. 6 | Email: rob.cook@gsa.gov 7 | Slack: @robcook 8 | -------------------------------------------------------------------------------- /_pages/shared-data/18f-director.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 18F Director 3 | --- 4 | 5 | The Current 18F (Acting) Director is: Dave Zvenyach. 6 | Email: vladlen.zvenyach@gsa.gov 7 | Slack: @vdavez -------------------------------------------------------------------------------- /_pages/shared-data/ncr-ogc.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR Office of General Counsel 3 | --- 4 | 5 | The current representative from NCR OGC for TTS is: Maria [last name unknown]. 6 | Email: ??? -------------------------------------------------------------------------------- /_pages/shared-data/opp-finance.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Office of Products and Programs (OPP) Finance POC 3 | --- 4 | 5 | The Current TTS Commissioner is: ??? 6 | Email: ??? 7 | Slack: ??? 8 | -------------------------------------------------------------------------------- /_pages/shared-data/tts-commissioner.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | The Current TTS Commissioner is: Rob Cook. 6 | Email: rob.cook@gsa.gov 7 | Slack: @robcook 8 | -------------------------------------------------------------------------------- /_pages/shared-data/tts-ogc.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: TTS Office of General Counsel 3 | --- 4 | 5 | The current representative of OGC for TTS is: John Peters. 6 | Email: john.h.peters@gsa.gov 7 | -------------------------------------------------------------------------------- /_pages/shared-data/ncr-dep-commissioner.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR Deputy Commissioner 3 | --- 4 | 5 | The current NCR Deputy Commissioner is: Darrick Early. 6 | Email: darrick.early@gsa.gov 7 | -------------------------------------------------------------------------------- /_pages/shared-data/tts-acq-director.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Acqstack Director 3 | --- 4 | 5 | The current Acqstack Director is: Dave Zvenyach. 6 | Email: vladlen.zvenyach@gsa.gov 7 | Slack: @vdavez 8 | -------------------------------------------------------------------------------- /_pages/shared-data/executive-summary.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Executive Summary 3 | --- 4 | 5 | Start with [this template](https://docs.google.com/document/d/1hEEyMLCRwPQDWOmSI5YTCpRCpxZPr0ijQwC1EyxhTB0/edit). 6 | -------------------------------------------------------------------------------- /_pages/shared-data/tts-acq-dep-director.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Acqstack Deputy Director 3 | --- 4 | 5 | The Current TTS Commissioner is: Alla Goldman-Seiffert. 6 | Email: alla.seiffert@gsa.gov 7 | Slack: @alla 8 | -------------------------------------------------------------------------------- /_pages/shared-data/opp-director.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Office of Products and Programs (OPP) Director 3 | --- 4 | 5 | The current OPP (Acting) Director: Sarah Crane. 6 | Email: sarah.crane@gsa.gov 7 | Slack: @sarahcrane 8 | -------------------------------------------------------------------------------- /_pages/shared-data/tts-assistant-commissioner.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: TTS Assistant Commissioner 3 | --- 4 | 5 | The current Acting TTS Assistant Commissioner is: Dave Zvenyach. 6 | Email: vladlen.zvenyach@gsa.gov 7 | Slack: @vdavez 8 | -------------------------------------------------------------------------------- /Gemfile: -------------------------------------------------------------------------------- 1 | source 'https://rubygems.org' 2 | 3 | gem 'jekyll' 4 | gem 'redcarpet' 5 | gem 'rouge' 6 | gem 'go_script' 7 | 8 | group :jekyll_plugins do 9 | gem "guides_style_18f", :github => '18F/guides-style', :branch => 'v0.4.10' 10 | end 11 | -------------------------------------------------------------------------------- /_pages/shared-data/ncr-pm.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR Project Manager 3 | --- 4 | 5 | The NCR PM is responsible for the relationship between NCR and TTS, and is the first person we escalate issues to. 6 | 7 | The Current TTS Commissioner is: Vivieca (Viv) Pierce. 8 | Email: vivieca.pierce@gsa.gov 9 | -------------------------------------------------------------------------------- /_pages/shared-data/ncr-cs.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Contracting Specialist 3 | --- 4 | 5 | A Contracting Specialist (CS) is our main point of contact for most buys. They do a majority of the writing and review, and only pass things off to the CO for major decisions or final reviews. 6 | 7 | Current NCR CS's are: Julio Permodo, Jasmine Mitchell, Julius Bradshaw. Maybe Aleseia Saunders. 8 | Email: julio.permodo@gsa.gov, jasmine.mitchell@gsa.gov, julius.bradshaw@gsa.gov, Aleseia.Saunders@gsa.gov -------------------------------------------------------------------------------- /_pages/external-clients/external-clients.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | External clients include everyone outside of the Technology Transformation Service (TTS). This includes other federal agencies and departments, as well as other parts of GSA. 6 | 7 | Other parts of TTS (OPP, Infrastructure, 18F, etc) are NOT considered external. 8 | 9 | For buys with External Clients, buy off the Agile BPA and work with the National Capital Region (NCR) of FAS as our official contracting office. 10 | 11 | -------------------------------------------------------------------------------- /_pages/internal-buys/qa.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/award.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/bizdev.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/drafting.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/intake.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/proposals.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/staffing.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/agreements.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/evaluation.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/onboarding.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/release-rfp.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/acq-package-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/co-team-assigned.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/infrastructure-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/internal-buys/solicitation-scoping.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: External Clients 3 | --- 4 | 5 | ### External Clients 6 | What is an external client? Talk about Agile BPA things. 7 | 8 | ### How long does this process usually take? 9 | 10 | ### What happens in this stage? 11 | 12 | ### Who is involved in this stage? 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | 2. Documents created 17 | 2. Approvals needed 18 | 19 | ### What can go wrong in this stage? 20 | 21 | ### What is the next step? 22 | 23 | 24 | -------------------------------------------------------------------------------- /_pages/shared-data/kanban-lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Kanban Lead 3 | --- 4 | 5 | TTS Office of Acquisitions (Acqstack) is divided up into several "substacks." A substack is a medium sized (usually 8-10 people), cross-functional team that takes on projects. 6 | 7 | A Kanban lead is a representative from that group (not necessarily someone "in charge" of the group though) who meets with the Acqstack Deputy Director and other Kanban leads regularly to discuss upcoming substack capacity and upcoming projects. 8 | 9 | The Current Kanban Leads are: Jessie Posilkin, Kirsten Green, and Michael Torres. -------------------------------------------------------------------------------- /_pages/shared-data/ncr-co.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR Contracting Officer 3 | --- 4 | 5 | NCR (National Capital Region) provides several contracting officers (CO's) to TTS. While TTS has our own COs, some of whom are warranted, currently TTS COs serve more as consulting COs on procurements. A CO from NCR is the official CO for all procurements with external clients. 6 | 7 | TTS was recently given limited internal procurement authority, which lets a TTS CO be the official CO for a small number of procurements with internal (within TTS) clients. 8 | 9 | Current NCR CO's are: Fred Thomas, Dan Higgins, Al Munoz. Potentially Aleseia Saunders 10 | Email: frederick.thomas@gsa.gov, daniel.higgins@gsa.gov, (no email for Al Munoz yet) Aleseia.Saunders@gsa.gov 11 | -------------------------------------------------------------------------------- /_pages/backup/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | permalink: / 3 | title: Introduction 4 | --- 5 | Hello, friend! So I heard you want to buy something. That’s great. Just whip out that credit card and - what’s that? You work for the federal government? Oh, okay then. No, it’s no problem. It’s just a little more complicated than buying socks or amazon web services would be in the private sector. 6 | 7 | To help you through, Acqstack has produced a journey map to guide you on your acquisitions path. So grab your towel and stick out your thumb, my friend. It’s time for us to begin our grand journey. 8 | 9 | Oh, before we begin. One quick question: are you buying something for someone in TTS (OPP/OCSIT, 18F, etc), or are you buying something for a non-TTS client (anywhere else in GSA, IRS, Department of State, etc)? 10 | -------------------------------------------------------------------------------- /_pages/internal-clients/release-rfp.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release the Solicitation 3 | --- 4 | 5 | ### What happens in this stage? 6 | The NCR CO releases the solicitation "to the street." 7 | 8 | ### How long does this process usually take? 9 | A day or two to publish the solicitation. How long it stays open depends on the particular acquisition strategy, but in general we aim for no more than 3-4 weeks. 10 | 11 | ### Who is involved in this stage? 12 | - NCR CO 13 | 14 | ### What needs to happen to get us out of this stage? 15 | 1. Tasks done 16 | - NCR CO informs TTS team the solicitation has been released 17 | 2. Documents created 18 | - N/A 19 | 2. Approvals needed 20 | - N/A 21 | 22 | ### What can go wrong in this stage? 23 | No known things can go wrong at this stage. 24 | 25 | ### What is the next step? 26 | Vendor Q&A 27 | -------------------------------------------------------------------------------- /_pages/external-clients/infrastructure-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Infrastructure Review 3 | --- 4 | 5 | ### What happens in this stage? 6 | If you are buying software, investigate your client agency's infrastructure review policies. Exact process will be situation dependent. 7 | 8 | ### How long does this process usually take? 9 | Unknown - will depend on the client agency. 10 | 11 | ### Who is involved in this stage? 12 | 13 | - Acqstack team 14 | - Client team 15 | - Client IT review organization 16 | 17 | ### What needs to happen to get us out of this stage? 18 | 19 | 1. Tasks done 20 | - Situation dependent 21 | 2. Documents created 22 | - Situation dependent 23 | 3. Approvals needed 24 | - Situation dependent 25 | 26 | ### What can go wrong in this stage? 27 | Situation dependent. 28 | 29 | ### What is the next step? 30 | Solicitation drafting. 31 | 32 | -------------------------------------------------------------------------------- /_pages/internal-clients/internal-clients.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Internal Clients 3 | --- 4 | 5 | Internal clients include anyone within the Technology Transformation Service (TTS). This includes, but is not limited to, OPP (formerly OCSIT), TTS Infrastructure, TTS Operations, Transformation Services, Custom Partner Solutions, TTS Acquisitions, etc. 6 | 7 | Other parts of GSA (GSA IT, FAS, PBS, etc) are NOT considered internal. 8 | 9 | For buys with Internal Clients, we typically work with the National Capital Region (NCR) of FAS as our official contracting office. 10 | 11 | But as of November 2016, we have the opportunity to do do a pilot of 5 buys on our own (referred to as Internal Buys) using our Internal Procurement Authority. If you think your buy might be a good fit for an Internal Buy, please discuss with the Director and Deputy Director of TTS Acquisitions. 12 | 13 | -------------------------------------------------------------------------------- /_pages/internal-clients/proposals.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Proposals 3 | --- 4 | 5 | ### What happens in this stage? 6 | Vendors submit their proposals to the NCR CO. The CO then sends us the proposals, sans the pricing information (so the evaluation team in the next phase can make an evaluation unbiased by price). 7 | 8 | ### How long does this process usually take? 9 | 8-10 days after Q&A answers are submitted (if applicable) 10 | 11 | ### Who is involved in this stage? 12 | - Vendor POC 13 | - NCR CO 14 | 15 | ### What needs to happen to get us out of this stage? 16 | 1. Tasks done 17 | - Vendors needs to submit proposals to NCR CO 18 | 2. Documents created 19 | - Vendor proposals 20 | 3. Approvals needed 21 | - N/A 22 | 23 | ### What can go wrong in this stage? 24 | No known things can go wrong at this stage. 25 | 26 | ### What is the next step? 27 | Evaluation. 28 | -------------------------------------------------------------------------------- /_pages/external-clients/onboarding.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Onboarding 3 | --- 4 | 5 | ### What happens in this stage? 6 | A project is staffed! Now it's time to get everyone up to speed. 7 | 8 | Schedule a kickoff meeting with the client to introduce them to the team, discuss the project, and establish next steps. 9 | 10 | ### How long does this process usually take? 11 | A week or two, depending on scheduling. 12 | 13 | ### Who is involved in this stage? 14 | 15 | - The client team 16 | - The Acqstack team 17 | 18 | ### What needs to happen to get us out of this stage? 19 | 1. Tasks done 20 | - Kickoff meeting 21 | 2. Documents created 22 | - N/A 23 | 3. Approvals needed 24 | - N/A 25 | 26 | ### What can go wrong in this stage? 27 | The fresh team tends to look around and say "Wait, what!? Why is this happening? Who told them that?" As a member of the project team, it's important to challenge all assumptions about the project. There are frequently expectation differences. Clients will often feel burned by the agreements process, and by shifting POC's on the TTS side. 28 | 29 | Be aware, the client point of contact may have changed. 30 | 31 | ### What is the next step? 32 | Solicitation Scoping 33 | -------------------------------------------------------------------------------- /_pages/backup/update-the-config-file/understanding-baseurl.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Understanding the `baseurl:` property 3 | --- 4 | __It isn't necessary to update `baseurl:` yourself in most cases. This 5 | section is not necessary to follow through with the reset of the 6 | instructions.__ 7 | 8 | The `baseurl:` configuration property affects the root URL of your guide when 9 | served locally on your machine. When published on [18F 10 | Pages](https://pages.18f.gov/), the `baseurl:` automatically sets to the 11 | name of your repository, so you don't have to do that yourself. 12 | 13 | For example, when run locally, the URL for this guide is 14 | `http://localhost:4000/`. In production, the URL is 15 | `https://pages.18f.gov/guides-template/`. 16 | 17 | The URLs of the individual section pages are relative to the `baseurl:`. For 18 | example, the `permalink:` of this page is `{{page.url}}`. The full local 19 | URL is `http://localhost:4000{{page.url}}`, and in 20 | production it's `https://pages.18f.gov/guides-template{{page.url}}`. 21 | 22 | ### Change the `baseurl:` when serving locally 23 | 24 | If you do change the `baseurl:` property in the `_config.yml` file, 25 | **remember to include the trailing '`/`' when serving locally**. The Jekyll 26 | built-in webserver doesn't redirect to it automatically. 27 | -------------------------------------------------------------------------------- /_pages/backup/add-images.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Add images 3 | --- 4 | There are two ways to add images. First, if you'd like to keep all your images 5 | in a separate directory, create an `images/` directory and put your images inside it. 6 | Otherwise, you can keep an image in the same directory as the page that 7 | references it. 8 | 9 | You may want to use [jpegoptim](https://github.com/tjko/jpegoptim) or 10 | [optipng](http://optipng.sourceforge.net/) to optimize your images. On OS X, 11 | both are available via [Homebrew](http://brew.sh/). 12 | 13 | Now within your documents, you can reference your images as outlined below and abiding by 14 | the advice in the [Accessibility 15 | Guide](http://18f.github.io/accessibility/images/). 16 | 17 | If an image is in a separate directory: 18 | 19 | ```html 20 | Example of 21 | an included image 22 | ``` 23 | 24 | If it's in the same directory as the source document, the link should be 25 | relative to the parent directory of the document, specified as `..`: 26 | 27 | ```html 28 | Example of an included image 29 | ``` 30 | 31 | Example of an included image 32 | 33 | ### Next steps 34 | 35 | Click the _Update the Config File_ entry in the table of contents. 36 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Welcome! 2 | 3 | We're so glad you're thinking about contributing to an 18F open source project! If you're unsure about anything, just ask -- or submit the issue or pull request anyway. The worst that can happen is you'll be politely asked to change something. We love all friendly contributions. 4 | 5 | We want to ensure a welcoming environment for all of our projects. Our staff follow the [18F Code of Conduct](https://github.com/18F/code-of-conduct/blob/master/code-of-conduct.md) and all contributors should do the same. 6 | 7 | We encourage you to read this project's CONTRIBUTING policy (you are here), its [LICENSE](LICENSE.md), and its [README](README.md). 8 | 9 | If you have any questions or want to read more, check out the [18F Open Source Policy GitHub repository]( https://github.com/18f/open-source-policy), or just [shoot us an email](mailto:18f@gsa.gov). 10 | 11 | ## Public domain 12 | 13 | This project is in the public domain within the United States, and 14 | copyright and related rights in the work worldwide are waived through 15 | the [CC0 1.0 Universal public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/). 16 | 17 | All contributions to this project will be released under the CC0 18 | dedication. By submitting a pull request, you are agreeing to comply 19 | with this waiver of copyright interest. 20 | -------------------------------------------------------------------------------- /_pages/internal-clients/staffing.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Staffing 3 | --- 4 | 5 | ### What happens in this stage? 6 | Substacks review projects in the "Staging" column of the 7 | [Acqstack Kanban Board](https://docs.google.com/spreadsheets/d/1KbMQvkggVjBvFpdTqrP4Qu3Rjekaavoh_9FRfAecI24/edit?pli=1#gid=0) during Daily Kanban Standups. They send the Executive Summary around to members of their substack. They decide whether to pull the project. 8 | 9 | Once they pull a project, members of that substack are assigned and the Project Onboarding checklist is completed. 10 | 11 | ### How long does this process usually take? 12 | A few days 13 | 14 | ### Who is involved in this stage? 15 | 16 | - [Kanban Lead]({{ site.baseurl }}/shared-data/kanban-lead/) 17 | - Members of the substack 18 | 19 | ### What needs to happen to get us out of this stage? 20 | 1. Tasks done 21 | - Project card is moved from "Staging" to their substack. 22 | - Begin going through the [Project Onboarding Checklist](https://docs.google.com/document/d/1AXDLCLU3Fzp5iCASmdOM8hPU2kU0eQhGE3RmHgEBEU0/edit), including a meeting between the PM and the Bizdev team to discuss the history of the project so far. 23 | 2. Documents created 24 | - N/A 25 | 3. Approvals needed 26 | - N/A 27 | 28 | ### What can go wrong in this stage? 29 | There may not be anyone who has capacity or desire to work on this project. 30 | 31 | ### What is the next step? 32 | Onboarding 33 | 34 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | As a work of the United States Government, this project is in the 2 | public domain within the United States. 3 | 4 | Additionally, we waive copyright and related rights in the work 5 | worldwide through the CC0 1.0 Universal public domain dedication. 6 | 7 | ## CC0 1.0 Universal Summary 8 | 9 | This is a human-readable summary of the 10 | [Legal Code (read the full text)](https://creativecommons.org/publicdomain/zero/1.0/legalcode). 11 | 12 | ### No Copyright 13 | 14 | The person who associated a work with this deed has dedicated the work to 15 | the public domain by waiving all of his or her rights to the work worldwide 16 | under copyright law, including all related and neighboring rights, to the 17 | extent allowed by law. 18 | 19 | You can copy, modify, distribute and perform the work, even for commercial 20 | purposes, all without asking permission. 21 | 22 | ### Other Information 23 | 24 | In no way are the patent or trademark rights of any person affected by CC0, 25 | nor are the rights that other persons may have in the work or in how the 26 | work is used, such as publicity or privacy rights. 27 | 28 | Unless expressly stated otherwise, the person who associated a work with 29 | this deed makes no warranties about the work, and disclaims liability for 30 | all uses of the work, to the fullest extent permitted by applicable law. 31 | When using or citing the work, you should not imply endorsement by the 32 | author or the affirmer. 33 | -------------------------------------------------------------------------------- /_pages/backup/add-a-new-page/make-a-child-page.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Make a child page 3 | --- 4 | 5 | If you want to nest a page under a parent page, first create a subdirectory of 6 | `_pages` that matches the file name of the parent page, minus the `.md` or 7 | other file extension. For example, the directory containing this page is 8 | {% capture basename %}/{{ page.path | split:"/" | last }}{% endcapture %}{% capture parent_dir %}{{ page.path | replace:basename,'' }}{% endcapture %}[`{{ parent_dir }}`]({{ site.repos[0].url }}/tree/18f-pages/{{ parent_dir }}/). 9 | 10 | Then follow the instructions to [add a new page]({{ site.baseurl }}/add-a-new-page/) inside the child directory. Here is the front-matter for this page: 11 | 12 | ```yaml 13 | --- 14 | title: {{ page.title }} 15 | --- 16 | ``` 17 | 18 | Or, if the page had set its `permalink:` explicitly: 19 | 20 | ```yaml 21 | --- 22 | permalink: {{ page.url }} 23 | title: {{ page.title }} 24 | --- 25 | ``` 26 | 27 | Note the `/parent/child/` format for the permalink. This way, when you're on a 28 | parent or child page, the children are visible in the menu. (You'll need to 29 | [run `./go update_nav`]({{ site.baseurl }}/update-the-config-file/#register-pages-in-nav-bar) 30 | before the changes to the menu appear— read more about that in the _Update the 31 | config file_ chapter.) 32 | 33 | ### Next steps 34 | 35 | Click the _Add images_ entry in the table of contents to learn how to add 36 | images to your guide. 37 | -------------------------------------------------------------------------------- /_pages/external-clients/award.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Award 3 | --- 4 | 5 | ### What happens in this stage? 6 | If the final price is more than the previous IX: IX must be rewritten and updated with the final price, IGCE needs to be updated with final price. Submit these to NCR together. 7 | 8 | NCR makes the award. Notify the Director and Deputy Director of Acquisitions the award has been made by email. 9 | 10 | NCR designates a COR (who can, and in almost every case, should be a member of Acqstack). For Agile BPA, they must be a Level 2 COR or higher. Once TTS decides who the COR should be, we send the COR 2 Certification Letter to NCR. NCR will verify it, then issue a COR Designee letter to that person. Designate an alternate COR (aCOR). 11 | 12 | Update Github Pages site with the relevant information: pages.18f.gov/ads-bpa. 13 | 14 | Once all that is done, you can schedule the kickoff with the vendor, the client, and NCR. NCR has a 15 minute-or-so agenda they will go through, then turn it over to you and the client. 15 | 16 | Perform any necessary external communications about this award and debrief unsuccessful vendors. 17 | 18 | ### How long does this process usually take? 19 | A few days. 20 | 21 | ### Who is involved in this stage? 22 | 23 | ### What needs to happen to get us out of this stage? 24 | 1. Tasks done 25 | 2. Documents created 26 | 3. Approvals needed 27 | 28 | ### What can go wrong in this stage? 29 | 30 | ### What is the next step? 31 | 32 | -------------------------------------------------------------------------------- /_pages/external-clients/release-rfp.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Release RFP 3 | --- 4 | 5 | ### What happens in this stage? 6 | NCR gives us the final package to review. Once we approve it, they will put it out on eBuy within a few hours. 7 | 8 | TTS creates a Github repository for this buy. Include a Contributing and License file, a Readme with the RFQ number, dates when questions are due, when final bids are due, and any other necessary information for vendors. Also create a Issues template for vendors to use when posting questions. Post the solicitation documents in a folder on that repository. You can use the [Forest Service e-Permitting API repo](https://github.com/18F/bpa-fs-epermit-api) as a template. 9 | 10 | ### How long does this process usually take? 11 | A few hours to a day or two. 12 | 13 | ### Who is involved in this stage? 14 | - TTS PM 15 | - TTS CO 16 | - NCR CO 17 | 18 | ### What needs to happen to get us out of this stage? 19 | 1. Tasks done 20 | - Github repo created 21 | - Solicitation documents posted 22 | 2. Documents created 23 | - Contributing, License, Readme, Issues Template files created 24 | 3. Approvals needed 25 | - TTS and Client final go-ahead that solicitation package looks good to post 26 | 27 | ### What can go wrong in this stage? 28 | Sometimes you will have to spend some extra time converting the solicitation documents back into markdown, if that was lost or unformatted along the way. 29 | 30 | ### What is the next step? 31 | Vendor Q&A -------------------------------------------------------------------------------- /_pages/internal-clients/onboarding.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Onboarding 3 | --- 4 | 5 | ### What happens in this stage? 6 | A project is staffed! Now it's time to get everyone up to speed. 7 | 8 | Meet with TTS Acquisition Management and Oversight to decide if this should be an internal buy or an NCR buy. If NCR, loop them in immediately and proceed to Agreements. If internal buy, do an MOU for contracted dollar amount between Acqstack and the program office. No published process currently exists for this. 9 | 10 | Schedule a kickoff meeting with the client to introduce them to the team, discuss the project, and establish next steps. 11 | 12 | ### How long does this process usually take? 13 | A week or two, depending on scheduling. 14 | 15 | ### Who is involved in this stage? 16 | 17 | - The client team 18 | - The Acqstack team 19 | 20 | ### What needs to happen to get us out of this stage? 21 | 1. Tasks done 22 | - Kickoff meeting 23 | 2. Documents created 24 | - N/A 25 | 3. Approvals needed 26 | - N/A 27 | 28 | ### What can go wrong in this stage? 29 | The fresh team tends to look around and say "Wait, what!? Why is this happening? Who told them that?" As a member of the project team, it's important to challenge all assumptions about the project. There are frequently expectation differences. Clients will often feel burned by the agreements process, and by shifting POC's on the TTS side. 30 | 31 | Be aware, the client point of contact may have changed. 32 | 33 | ### What is the next step? 34 | Agreements 35 | -------------------------------------------------------------------------------- /_pages/internal-clients/evaluation.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Proposal Evaluation 3 | --- 4 | 5 | ### What happens in this stage? 6 | TTS and the client team forms an evaluation panel. This panel should be briefed by the TTS CO about how to properly do the evaluation and what to avoid doing to ensure compliance with all rules and regulations. 7 | 8 | Evaluation panels are typically made up of a client product owner, a product lead, and a technical lead. 9 | 10 | TTS will typically do oral interviews with vendors, as well as evaluations of the written proposal. 11 | 12 | NCR handles formal communications with all bidders. 13 | 14 | After evaluations are completed, NCR releases pricing information to TTS. Final determinations are then made. 15 | 16 | ### How long does this process usually take? 17 | A few days to two weeks, depending on type of solicitation and number of bidders. 18 | 19 | ### Who is involved in this stage? 20 | - NCR CO 21 | - TTS/client eval team 22 | - Vendor teams 23 | 24 | ### What needs to happen to get us out of this stage? 25 | 1. Tasks done 26 | - All vendor bids must be evaluated, and decisions documented 27 | - A winning vendor is chosen 28 | 2. Documents created 29 | - (Depending on evaluation criteria) Consesnsus/summary document 30 | - (Depending on evaluation criteria) Strengths and weaknesses for each bid (if there was more than one proposal) 31 | 3. Approvals needed 32 | - Evaluation team 33 | - NCR CO 34 | 35 | ### What can go wrong in this stage? 36 | 37 | 38 | ### What is the next step? 39 | Award. 40 | 41 | -------------------------------------------------------------------------------- /_pages/external-clients/proposals.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Proposals 3 | --- 4 | 5 | ### What happens in this stage? 6 | Vendors submit their proposals to the NCR CO. The CO then sends us the proposals, sans the pricing information (so the evaluation team in the next phase can make an evaluation unbiased by price). 7 | 8 | TTS is moving toward requiring vendors to comply with a specific proposal template. Making all proposals consistent would speed up evaluations and decrease the amount of content and overhead a vendor needs to create in order to bid. 9 | 10 | ### How long does this process usually take? 11 | 8-10 days after Q&A answers are submitted (if applicable) 12 | 13 | ### Who is involved in this stage? 14 | - Vendor POC 15 | - NCR CO 16 | 17 | ### What needs to happen to get us out of this stage? 18 | 1. Tasks done 19 | - Vendors needs to submit proposals to NCR CO 20 | 2. Documents created 21 | - Vendor proposals 22 | 3. Approvals needed 23 | - N/A 24 | 25 | ### What can go wrong in this stage? 26 | Vendor can submit proposals that are not compliant with a number of different requests. Some of these are insignificant, some of these violations might result in the NCR CO, or the TTS evaluation team disqualifying the proposal. 27 | 28 | We may not receive any bids. 29 | 30 | They could send the pricing information directly to the TTS evaluation team, even though it's supposed to go to the NCR CO. The eval team is not supposed to see that information until after the first round of evaluations. 31 | 32 | ### What is the next step? 33 | Evaluation. -------------------------------------------------------------------------------- /_pages/external-clients/solicitation-scoping.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Solicitation Scoping 3 | --- 4 | 5 | ### What happens in this stage? 6 | It's time to figure out what the client needs to buy, and the acquisition strategy to get it! Here, we may run workshops, do user research, and even do some prototyping. There is a coaching and consulting element to this stage as well, as we potentially teach them about the benefits of open source, agile developent, or modular contracting. 7 | 8 | We learn as much as we can to develop an acquisition strategy and prepare to draft the acquisition documents. 9 | 10 | For external buys, we only help our clients buy development work to build them a thing. 11 | 12 | ### How long does this process usually take? 13 | Weeks to months. 14 | 15 | ### Who is involved in this stage? 16 | 17 | - The client team 18 | - The Acqstack team 19 | 20 | ### What needs to happen to get us out of this stage? 21 | 1. Tasks done 22 | - Workshops or conversations to scope the need 23 | - Coaching to help client stakeholders buy in to new strategies (like agile, open source, or modular contracting) 24 | 2. Documents created 25 | - Notes about solicitation needs 26 | 3. Approvals needed 27 | - Preliminary client buy-off on acquisition strategy 28 | 29 | ### What can go wrong in this stage? 30 | Sometimes there is a desire to "just get started" and we just have a conversation with the client instead of a larger workshop. This is risky, and depending on the buy can definitely come back to bite you. 31 | 32 | ### What is the next step? 33 | Infrastructure review 34 | 35 | -------------------------------------------------------------------------------- /_pages/external-clients/staffing.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Staffing 3 | --- 4 | 5 | ### What happens in this stage? 6 | Substacks review projects in the "Staging" column of the 7 | [Acqstack Kanban Board](https://docs.google.com/spreadsheets/d/1KbMQvkggVjBvFpdTqrP4Qu3Rjekaavoh_9FRfAecI24/edit?pli=1#gid=0) during Daily Kanban Standups. They send the Executive Summary around to members of their substack. They decide whether to pull the project. 8 | 9 | Once they pull a project, members of that substack are assigned and the [Project Onboarding Checklist](https://docs.google.com/document/d/1AXDLCLU3Fzp5iCASmdOM8hPU2kU0eQhGE3RmHgEBEU0/edit) is completed. Project moved from "Pending" to "Substack Assignment" to "People assigned" on the Acqstack Kanban board. 10 | 11 | ### How long does this process usually take? 12 | A few days 13 | 14 | ### Who is involved in this stage? 15 | 16 | - [Kanban Lead]({{ site.baseurl }}/shared-data/kanban-lead/) 17 | - Members of the substack 18 | 19 | ### What needs to happen to get us out of this stage? 20 | 1. Tasks done 21 | - Project card is moved from "Staging" to their substack. 22 | - Begin going through the [Project Onboarding Checklist](https://docs.google.com/document/d/1AXDLCLU3Fzp5iCASmdOM8hPU2kU0eQhGE3RmHgEBEU0/edit), including a meeting between the PM and the Bizdev team to discuss the history of the project so far. 23 | 2. Documents created 24 | - N/A 25 | 3. Approvals needed 26 | - N/A 27 | 28 | ### What can go wrong in this stage? 29 | There may not be anyone who has capacity or desire to work on this project. 30 | 31 | ### What is the next step? 32 | Onboarding -------------------------------------------------------------------------------- /go: -------------------------------------------------------------------------------- 1 | #! /usr/bin/env ruby 2 | 3 | require 'English' 4 | 5 | Dir.chdir File.dirname(__FILE__) 6 | 7 | def try_command_and_restart(command) 8 | exit $CHILD_STATUS.exitstatus unless system command 9 | exec({ 'RUBYOPT' => nil }, RbConfig.ruby, *[$PROGRAM_NAME].concat(ARGV)) 10 | end 11 | 12 | begin 13 | require 'bundler/setup' if File.exist? 'Gemfile' 14 | rescue LoadError 15 | try_command_and_restart 'gem install bundler' 16 | rescue SystemExit 17 | try_command_and_restart 'bundle install' 18 | end 19 | 20 | begin 21 | require 'go_script' 22 | rescue LoadError 23 | try_command_and_restart 'gem install go_script' unless File.exist? 'Gemfile' 24 | abort "Please add \"gem 'go_script'\" to your Gemfile" 25 | end 26 | 27 | require 'guides_style_18f' 28 | 29 | extend GoScript 30 | check_ruby_version '2.2.4' 31 | 32 | command_group :dev, 'Development commands' 33 | 34 | def_command( 35 | :create_repo, 'Remove template files and create a new Git repository') do 36 | GuidesStyle18F.clear_template_files_and_create_new_repository Dir.pwd 37 | end 38 | 39 | def_command :update_nav, 'Update the \'navigation:\' data in _config.yml' do 40 | GuidesStyle18F.update_navigation_configuration Dir.pwd 41 | end 42 | 43 | def_command :update_theme, 'Update the guides_style_18f gem' do 44 | GuidesStyle18F.update_theme 45 | end 46 | 47 | def_command :update_gems, 'Update Ruby gems' do |gems| 48 | update_gems gems 49 | end 50 | 51 | def_command :serve, 'Serve the site at localhost:4000' do |args| 52 | serve_jekyll args 53 | end 54 | 55 | def_command :build, 'Build the site' do |args| 56 | build_jekyll args 57 | end 58 | 59 | execute_command ARGV 60 | -------------------------------------------------------------------------------- /Gemfile.lock: -------------------------------------------------------------------------------- 1 | GIT 2 | remote: git://github.com/18F/guides-style.git 3 | revision: 80bbf2308ea85b52a0d6d778981499e55cec4f72 4 | branch: v0.4.10 5 | specs: 6 | guides_style_18f (0.4.10) 7 | jekyll 8 | jekyll_pages_api 9 | jekyll_pages_api_search 10 | rouge 11 | sass 12 | 13 | GEM 14 | remote: https://rubygems.org/ 15 | specs: 16 | colorator (0.1) 17 | ffi (1.9.14) 18 | go_script (0.1.9) 19 | bundler (~> 1.10) 20 | safe_yaml (~> 1.0) 21 | htmlentities (4.3.4) 22 | jekyll (3.1.6) 23 | colorator (~> 0.1) 24 | jekyll-sass-converter (~> 1.0) 25 | jekyll-watch (~> 1.1) 26 | kramdown (~> 1.3) 27 | liquid (~> 3.0) 28 | mercenary (~> 0.3.3) 29 | rouge (~> 1.7) 30 | safe_yaml (~> 1.0) 31 | jekyll-sass-converter (1.4.0) 32 | sass (~> 3.4) 33 | jekyll-watch (1.4.0) 34 | listen (~> 3.0, < 3.1) 35 | jekyll_pages_api (0.1.6) 36 | htmlentities (~> 4.3) 37 | jekyll (>= 2.0, < 4.0) 38 | jekyll_pages_api_search (0.5.0) 39 | jekyll_pages_api (~> 0.1.4) 40 | sass (~> 3.4) 41 | kramdown (1.11.1) 42 | liquid (3.0.6) 43 | listen (3.0.8) 44 | rb-fsevent (~> 0.9, >= 0.9.4) 45 | rb-inotify (~> 0.9, >= 0.9.7) 46 | mercenary (0.3.6) 47 | rb-fsevent (0.9.7) 48 | rb-inotify (0.9.7) 49 | ffi (>= 0.5.0) 50 | redcarpet (3.3.4) 51 | rouge (1.11.1) 52 | safe_yaml (1.0.4) 53 | sass (3.4.22) 54 | 55 | PLATFORMS 56 | ruby 57 | 58 | DEPENDENCIES 59 | go_script 60 | guides_style_18f! 61 | jekyll 62 | redcarpet 63 | rouge 64 | 65 | BUNDLED WITH 66 | 1.12.5 67 | -------------------------------------------------------------------------------- /_pages/external-clients/intake.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Intake 3 | --- 4 | 5 | ### What happens in this stage? 6 | 7 | This stage is where you define and scope the engagement, and get agreement from the TTS project team and the client. This includes estimates for the cost of TTS Acquisition's services, in addition to the cost of the vendor. Ensure you have agreement from the client on the rough labor breakdown between TTS and the vendor. 8 | 9 | ### How long does this process usually take? 10 | 11 | Usually 2-8 weeks. The length of the Intake phase depends on how well-scoped the project is and whether there is familiarity with the Inter-Agency Agreement (IAA) process from the agency POC. 12 | 13 | ### Who is involved in this stage? 14 | 15 | - TTS management 16 | - Possibly a Acqstack PM 17 | - Client Product Owner 18 | - Client senior agency stakeholders 19 | 20 | ### What needs to happen to get us out of this stage? 21 | 22 | 1. Tasks done 23 | - Estimated total project cost 24 | - Defining scope 25 | 2. Documents created 26 | - Scope engagement and write relevant scoping sections of IA Part A and B. 27 | 3. Approvals 28 | - All major stakeholders need to understand and agree on the project scope and the breakdown of funding between TTS and the vendor. No official or signed approval is needed at this step though. 29 | 30 | ### What can go wrong in this stage? 31 | 32 | Lack of definition and understanding around how funding will be apportioned between TTS and the vendor could present problems later on. It is critical for the agency partner and TTS representatives to be closely involved and align all stakeholders around project scope, funding, and ownership. 33 | 34 | ### What is the next step? 35 | 36 | When the project is well-defined and all stakeholders are in agreement, the project moves into the Agreements phase. Create card in Kanban board. -------------------------------------------------------------------------------- /_pages/internal-clients/solicitation-scoping.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Solicitation Scoping 3 | --- 4 | 5 | ### What happens in this stage? 6 | It's time to figure out what the client needs to buy, and the acquisition strategy to get it! Here, we may run workshops, do user research, and even do some prototyping. 7 | 8 | We learn as much as we can to develop an acquisition strategy and prepare to draft the acquisition documents. 9 | 10 | Because this is an internal buy, the activities in this phase may vary depending on whether we're helping them scope the acquisition, or just executing on it. 11 | 12 | There are three types of things we can help our clients buy: 13 | 14 | 1. Dev work to build them a thing 15 | 2. "Off the shelf software" (COTS) 16 | 3. Body shop/staff augmentation 17 | 18 | If you find yourself doing a heavy amount of prototyping and the consulting aspect becomes a much heavier lift than just prepping to process a buy, that's a signal this project might be better done by 18F's Custom Partner Solutions. Consider transitioning the project to 18F. 19 | 20 | ### How long does this process usually take? 21 | Weeks to months. 22 | 23 | ### Who is involved in this stage? 24 | 25 | - The client team 26 | - The Acqstack team 27 | - Acqusiition Mangagement and Oversight 28 | 29 | ### What needs to happen to get us out of this stage? 30 | 1. Tasks done 31 | - Workshops or conversations to scope the need 32 | 2. Documents created 33 | - Notes about solicitation needs 34 | 3. Approvals needed 35 | - Preliminary client buy-off on acquisition strategy 36 | 37 | ### What can go wrong in this stage? 38 | Sometimes there is a desire to "just get started" and we just have a conversation with the client instead of a larger workshop. This is risky, and depending on the buy can definitely come back to bite you. 39 | 40 | ### What is the next step? 41 | Infrastructure review 42 | -------------------------------------------------------------------------------- /_pages/external-clients/co-team-assigned.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR CO Team Assigned 3 | --- 4 | 5 | ### What happens in this stage? 6 | Once you have the required documents from the Drafting stage, the PM should contact the [NCR PM]({{ site.baseurl }}/shared-data/ncr-pm/) to set up a kickoff meeting. NCR will bring along a Contracting Officer and Contracting Specialist (CS). 7 | 8 | During this kickoff, you will walk through the [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/), explain the buy to NCR, and establish a mutually agreed upon timeline of events. 9 | 10 | This is also a good time to agree on communication patterns (who from NCR is sending updates? Who is receiving them at TTS? How often are updates, and what types of events do you want to be updated about?) and workflow (doing all reviews and edits in Google Docs. If someone from NCR needs Google Docs training, let us know and we'll be happy to provide it.) 11 | 12 | ### How long does this process usually take? 13 | A few days, if NCR is not at their WIP limit of active projects. 14 | 15 | ### Who is involved in this stage? 16 | - NCR PM 17 | - TTS project team 18 | - Client project team 19 | - NCR CO 20 | - NCR CS 21 | 22 | ### What needs to happen to get us out of this stage? 23 | 1. Tasks done 24 | - NCR assigns a CO and CS. 25 | - Kickoff meeting with NCR. 26 | - NCR commits to a timeline. 27 | 2. Documents created 28 | - N/A 29 | 3. Approvals needed 30 | - N/A 31 | 32 | ### What can go wrong in this stage? 33 | Sometimes this step is done just through email. This is pretty universally a bad plan, and almost guarantees problems down the road. A live conversation, either sit down or video call, is necessary to ensure all parties are on the same page about the acquisitiion strategy and timelines. 34 | 35 | It's really important that NCR actually confirms their committment to the timeline. Put extra EXTRA emphasis on this near the end of the fiscal/calendar year. 36 | 37 | ### What is the next step? 38 | Acquisition Package Review 39 | 40 | 41 | -------------------------------------------------------------------------------- /_pages/internal-clients/co-team-assigned.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: NCR CO Team Assigned 3 | --- 4 | 5 | ### What happens in this stage? 6 | Once you have the required documents from the Drafting stage, alert the [TTS Acquisitions Deputy Director]({{ site.baseurl }}/shared-data/tts-acq-dep-director/), who will set up a kickoff with the [NCR PM]({{ site.baseurl }}/shared-data/ncr-pm/). NCR will bring along a [Contracting Officer (CO)]({{ site.baseurl }}/shared-data/ncr-co/) and [Contracting Specialist (CS)]({{ site.baseurl }}/shared-data/ncr-cs/). 7 | 8 | During this kickoff, you will walk through the [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/), explain the buy to NCR, and establish a mutually agreed upon timeline of events. 9 | 10 | This is also a good time to agree on communication patterns (who from NCR is sending updates? Who is receiving them at TTS? How often are updates, and what types of events do you want to be updated about?) and workflow (doing all reviews and edits in Google Docs. If someone from NCR needs Google Docs training, let us know and we'll be happy to provide it.) 11 | 12 | ### How long does this process usually take? 13 | A few days, if NCR is not at their WIP limit of active projects. 14 | 15 | ### Who is involved in this stage? 16 | - NCR PM 17 | - TTS project team 18 | - Client project team 19 | - [NCR CO]({{ site.baseurl }}/shared-data/ncr-co/) 20 | - [NCR CS]({{ site.baseurl }}/shared-data/ncr-cs/) 21 | 22 | ### What needs to happen to get us out of this stage? 23 | 1. Tasks done 24 | - NCR assigns a CO and CS. 25 | - Kickoff meeting with NCR. 26 | - NCR commits to a timeline. 27 | 2. Documents created 28 | - N/A 29 | 3. Approvals needed 30 | - N/A 31 | 32 | ### What can go wrong in this stage? 33 | Sometimes this step is done just through email. This is pretty universally a bad plan, and almost guarantees problems down the road. A live conversation, either sit down or video call, is necessary to ensure all parties are on the same page about the acquisitiion strategy and timelines. 34 | 35 | ### What is the next step? 36 | Acquisition Package Review 37 | 38 | 39 | -------------------------------------------------------------------------------- /_pages/external-clients/acq-package-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Acquisition Package Review 3 | --- 4 | 5 | ### What happens in this stage? 6 | The NCR CO and CS review the solicitation documents the TTS project team put together. They may ask for changes, additional explanations, additional documents, or for certain sections to be rewritten. Everyone should be using Google Docs to review and make edits. 7 | 8 | After changes are made, go back and get the client's approval. Then go back and get NCR's approval. 9 | 10 | This approval process is a cycle. Keep going until everyone is happy. 11 | 12 | This process will take way longer than you expect it to, even for short and simple procurements. 13 | 14 | Be sure to work with the NCR CO to agree on a evaluation "consensus report" strategy for evaluation of bids with NCR CO. You want to ensure the NCR CO has no issues with the evaluation strategy. 15 | 16 | ### How long does this process usually take? 17 | 3-5 weeks. Sometimes longer. 18 | 19 | ### Who is involved in this stage? 20 | - NCR CO 21 | - NCR CS 22 | - TTS Project Team 23 | - Client project team 24 | - Many approvers 25 | 26 | ### What needs to happen to get us out of this stage? 27 | 1. Tasks done 28 | - All approvers must sign off on the final version of the documents. 29 | - NCR and TTS mutually agree documents are "locked" and no more edits will be made by either party. 30 | - Agree on a evaluation "consensus report" strategy for evaluation of bids with NCR CO. 31 | 2. Documents created 32 | - N/A 33 | 3. Approvals needed 34 | - NCR CO 35 | - NCR CS 36 | - TTS Project Team 37 | - Client project team 38 | - Client approvers (OGC, find out who else) 39 | - TTS front office (?) 40 | - TTS Commissioner (?) 41 | - TTS OGC 42 | - NCR OGC 43 | - NCR Commissioner 44 | 45 | ### What can go wrong in this stage? 46 | There is a whole lot of going in circles getting approvals at this stage. Often, people farther from the project work (such as OGC) won't be properly read in on why we're taking a certain approach or doing things differently than the standard way. Be prepared for speedbumps, unexpected requests, or changes that don't seem to make sense given the acquisition strategy you've put together. 47 | 48 | ### What is the next step? 49 | Release the RFP. 50 | 51 | 52 | -------------------------------------------------------------------------------- /_pages/external-clients/bizdev.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Business Development 3 | --- 4 | 5 | ### What happens in this stage? 6 | 7 | Biz Dev happens in three primary ways: 8 | 9 | 1. Repeat business with an agency who has been a TTS partner before 10 | 2. Inbound request from an agency via a referral or from hearing about TTS’s track record 11 | 3. TTS staff making outbound inquiries to agencies for important projects we can help execute (essentially cold calls) 12 | 13 | TTS evaluates each potential project based on whether an acquisition is the right thing for the agency to do at the time, especially compared to alternatives (for example, building a small prototype instead to validate initial assumptions). 14 | 15 | TTS and the agency mutually agree to move forward and work together on an assisted acquisition. 16 | 17 | ### How long does this process usually take? 18 | 19 | The length of time in Biz Dev is highly variable depending on the urgency of the agency’s needs and how familiar the agency is with how TTS works. 20 | 21 | ### Who is involved in this stage? 22 | 23 | One or two members of TTS Acquisitions, the agency sponsor for the potential project, and Agency Partnerships. 24 | 25 | ### What needs to happen to get us out of this stage? 26 | 27 | 1. Tasks done 28 | - Ensure funding availability: Is there enough money available to execute a TTS assisted acquisition? When does the funding expire (1 year money vs multi-year money)? 29 | - Agency readiness: Has the partner agency identified an empowered Product Owner? Does the project have senior stakeholder buy-in? Does the agency understand the agile process and are they willing to execute the project using open source code? If modular procurement is appropriate, are they willing to execute the procurements that way? 30 | - Acqstack and an agency agree to move forward and work together on an assisted acquisition. 31 | 2. Documents created 32 | - N/A 33 | 3. Approvals 34 | - TTS Acquisitions management 35 | - Agency management 36 | 37 | ### What can go wrong in this stage? 38 | 39 | This stage is intended to be exploratory, and very low-risk for all parties. No funding has been obligated and TTS and the potential partner agency are trying to establish fit. 40 | 41 | As a reminder, no work is done before a signed agreement is in place. 42 | 43 | ### What is the next step? 44 | 45 | Intake. 46 | -------------------------------------------------------------------------------- /_pages/internal-clients/award.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Award 3 | --- 4 | 5 | ### What happens in this stage? 6 | If the final price is more than the previous IX, the [IX]({{ site.baseurl }}/shared-data/IX/) must be rewritten and updated with the final price. The [IGCE]({{ site.baseurl }}/shared-data/IGCE/) must also be updated to match the final price. If these need to be updated, resubmit the updated documents to NCR together. Will need to get the IX re-approved by everyone in the approval chain. 7 | 8 | NCR will make the award to the vendor. 9 | 10 | Any unsuccessful vendors may request a debrief from NCR/TTS/the client. 11 | 12 | Plan kickoff meeting with vendor to go over contract details, expectations, and next steps. Clarify with [NCR CO]({{ site.baseurl }}/shared-data/ncr-co/) what they want their role in setting up and conducting this meeting to be. 13 | 14 | Conduct any necessary external communications about the award (blog posts, tweets, announcements, etc). You may need to involve the Office of Strategic Communications (OSC) (previously Office of Communications and Marketing (OCM)). Talk to #outreach if you need to get in touch with them. 15 | 16 | Check in on/reinitiate GSA IT/infrastructure reviews. Get pilot status if necessary and haven't already gotten it. If a GSA IT review is necessary but not yet complete, there must be language in the award that says the award is contingent on GSA IT approval. 17 | 18 | ### How long does this process usually take? 19 | A few days to a week, assuming all financial documents (ie: the IX) were already submitted and correct. 20 | 21 | ### Who is involved in this stage? 22 | - [NCR CO]({{ site.baseurl }}/shared-data/ncr-co/) 23 | - TTS/client team 24 | - Potentially OSC/OCM 25 | - Winning vendor 26 | - Unsuccessful vendors 27 | 28 | ### What needs to happen to get us out of this stage? 29 | 1. Tasks done 30 | - NCR makes the award and winning vendor is notified 31 | - Unsuccessful vendors are notified 32 | - Kickoff meeting scheduled with winning vendor 33 | - Check in on GSA IT/infrastructure reviews, if necessary 34 | 2. Documents created 35 | - Revised [IX]({{ site.baseurl }}/shared-data/ix/) and [IGCE]({{ site.baseurl }}/shared-data/IGCE/), if necssary. 36 | 3. Approvals needed 37 | - N/A 38 | 39 | ### What can go wrong in this stage? 40 | GSA IT review could result in the rejection of the winning vendor. 41 | 42 | ### What is the next step? 43 | Post-award management and closeout. 44 | -------------------------------------------------------------------------------- /_pages/internal-clients/acq-package-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Acquisition Package Review 3 | --- 4 | 5 | ### What happens in this stage? 6 | The [NCR CO]({{ site.baseurl }}/shared-data/ncr-co/) and [NCR CS]({{ site.baseurl }}/shared-data/ncr-cs/) review the solicitation documents the TTS project team put together. They may ask for changes, additional explanations, additional documents, or for certain sections to be rewritten. Everyone should be using Google Docs to review and make edits. 7 | 8 | After changes are made, go back and get the client's approval. Then go back and get NCR's approval. 9 | 10 | This approval process is a cycle. Keep going until everyone is happy. 11 | 12 | This process will take way longer than you expect it to, even for short and simple procurements. 13 | 14 | ### How long does this process usually take? 15 | 3-5 weeks. Sometimes longer. 16 | 17 | ### Who is involved in this stage? 18 | - [NCR CO]({{ site.baseurl }}/shared-data/ncr-co/) 19 | - [NCR CS]({{ site.baseurl }}/shared-data/ncr-cs/) 20 | - TTS Project Team 21 | - Client project team 22 | - Many approvers 23 | 24 | ### What needs to happen to get us out of this stage? 25 | 1. Tasks done 26 | - All approvers must sign off on the final version of the documents. 27 | - NCR and TTS mutually agree documents are "locked" and no more edits will be made by either party. 28 | 2. Documents created 29 | - N/A 30 | 3. Approvals needed 31 | - [NCR CO]({{ site.baseurl }}/shared-data/ncr-co/) 32 | - [NCR CS]({{ site.baseurl }}/shared-data/ncr-cs/) 33 | - TTS Project Team 34 | - Client project team 35 | - TTS front office (?) 36 | - TTS Commissioner (?) 37 | - [TTS Assistant Commissioner]({{ site.baseurl }}/shared-data/tts-assistant-commissioner/) for that program office 38 | - [TTS OGC]({{ site.baseurl }}/shared-data/tts-ogc/) 39 | - [NCR OGC]({{ site.baseurl }}/shared-data/ncr-ogc/) 40 | - [NCR Commissioner]({{ site.baseurl }}/shared-data/ncr-commissioner/) 41 | 42 | ### What can go wrong in this stage? 43 | There is a whole lot of going in circles getting approvals at this stage. Often, people farther from the project work (such as OGC) won't be properly read in on why we're taking a certain approach or doing things differently than the standard way. Be prepared for speedbumps, unexpected requests, or changes that don't seem to make sense given the acquisition strategy you've put together. 44 | 45 | ### What is the next step? 46 | Release the RFP. 47 | 48 | 49 | -------------------------------------------------------------------------------- /_pages/external-clients/evaluation.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Proposal Evaluation 3 | --- 4 | 5 | ### What happens in this stage? 6 | TTS and the client team forms an Technical Evaluation Panel or Board (TEP). This panel should be briefed by the TTS CO and NCR CO about how to properly do the evaluation and what to avoid doing to ensure compliance with all rules and regulations. 7 | 8 | Evaluation panels are typically made up of a client product owner, a product lead, and a technical lead. 9 | 10 | The evaluation panel will evaluate the written proposals, and then typically do oral interviews with vendors as well. Evaluate vendors on written proposals first so you have an idea of what you want to particularly listen to for that vendor during the orals. If you write it into the RFP, you can also disqualify a vendor based on their written proposal and skip their oral interview. 11 | 12 | Scheduling these is much easier when you give the vendors windows of time to sign up for, rather than asking what works for them. 13 | 14 | NCR handles formal communications with all bidders. 15 | 16 | After evaluations are completed, NCR releases pricing information to TTS. Final determinations are then made. 17 | 18 | ### How long does this process usually take? 19 | 1-3 weeks, depending on type of solicitation, number of bidders, and whether there are oral interviews. 20 | 21 | ### Who is involved in this stage? 22 | - NCR CO 23 | - TTS/client eval team 24 | - Vendor teams 25 | 26 | ### What needs to happen to get us out of this stage? 27 | 1. Tasks done 28 | - All vendor bids must be evaluated, and decisions documented 29 | - A winning vendor is chosen 30 | 2. Documents created 31 | - Fill out oral evaluation ([template](https://docs.google.com/document/d/1iuHFhuSQHSPJ4hLeYLUhPPWTXAZRKxIEpy4pxOafHZc/edit)) 32 | - (Depending on evaluation criteria) Consensus/summary document 33 | - (Depending on evaluation criteria) Strengths and weaknesses for each bid (if there was more than one proposal) 34 | 3. Approvals needed 35 | - Evaluation team 36 | - NCR CO 37 | 38 | ### What can go wrong in this stage? 39 | Timeline might go longer due to client-side issues. 40 | 41 | Scheduling oral interviews can be tough, and a vendor missing their oral interview can delay the whole timeline. 42 | 43 | Written proposals take a long time to evaluate when there they don't follow a standard template. 44 | 45 | Because price is introduced last, sometimes preferred vendor is out of price range. 46 | 47 | ### What is the next step? 48 | Award. -------------------------------------------------------------------------------- /_pages/internal-clients/qa.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Vendor Q&A 3 | --- 4 | 5 | ### What happens in this stage? 6 | This phase is optional, depending on the type of solicitation. A full and open competition would have time baked in for questions and answers from vendors, so they can prepare better proposals and more accurate price quotes. A direct award of some sort would not require this step. 7 | 8 | Traditionally, vendors email their questions to the CO, who then sends them to the TTS and client team. Answers are written, then sent back to the CO who posts the answers as an amendment to the solicitation for everyone to see. 9 | 10 | Alternatively, and with CO's discretion, you can recieve questions via google forms, or by having vendors post questions as Github Issues, and the government can answer on github. All the questions and answers should still be officially posted as an amendment when the Q&A period closes. 11 | 12 | It is up to the CO’s discretion to allow questions after the Q&A has closed. Additional amendments should be posted for all vendors to see with answers to any further questions. 13 | 14 | ### How long does this process usually take? 15 | There is no set-in-stone timelines, but generally if we're buying off of a schedules or a BPA, we give vendors about 1 week to submit questions. If we're buying with a full & open competition, we give vendors 2 weeks to submit questions. 16 | 17 | We spend a 2 or 3 days answering. Posting the answers (which traditionally happens by posting an amendment to the solicitation) can happen in 1 day. 18 | 19 | ### Who is involved in this stage? 20 | - NCR CO 21 | - TTS team 22 | - Client team 23 | - Vendor points of contact 24 | 25 | ### What needs to happen to get us out of this stage? 26 | 1. Tasks done 27 | - Questions recieved by TTS and client team 28 | - Answers are posted publicly 29 | 2. Documents created 30 | - Amendment to the solicitation with questions and answers 31 | 3. Approvals needed 32 | - Some answers may need to be approved by legal, the CO, the client team, or the TTS team, depending on the subject matter. 33 | - The CO may want to approve answers to all questions before they are posted publicly. 34 | 35 | ### What can go wrong in this stage? 36 | There can be more questions than expected, which can take a long time to answer. Questions can also reveal problems with the original solicitation that require more significant revisions. No matter how long you give vendors, history indicates they will typically wait until the last day possible to submit questions. 37 | 38 | ### What is the next step? 39 | Proposals. 40 | 41 | -------------------------------------------------------------------------------- /_pages/internal-clients/infrastructure-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Infrastructure Review 3 | --- 4 | 5 | ### What happens in this stage? 6 | If you are buying software, pay attention to this stage! If you're buying access to people, you can proceed to the Solicitation Drafting stage. 7 | 8 | There is a preliminary review, and a full GSA IT review. 9 | 10 | [Get more details about the Infrastructure Review process here.](https://docs.google.com/document/d/1AUyRggdKWLRcHC3E4ssHE_2tmOaDYTv0ex0lgwbwFSA/edit) A summary is below: 11 | 12 | If you know what you want to buy: 13 | 14 | 1. Is anyone else using this software, or something similar to it? Ping your [Infrastructure Lead]({{ site.baseurl }}/shared-data/infra-lead/) to find out. 15 | 2. Check the pre-approved software list [LINK]. If the software is on that list, no review or approvals necessary. 16 | 3. If it's not on that list, send your request to the [Infrastructure Lead]({{ site.baseurl }}/shared-data/infra-lead/) for that business unit or department for review. You may not proceed until this initial review is complete. 17 | 4. Once Infrastructure approves, be sure you get added to the official GSA IT review process (this includes a Legal and 508 compliance review). 18 | 5. [GET FEEDBACK ON THIS SECTION] You may continue with the procurement while GSA IT review happens. You can potentially apply for pilot status here, through a p-card. 19 | 20 | If you don't know what you want to buy: 21 | 22 | 1. In the case of a full and open competition where you're unsure at this phase who will even bid, let alone win, Infrastructure review cannot feasible happen here. 23 | 2. It must happen immediately after award, and be sure to include language that awards the contract to the winner pending successful GSA IT review. 24 | 25 | ### How long does this process usually take? 26 | Potentially months, but you can proceed once the preliminary review is done, which should take less than a week. 27 | 28 | ### Who is involved in this stage? 29 | 30 | - Acqstack team 31 | - The program office's [Infrastructure Lead]({{ site.baseurl }}/shared-data/infra-lead/) 32 | - GSA IT 33 | 34 | ### What needs to happen to get us out of this stage? 35 | 36 | 1. Tasks done 37 | - Preliminary review complete 38 | - GSA IT review initiated 39 | 2. Documents created 40 | - N/A 41 | 3. Approvals needed 42 | - [Infrastructure Lead]({{ site.baseurl }}/shared-data/infra-lead/) 43 | 44 | ### What can go wrong in this stage? 45 | 46 | You could get denied by Infrastructure! Their review is typically looking to answer the question "Could this sort of thing pass GSA IT review?" 47 | 48 | ### What is the next step? 49 | Solicitation drafting. 50 | 51 | -------------------------------------------------------------------------------- /_pages/external-clients/qa.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Vendor Q&A 3 | --- 4 | 5 | ### What happens in this stage? 6 | This phase is optional, depending on the type of solicitation. Often, you want to bake in time for questions and answers from vendors so they can prepare better proposals and more accurate price quotes. It's time to make it clear between the vendor and the client what is expected of them. It's also a chance for the vendor to point out inconsistencies in scope or objectives in different documents, and for us to correct those inconsistencies, and to clear up any technical concerns they have. 7 | 8 | A direct award does not require this step, though they may still have questions. 9 | 10 | Vendors post their questions as an issue on the Github repo. Configure this a Google Sheet with this script [FIND THE LINK TO THIS] that connects to your Github repo. It will copy issues from the repo into the Google Sheet. There TTS, the client, and NCR can collaborate on answers. The NCR CO will approve the answer, then TTS can post the answer as a response to the Github Issue. 11 | 12 | At the end of the Q&A period, the NCR CO will post all questions and answers as an amendment on eBuy, the system of record. 13 | 14 | It is up to the CO’s discretion to allow questions after the Q&A has closed. Additional amendments should be posted for all vendors to see with answers to any further questions. 15 | 16 | ### How long does this process usually take? 17 | There is no set-in-stone timelines, but for the Agile BPA we generally give vendors about 1 week to submit questions. 18 | 19 | We spend a 2 or 3 days answering. Posting the answers (which traditionally happens by posting an amendment to the solicitation) can happen in 1 day. 20 | 21 | ### Who is involved in this stage? 22 | - NCR CO 23 | - TTS team 24 | - Client team 25 | - Vendor points of contact 26 | 27 | ### What needs to happen to get us out of this stage? 28 | 1. Tasks done 29 | - Questions recieved by TTS and client team 30 | - Answers are posted publicly 31 | 2. Documents created 32 | - Amendment to the solicitation with questions and answers 33 | 3. Approvals needed 34 | - Some answers may need to be approved by legal, the CO, the client team, or the TTS team, depending on the subject matter. 35 | - The CO will likely want to approve answers to all questions before they are posted publicly. 36 | 37 | ### What can go wrong in this stage? 38 | There can be more questions than expected, which can take a long time to answer. Questions can also reveal problems with the original solicitation that require more significant revisions. 39 | 40 | No matter how long you give vendors, history indicates they will typically wait until the last day possible to submit questions. Try posting in the Readme that you encourage vendors to ask questions early and often, and explain they'll get their answers faster. 41 | 42 | If a vendor posts a question after the Q&A time is done and you choose to answer that question, you must re-open Q&A for everyone for some period of time. 43 | 44 | ### What is the next step? 45 | Proposals. 46 | -------------------------------------------------------------------------------- /_pages/external-clients/agreements.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Agreements 3 | --- 4 | 5 | ### What happens in this stage? 6 | 7 | The TTS IAA process is used to formalize a tripartite agreement between TTS, National Capital Region (NCR) Contracting Office, and an agency partner where TTS/NCR will perform an assisted acquisition on behalf of the agency partner. 8 | 9 | The partner agency point of contact completes the [IAA prep form](https://docs.google.com/a/gsa.gov/forms/d/e/1FAIpQLSdcP-ifAEPjk1FUK4q_hzkSmlAJaIyGx9y_4BSLrJI_ZLdVzw/viewform) and provides all information for the IAA to TTS. Ensure the funding official, product owner, and other stakeholders at the agency approve the cost and understand they are paying for TTS labor and vendor labor. 10 | 11 | Once you have all the data you need, you can fill out the [IAA Request Form](https://docs.google.com/a/gsa.gov/forms/d/e/1FAIpQLSdRQerRDxl4hPX_zTQJcY9fR9i0z3LI3dLQiKE0uyJ5fF666g/viewform). This provides all the information the TTS Agreements team needs to generate the IAA for you. 12 | 13 | The TTS Agreements team will manage the workflow of shipping all documents to all the right approvers - please do not reach out to reviewers and approvers to request signatures directly. 14 | 15 | We cannot leave this stage until money is obligated, not just IAA signed. 16 | 17 | ### How long does this process usually take? 18 | As of December 2016, the average time from IAA Request Form being filled out to final signature is 42 days, and typically ranges from 30 to 60 days. The amount of time spent in the Agreements process depends largely on how fast TTS and the agency partner get the necessary approvals and signatures and finalize the agreement. 19 | 20 | ### Who is involved in this stage? 21 | 22 | - TTS: Acquisitions Team, Agreements Team, Finance Team 23 | - NCR: OGC/Legal, Project Manager 24 | - Partner agency: Legal, Project Team 25 | 26 | ### What needs to happen to get us out of this stage? 27 | 1. Tasks done 28 | - Partner agency completes [IAA prep form](https://docs.google.com/a/gsa.gov/forms/d/e/1FAIpQLSdcP-ifAEPjk1FUK4q_hzkSmlAJaIyGx9y_4BSLrJI_ZLdVzw/viewform) and TTS ensures we have everything needed for IAA creation. 29 | - TTS PM filled out the [IAA Request Form](https://docs.google.com/a/gsa.gov/forms/d/e/1FAIpQLSdRQerRDxl4hPX_zTQJcY9fR9i0z3LI3dLQiKE0uyJ5fF666g/viewform). 30 | - Finalize IAA 31 | - Money is obligated 32 | 2. Documents created 33 | - IA Part A 34 | - IA Part B 35 | - Determination of best procurement approach 36 | - Different forms as required by other agencies 37 | 3. Approvals needed 38 | - TTS Commissioner 39 | - NCR Deputy Commissioner 40 | - TTS OCFO 41 | - FAS/NCR OCFO 42 | - TTS OGC 43 | - NCR OGC 44 | - Client point of contact 45 | - Client Finance point of contact 46 | - Client legal 47 | - Contracting Officer from client's acquisition team may need to be the signatory, or at least look at it. Ask your client. 48 | 49 | ### What can go wrong in this stage? 50 | 51 | This process can take an enormous amount of time if there is not a good process and working relationship between the project team, legal, finance, and the approving authorities at TTS, NCR, and the agency. 52 | 53 | ### What is the next step? 54 | 55 | When IAA goes out for client signature, Acqstack Management creates a card for the project on the Acqstack Kanban Board under "IAA pending". 56 | 57 | Once the IAA is signed, move into the Staffing phase. -------------------------------------------------------------------------------- /_pages/internal-clients/agreements.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Agreements 3 | --- 4 | 5 | ### What happens in this stage? 6 | Warning: You can proceed with the project before this phase is done for internal procurements, but expect this process to be long and full of unexpected surprises and requirements. Start this phase as soon as a TTS PM is assigned to your project, and stay on top of it. 7 | 8 | To initiate a new project with an internal (TTS) client, TTS must create a new "intra-agency agreement" with NCR to define the scope of work for this procurement action and to define the necessary financial information. These are described in two documents, called [IA Part A]({{ site.baseurl }}/shared-data/ia-part-a/) and [IA Part B]({{ site.baseurl }}/shared-data/ia-part-b/)'s respectively. These documents are templates that should not be edited, except for very specific sections referencing your particular client and project. 9 | 10 | All of these documents must go through their signature and approval processes. We currently use TTS's Interagency Agreements team for agreements. Once you have filled out the client and project specific parts of the IA Part A and B, fill out the [IAA Request Form](https://docs.google.com/a/gsa.gov/forms/d/e/1FAIpQLSdRQerRDxl4hPX_zTQJcY9fR9i0z3LI3dLQiKE0uyJ5fF666g/viewform) and team ops will fill out the rest of the information on the IA forms, will send to [TTS OGC]({{ site.baseurl }}/shared-data/tts-ogc/) and [NCR OGC]({{ site.baseurl }}/shared-data/ncr-ogc/) for review, and will route for signatures. 11 | 12 | The client must also create and submit an [IX]({{ site.baseurl }}/shared-data/IX/) to NCR. Who handles the IX generation process depends on which office the client is in. For TTS, talk to [TTS Finance]({{ site.baseurl }}/shared-data/tts-finance/), for OPP talk to Stephanie.Webb@gsa.gov. 13 | 14 | ### How long does this process usually take? 15 | Huge variance. Anywhere from a few weeks to a months and months. As of December 2016, the average time is 42 days. 16 | 17 | ### Who is involved in this stage? 18 | - TTS Agreements team 19 | - [TTS Finance]({{ site.baseurl }}/shared-data/tts-finance/) 20 | - [NCR Legal/OGC]({{ site.baseurl }}/shared-data/ncr-ogc/) 21 | - [NCR PM]({{ site.baseurl }}/shared-data/ncr-pm/) 22 | - [TTS Legal/OGC]({{ site.baseurl }}/shared-data/tts-ogc/) 23 | - TTS team 24 | - Client 25 | - [NCR Deputy Commissioner]({{ site.baseurl }}/shared-data/ncr-dep-commissioner/) 26 | - [TTS Commissioner]({{ site.baseurl }}/shared-data/tts-commissioner/) 27 | - [TTS OCFO]({{ site.baseurl }}/shared-data/tts-ocfo/) 28 | - NCR OCFO 29 | - Client POC 30 | - Client Finance POC 31 | 32 | ### What needs to happen to get us out of this stage? 33 | 1. Tasks done 34 | - [IA Part A]({{ site.baseurl }}/shared-data/ia-part-a/) and [IA Part B]({{ site.baseurl }}/shared-data/ia-part-b/) generated, approved, and signed by a lot of people. 35 | 2. Documents created 36 | - [IA Part A]({{ site.baseurl }}/shared-data/ia-part-a/) 37 | - [IA Part B]({{ site.baseurl }}/shared-data/ia-part-b/) 38 | - [IX]({{ site.baseurl }}/shared-data/ix/) 39 | 3. Approvals needed 40 | - Everyone in the "who is involved" section 41 | 42 | ### What can go wrong in this stage? 43 | Historically, so, so, so many things. Theoretically, the process as is written above should be smoother now. If you start this process ASAP, you should have time to get all this done. 44 | 45 | ### What is the next step? 46 | Solicitation Scoping 47 | 48 | 49 | -------------------------------------------------------------------------------- /_pages/internal-clients/intake.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Internal Client Intake 3 | --- 4 | ### What happens in this stage? 5 | Someone else in TTS says "We have something we need to buy!" Unlike external buys where Acqstack can decide the client or project is not a good fit and choose to pass on the work, we must be involved in all buys TTS performs. 6 | 7 | Someone tells the [Director of TTS Acquisitions]({{ site.baseurl }}/shared-data/tts-acq-director/) or [Deputy Director of TTS Acquisitions]({{ site.baseurl }}/shared-data/tts-acq-dep-director/) they need something in person, over email, or slack in a DM, in #acquisition, or somewhere else. There is no standard place or way to request assistance at this time. #acq-wg-inception is working on improving this. 8 | 9 | Things can come up in a number of ways: 10 | 11 | - Surprise fires, such as a contract expired without those using it realizing it was going to. 12 | - Parties outside of our control (for example, OGC) decide a contract cannot continue, or options cannot be used, and a new contract must be put in place. 13 | - Pre-planned, well thought out requirements from a program office. 14 | - One contract is ending, but there is money left. 15 | 16 | Because we are required to assist in all internal TTS buys, there has been a reoccuring issue of how involved we get in answering the question "Is this the right thing to buy, and is the client ready to buy this?" 17 | 18 | In some ways, we have less control than with external clients. That help is obstensibly why they hired us, and if the external client is committed to doing something we think is harmful, we have the ability to walk away. But in other ways, we have more control with internal clients. Ideally, we have more awareness about what our fellow TTS program offices are working on, and have more ability to get involved earlier in the procurement strategy and requirements definition process. 19 | 20 | ### How long does this process usually take? 21 | Unknown. 22 | 23 | ### Who is involved in this stage?? 24 | 25 | - [Director of TTS Acquisitions]({{ site.baseurl }}/shared-data/tts-acq-director/) or [Deputy Director of TTS Acquisitions]({{ site.baseurl }}/shared-data/tts-acq-dep-director/) 26 | - Sometimes TTS Agency Partnerships 27 | - Other TTS program office (the client) 28 | 29 | ### What needs to happen to get us out of this stage? 30 | 1. Tasks done 31 | * Established client point of contact 32 | * Verbal confirmation budget for TTS and for vendor is available 33 | * A card is created in the Kanban board, links to the [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/), and is moved to "Staging." 34 | 2. Documents created 35 | * [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/) document is filled out. 36 | * Generate an [IA Part A]({{ site.baseurl }}/shared-data/ia-part-a/) and [IA Part B]({{ site.baseurl }}/shared-data/ia-part-b/) for this client from the template. Does not need to be filled out right now to proceed. 37 | * New google drive folder is created in [WHERE SHOULD THIS FOLDER BE?] 38 | 3. Approvals needed 39 | * [Director of TTS Acquisitions]({{ site.baseurl }}/shared-data/tts-acq-director/) or [Deputy Director of TTS Acquisitions]({{ site.baseurl }}/shared-data/tts-acq-dep-director/) 40 | 41 | ### What can go wrong in this stage? 42 | In the past, there has been an expectation that no, or very little, planning or coordination is necessary. Just "here's an email, now lets go go go!" 43 | 44 | ### What is the next step? 45 | The project is staffed! 46 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## 18F Guides Template 2 | 3 | This is a skeleton repo containing the 4 | [CFPB/DOCter](https://github.com/CFPB/DOCter)-based 5 | [Jekyll](http://jekyllrb.com/) template for 6 | [18F Guides](http://18f.github.io/guides/). 7 | 8 | ### Getting started 9 | 10 | #### Installing Ruby 11 | 12 | You will need [Ruby](https://www.ruby-lang.org) ( > version 2.1.5 ). To check 13 | whether it's already installed on a UNIX-like system, open up a terminal 14 | window (e.g. Terminal on OS X) and type `ruby -v` at the command prompt. For 15 | example, you should see something similar to the following: 16 | 17 | ```shell 18 | $ ruby -v 19 | ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14] 20 | ``` 21 | 22 | If the version number is less than 2.1.5, or instead you see something like: 23 | 24 | ```shell 25 | $ ruby -v 26 | -bash: ruby: command not found 27 | ``` 28 | 29 | Then Ruby is not installed, and you should choose one of the installation 30 | methods below. [The "Installing Ruby" page of the official 31 | Ruby language web 32 | site](https://www.ruby-lang.org/en/documentation/installation/) explains how 33 | to do this in a number of ways across many different systems. 34 | 35 | ##### Quickest Ruby install/upgrade for OS X 36 | 37 | On OS X, you can use [Homebrew](http://brew.sh/) to install Ruby in 38 | `/usr/local/bin`, which may require you to update your `$PATH` environment 39 | variable: 40 | 41 | ```shell 42 | $ brew update 43 | $ brew install ruby 44 | ``` 45 | 46 | ##### Optional: using a version manager 47 | 48 | Whether or not Ruby is already installed, we strongly recommend using a Ruby 49 | version manager such as [rbenv](https://github.com/sstephenson/rbenv) or 50 | [rvm](https://rvm.io/) to help ensure that Ruby version upgrades don't mean 51 | all your [gems](https://rubygems.org/) will need to be rebuilt. 52 | 53 | #### Cloning and serving the Guides Template locally 54 | 55 | To create a new guide and serve it locally, where `MY-NEW-GUIDE` is the name 56 | of your new repository: 57 | 58 | ```shell 59 | $ git clone https://github.com/18F/guides-template.git MY-NEW-GUIDE 60 | $ cd MY-NEW-GUIDE 61 | $ ./go serve 62 | ``` 63 | 64 | The `./go` script will check that your Ruby version is supported, install the 65 | [Bundler gem](http://bundler.io/) if it is not yet installed, install all the 66 | gems needed by the template, and launch a running instance on 67 | `http://localhost:4000/`. 68 | 69 | #### Follow the template instructions 70 | 71 | The Guides Template (either [running locally](http://localhost:4000) or the 72 | [published version](https://pages.18f.gov/guides-template/)) will walk you 73 | through the rest of the steps to edit and publish your guide. 74 | 75 | ### Staging version (for 18F team members) 76 | 77 | In addition to the `18f-pages` branch, you can create an `18f-pages-staging` 78 | branch and changes to that branch will be published to 79 | `https://pages-staging.18f.gov/MY-NEW-GUIDE`, which is identical to 80 | `https://pages.18f.gov/` but provides authenticated access. 81 | 82 | ### Public domain 83 | 84 | This project is in the worldwide [public domain](LICENSE.md). As stated in [CONTRIBUTING](CONTRIBUTING.md): 85 | 86 | > 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](https://creativecommons.org/publicdomain/zero/1.0/). 87 | > 88 | > All contributions to this project will be released under the CC0 89 | >dedication. By submitting a pull request, you are agreeing to comply 90 | >with this waiver of copyright interest. 91 | -------------------------------------------------------------------------------- /_pages/backup/github-setup.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: GitHub setup 3 | --- 4 | Work your way through these steps to prepare your GitHub repository: 5 | 6 | - [Create a new local repository.](#create-local-repo) 7 | - [Set up SSH access to GitHub.](#set-up-ssh) 8 | - [Create a new 18F GitHub repository.](#create-18f-repo) 9 | 10 | ### Create a new local repository 11 | 12 | Once you've got the `_config.yml` file up to date, detach your new 13 | guide's history from the template's. Do this by replacing the 14 | original local Git repository — the one your guide inherited — from the template with a 15 | completely new local repository, which won't contain the history from the 16 | template and will become the starting point for your new GitHub repository. 17 | 18 | In the top-level directory, run `./go create_repo` to remove all the pages 19 | and images that came with this template — make sure you didn't reuse any of the 20 | file names from this template! — and create a new Git repository: 21 | 22 | ``` 23 | $ ./go create_repo 24 | 25 | Clearing Guides Template files. 26 | Removing `:create_repo` command from the `./go` script. 27 | Removing old git repository. 28 | Creating a new git repository. 29 | Initialized empty Git repository in .../MY-NEW-GUIDE/.git/ 30 | Creating 18f-pages branch. 31 | Switched to a new branch '18f-pages' 32 | Adding files for initial commit. 33 | All done! Run 'git commit' to create your first commit. 34 | ``` 35 | 36 | Then execute `git commit -m 'Initial commit'` to create your new Guide! 37 | (Unless you're Git savvy and would like to tweak things a bit first.) 38 | 39 | ### Set up SSH access to GitHub 40 | 41 | You may want to [set up SSH access to 42 | GitHub](https://help.github.com/articles/generating-ssh-keys/) if you haven't 43 | already— this way you won't need to enter your password and two-factor authentication 44 | code every time you push changes to GitHub. Otherwise, you can use 45 | `https://github.com/18F/` URLs to access 18F repos. 46 | 47 | ### Create a new 18F GitHub repository 48 | 49 | Now you're ready to [create a new 18F GitHub 50 | repository](https://github.com/organizations/18F/repositories/new). You'll 51 | want to set the `Public` attribute under the **Team** section and add a 52 | fitting `Description`. 53 | 54 | Do _not_ select **Initialize this repository with a README**, **Add 55 | .gitignore**, or **Add a license**. Instead, update the `README.md` file in 56 | your own, local repository, as necessary. Your local repository also already has 57 | `.gitignore` and `LICENSE.md` files. 58 | 59 | After submitting the form to create a new repository, you'll see GitHub's 60 | instructions to create a local repository and push your changes up to it. You can ignore these instructions. Instead, do the following, replacing `MY-NEW-GUIDE` with the name of your guide's repository: 61 | 62 | ``` 63 | # If you have SSH set up: 64 | $ git remote add origin git@github.com:18F/MY-NEW-GUIDE.git 65 | 66 | # Otherwise: 67 | $ git remote add origin https://github.com/18F/MY-NEW-GUIDE.git 68 | 69 | $ git push -u origin 18f-pages 70 | ``` 71 | 72 | Note that you can update the description and add a website link to the 73 | repository after creating it: 74 | 75 | Setting the 76 | description and website of the GitHub repository 77 | 78 | ### Next steps 79 | 80 | Once you've finished the steps to create your new guide repo and push it 81 | to GitHub, click the _Post Your Guide_ entry in the table of contents for the 82 | final steps to publish your guide. 83 | -------------------------------------------------------------------------------- /_pages/backup/post-your-guide.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Post your guide 3 | --- 4 | Work your way through these steps to set up automated publishing to [18F 5 | Pages](https://pages.18f.gov/) for your new guide: 6 | 7 | - [Create the `18f-pages` branch.](#create-18f-pages-branch) 8 | - [Set the default branch.](#set-default-branch) 9 | - [Create the publishing webhook.](#set-webhook) 10 | - [Trigger a build.](#trigger-a-build) 11 | - [Add the new guide to 18F Guides.](#add-new-guide) 12 | 13 | ### Create the `18f-pages` branch 14 | 15 | **If you ran the `./go create_repo` command from the _GitHub setup_ chapter, 16 | you can skip ahead to the [Create the publishing webhook](#set-webhook) 17 | section. Otherwise, keep reading.** 18 | 19 | To publish your guide automatically to `pages.18f.gov`, you'll need 20 | to create an `18f-pages` branch. You can do this using the GitHub interface by 21 | clicking the **branch: master** button and entering `18f-pages` in the **Switch 22 | branches/tags** drop-down box: 23 | 24 | GitHub branch creation 25 | interface 26 | 27 | ### Set the default branch 28 | 29 | _Note: If your repository is not just a Jekyll site — for example, if it's a project 30 | repository with a `gh-pages` or `18f-pages` branch for documentation — you can 31 | ignore this step._ 32 | 33 | You also need to set `18f-pages` branch as the default. First, click the **Settings** page button on the right side of the screen:
34 | GitHub settings page button 35 | 36 | This will present you with the **Options** page. In the **Settings** section, select `18f-pages` from the **Default branch** drop-down menu:
37 | GitHub default branch option 38 | 39 | Deleting the original `master` branch, both on GitHub and locally, is left as 40 | an exercise for the reader. Doing so will help avoid confusion in the long run 41 | but isn't strictly necessary. 42 | 43 | ### Create the publishing webhook 44 | 45 | **18F Team members can skip this step!** Our pages are now building via an 46 | organization-wide GitHub webhook. There is no need to set up a repo-specific 47 | webhook anymore. 48 | 49 | **Other users running their own [18F/pages](https://github.com/18F/pages/) 50 | instance:** You can either set up a webhook for your organization, or you can 51 | add it per-repository as described below. The steps are nearly identical in 52 | either case. 53 | 54 | Go into the **Webhooks & Services** section of the **Settings** section 55 | and click the **Add webhook** button. On the following screen, set the 56 | **Payload URL** to `https://pages.18f.gov/deploy`, leave the **Secret** field 57 | blank, and click **Update webhook**: 58 | 59 | Set the GitHub webhook 60 | 61 | ### Trigger a build 62 | 63 | With the webhook in place, push any update to your `18f-pages` branch to your 64 | GitHub repository. Within seconds, your guide should appear at 65 | `https://pages.18f.gov/MY-NEW-GUIDE`. Your guide is now live! 66 | 67 | ### Add the new guide to 18F Guides 68 | 69 | You've reached the final step! Add an entry to the `navigation:` list of [18F 70 | Guides](http://18f.github.io/guides/) linking to your new guide. You can [use 71 | this link to edit the file directly in 72 | GitHub](https://github.com/18F/guides/edit/18f-pages/_config.yml): 73 | 74 | Add the new guide to 18F Guides using the GitHub text editor 75 | 76 | Congratulations! Your guide should now be published and accessible to the world 77 | as one of the few, the proud, the [18F Guides](https://pages.18f.gov/guides/)! 78 | -------------------------------------------------------------------------------- /_pages/external-clients/drafting.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Solicitation Drafting 3 | --- 4 | 5 | ### What happens in this stage? 6 | This is where the magic happens: drafting of the solicitation documents! Typically the TTS CO will take point on writing these, but they'll be aided by the tech lead and the product lead. 7 | 8 | The program office should be involved in reviewing these documents as they're written. This will reduce review times later on and makes sure they're on board with the direction we're heading. 9 | 10 | We typically write these documents in Google Docs to facilitate easy collaboration and sharing. 11 | 12 | These five documents must be created before the next stage, assigning a Contracting Officer from NCR. Once these documents are done, email them to the NCR PM and cc the Director and Deputy Director of Acquisitions. Update the Trello card to reflect the initial package has been shipped. 13 | 14 | - [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/) 15 | - [Performance Work Statement (PWS)]({{ site.baseurl }}/shared-data/pws/) 16 | - [Independent Government Cost Estimate (IGCE)]({{ site.baseurl }}/shared-data/igce/) 17 | - [Market Research]({{ site.baseurl }}/shared-data/market-research/) 18 | - [Evaluation Criteria]({{ site.baseurl }}/shared-data/eval-criteria/) 19 | 20 | These are the documents that must be created, but can be created after we have an assigned CO from NCR: 21 | 22 | - [Quality Assurance Surveillance Plan (QASP)]({{ site.baseurl }}/shared-data/qasp/) 23 | - [Acquisition Plan]({{ site.baseurl }}/shared-data/acquisition-plan/) 24 | - [Any justifications that are needed]({{ site.baseurl }}/shared-data/justifications/) 25 | - [Proposal Template]({{ site.baseurl }}/shared-data/proposal-template/) 26 | - [The RF(x) itself]({{ site.baseurl }}/shared-data/rfx/) 27 | 28 | While the CO is writing solicitation documents, the PM should focus on getting the [IX]({{ site.baseurl }}/shared-data/ix/) completed by the TTS Finance team before we can move forward. 29 | 30 | ### How long does this process usually take? 31 | A few days to a week or two to create the documents. A few weeks to a few months depending on client reviews. 32 | 33 | ### Who is involved in this stage? 34 | 35 | - TTS CO 36 | - TTS Product Lead 37 | - TTS Technical Lead 38 | - Client product owner 39 | 40 | ### What needs to happen to get us out of this stage? 41 | 1. Tasks done 42 | - Clients have reviewed the documents and given the go ahead to continue. 43 | - [IX]({{ site.baseurl }}/shared-data/ix/) is generated and submitted to NCR. 44 | 2. Documents created 45 | - [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/) 46 | - [Performance Work Statement (PWS)]({{ site.baseurl }}/shared-data/pws/) 47 | - [Independent Government Cost Estimate (IGCE)]({{ site.baseurl }}/shared-data/igce/) 48 | - [Market Research]({{ site.baseurl }}/shared-data/market-research/) 49 | - [Evaluation Criteria]({{ site.baseurl }}/shared-data/eval-criteria/) 50 | - [IX]({{ site.baseurl }}/shared-data/ix/) 51 | 52 | 3. Approvals needed 53 | - Initial client approval of solicitation documents. 54 | - IX approved by OCFO and TTS Finance 55 | - IA part A and B signed and approved by, in the folllowing order: 56 | - [TTS OGC]({{ site.baseurl }}/shared-data/tts-ogc/) 57 | - [NCR OGC]({{ site.baseurl }}/shared-data/ncr-ogc/) 58 | - [TTS OCFO]({{ site.baseurl }}/shared-data/tts-ocfo/) 59 | - [TTS Assistant Commissioner]({{ site.baseurl }}/shared-data/tts-assistant-commissioner/) for that program office 60 | - FAS/NCR OCFO certifying official (unclear what or who this is???) 61 | - [NCR Commissioner]({{ site.baseurl }}/shared-data/ncr-commissioner/) 62 | 63 | 64 | ### What can go wrong in this stage? 65 | There are a lot of approvals to get just to start work. Expect unexpected delays. 66 | 67 | Client approval of documents is something we have no control over, and is a significant watchpoint. 68 | 69 | You should also over-communicate to the client how the work will be done (open source, agile, etc), and get clear buy-in from all releavnt stakeholders. It is very easy to not do enough here, then be met with resistance later on when stakeholders realize what's happening. 70 | 71 | ### What is the next step? 72 | NCR Contracting Officer and Contracting Specialist are assigned. 73 | 74 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | markdown: redcarpet 2 | name: 18F Guides Template 3 | exclude: 4 | - CONTRIBUTING.md 5 | - Gemfile 6 | - Gemfile.lock 7 | - LICENSE.md 8 | - README.md 9 | - go 10 | - vendor 11 | 12 | permalink: pretty 13 | highlighter: rouge 14 | incremental: true 15 | 16 | sass: 17 | style: :compressed 18 | 19 | # Author/Organization info to be displayed in the templates 20 | author: 21 | name: 18F 22 | url: https://18f.gsa.gov 23 | 24 | # Point the logo URL at a file in your repo or hosted elsewhere by your organization 25 | logourl: /assets/img/18f-logo.png 26 | logoalt: 18F logo 27 | 28 | # To expand all navigation bar entries by default, set this property to true: 29 | expand_nav: true 30 | 31 | # Navigation 32 | # List links that should appear in the site sidebar here 33 | navigation: 34 | - text: Acqstack Journeymap 35 | internal: true 36 | - text: External Clients 37 | url: external-clients/ 38 | internal: true 39 | children: 40 | - text: Biz Dev 41 | url: bizdev/ 42 | internal: true 43 | - text: Intake 44 | url: intake/ 45 | internal: true 46 | - text: Agreements 47 | url: agreements/ 48 | internal: true 49 | - text: Staffing 50 | url: staffing/ 51 | internal: true 52 | - text: Onboarding 53 | url: onboarding/ 54 | internal: true 55 | - text: Solicitation Scoping 56 | url: solicitation-scoping/ 57 | internal: true 58 | - text: Solictation Drafting 59 | url: drafting/ 60 | internal: true 61 | - text: CO Team Assigned 62 | url: co-team-assigned/ 63 | internal: true 64 | - text: Acquisition Package Review 65 | url: acq-package-review/ 66 | internal: true 67 | - text: Releasing RFP 68 | url: release-rfp/ 69 | internal: true 70 | - text: Question and Answers 71 | url: qa/ 72 | internal: true 73 | - text: Proposals 74 | url: proposals/ 75 | internal: true 76 | - text: Evaluation 77 | url: evaluation/ 78 | internal: true 79 | - text: Award 80 | url: award/ 81 | internal: true 82 | - text: Internal Clients 83 | url: internal-clients/ 84 | internal: true 85 | children: 86 | - text: Intake 87 | url: intake/ 88 | internal: true 89 | - text: Staffing 90 | url: staffing/ 91 | internal: true 92 | - text: Onboarding 93 | url: onboarding/ 94 | internal: true 95 | - text: Agreements 96 | url: agreements/ 97 | internal: true 98 | - text: Solicitation Scoping 99 | url: solicitation-scoping/ 100 | internal: true 101 | - text: Infrastructure Review 102 | url: infrastructure-review/ 103 | internal: true 104 | - text: Solictation Drafting 105 | url: drafting/ 106 | internal: true 107 | - text: CO Team Assigned 108 | url: co-team-assigned/ 109 | internal: true 110 | - text: Acquisition Package Review 111 | url: acq-package-review/ 112 | internal: true 113 | - text: Releasing RFP 114 | url: release-rfp/ 115 | internal: true 116 | - text: Question and Answers 117 | url: qa/ 118 | internal: true 119 | - text: Proposals 120 | url: proposals/ 121 | internal: true 122 | - text: Evaluation 123 | url: evaluation/ 124 | internal: true 125 | - text: Award 126 | url: award/ 127 | internal: true 128 | 129 | repos: 130 | - name: Acqstack Journeymap 131 | description: acqstack journeymap 132 | url: https://github.com/18F/acqstack-journeymap 133 | 134 | back_link: 135 | url: "https://pages.18f.gov/guides/" 136 | text: Read more 18F Guides 137 | 138 | google_analytics_ua: UA-48605964-19 139 | 140 | collections: 141 | pages: 142 | output: true 143 | permalink: /:path/ 144 | 145 | defaults: 146 | - scope: 147 | path: "" 148 | values: 149 | layout: "guides_style_18f_default" 150 | 151 | # Configuration for jekyll_pages_api_search plugin gem. 152 | jekyll_pages_api_search: 153 | # Uncomment this to speed up site generation while developing. 154 | #skip_index: true 155 | 156 | # Each member of `index_fields` should correspond to a field generated by 157 | # the jekyll_pages_api. It can hold an optional `boost` member as a signal 158 | # to Lunr.js to weight the field more highly (default is 1). 159 | index_fields: 160 | title: 161 | boost: 10 162 | tags: 163 | boost: 10 164 | url: 165 | boost: 5 166 | body: 167 | -------------------------------------------------------------------------------- /_pages/backup/update-the-config-file.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Update the config file 3 | --- 4 | Work your way through these steps to update 5 | the `_config.yml` file — this configures the 18F style template for your specific guide: 6 | 7 | - [Set the guide name.](#set-name) 8 | - [Add defaults and collections.](#add-defaults-and-collections) 9 | - [Set the `exclude:` entries.](#set-exclude-entries) 10 | - [Register pages in the navigation bar.](#register-pages-in-nav-bar) 11 | - [Update the repository list.](#update-repository-list) 12 | - [Optional: Set the `back_link:` property.](#set-back-link) 13 | - [Optional: Update `google_analytics_ua:`.](#set-google-analytics) 14 | 15 | ### Set the guide name 16 | 17 | The `name:` property appears as the guide's overall title. For example: 18 | 19 | ```yaml 20 | name: {{site.name}} 21 | ``` 22 | 23 | ### Add defaults and collections 24 | 25 | We often use simple Markdown pages. 26 | 27 | ```yaml 28 | defaults: 29 | - 30 | scope: 31 | path: "" 32 | type: "pages" 33 | values: 34 | layout: "page" 35 | 36 | collections: 37 | pages: 38 | output: true 39 | permalink: /:path/ 40 | ``` 41 | 42 | The `name:` property appears as the guide's overall title. For example: 43 | 44 | ```yaml 45 | name: {{site.name}} 46 | ``` 47 | 48 | ### Set the `exclude:` entries 49 | 50 | Make sure the `exclude:` list contains at least the following files, and add 51 | any other files you might have added that shouldn't appear in the 52 | generated `_site` directory: 53 | 54 | ```yaml 55 | exclude: 56 | {% for i in site.exclude %}- {{ i }} 57 | {% endfor %}``` 58 | 59 | ### Register pages in the navigation bar 60 | 61 | The `navigation:` list generates the table of contents. For example, 62 | the `navigation:` section of this guide contains: 63 | 64 | ```yaml 65 | navigation: 66 | {% for i in site.navigation %}- text: {{ i.text }}{% if i.url %} 67 | url: {{ i.url }}{% endif %} 68 | internal: {{ i.internal }}{% if i.children %} 69 | children:{% for child in i.children %} 70 | - text: {{ child.text }} 71 | url: {{ child.url }} 72 | internal: {{ child.internal }}{% endfor %}{% endif %} 73 | {% endfor %}``` 74 | 75 | After you add pages, move pages, or make changes to `title:` or `permalink:`, 76 | run `./go update_nav` from the root directory to produce this list (it will 77 | reflect the arrangement and contents of the files in your pages directory). 78 | After running the script, you may edit the results by hand to produce the 79 | desired ordering of any new pages; the order of existing entries will remain 80 | the same. 81 | 82 | ### Update the repository list 83 | 84 | You'll need to update the `repos:` list to reflect the GitHub 85 | repository that will contain your guide. The first of these repositories 86 | should be the repository for the guide itself; it will be used to generate 87 | the _Edit this page_ and _file an issue_ links in the footer. 88 | 89 | The `url:` should be `https://github.com/18F/MY-NEW-GUIDE`, where 90 | `MY-NEW-GUIDE` is the name you gave your clone of the 18F/guides-template 91 | repository. For the `description:` property, it's OK to enter something 92 | generic like "main repository." However, if you aren't certain about either 93 | value, it's also OK to enter placeholder text for these properties and change 94 | them later, ideally before posting to the 18F Pages server. 95 | 96 | The `repos:` entry of this template contains: 97 | 98 | ```yaml 99 | repos:{% for i in site.repos %} 100 | - name: {{ i.name }} 101 | description: {{ i.description }} 102 | url: {{ i.url }} 103 | {% endfor %} 104 | ``` 105 | 106 | ### Optional: set the `back_link:` property 107 | 108 | The `back_link:` property produces the _Read more 18F Guides_ link just under 109 | the title of the guide at the top of the page. If your document is not 110 | actually an 18F Guide, you may change this property to link to 18F Pages— or 111 | any other collection of documents to which your new "guide" actually belongs. 112 | 113 | ### Optional: update `google_analytics_ua:` 114 | 115 | The `google_analytics_ua:` property defaults to the Google Analytics account 116 | identifier for all 18F Pages sites. You can override it if you prefer. 117 | 118 | ### Next steps 119 | 120 | Once you're finished updating the config file, click the _GitHub Setup_ 121 | entry in the table of contents. 122 | -------------------------------------------------------------------------------- /_pages/internal-clients/drafting.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Solicitation Drafting 3 | --- 4 | 5 | ### What happens in this stage? 6 | This is where the magic happens: drafting of the solicitation documents! Typically the TTS CO will take point on writing these, but they'll be aided by the tech lead and the product lead. 7 | 8 | The program office should be involved in reviewing these documents as they're written. This will reduce review times later on and makes sure they're on board with the direction we're heading. 9 | 10 | We typically write these documents in Google Docs to facilitate easy collaboration and sharing. 11 | 12 | These are the documents that must be created before we can move forward to the next stage, assigning a Contracting Officer from NCR: 13 | 14 | - [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/) 15 | - [Performance Work Statement (PWS)]({{ site.baseurl }}/shared-data/pws/) 16 | - [Independent Government Cost Estimate (IGCE)]({{ site.baseurl }}/shared-data/igce/) 17 | - [Market Research]({{ site.baseurl }}/shared-data/market-research/) 18 | - [Evaluation Criteria]({{ site.baseurl }}/shared-data/eval-criteria/) 19 | 20 | These are the documents that must be created, but can be created after we have an assigned CO from NCR: 21 | 22 | - [Quality Assurance Surveillance Plan (QASP)]({{ site.baseurl }}/shared-data/qasp/) 23 | - [Acquisition Plan]({{ site.baseurl }}/shared-data/acquisition-plan/) 24 | - [Any justifications that are needed]({{ site.baseurl }}/shared-data/justifications/) 25 | - [Proposal Template]({{ site.baseurl }}/shared-data/proposal-template/) 26 | - [The RF(x) itself]({{ site.baseurl }}/shared-data/rfx/) 27 | 28 | While the CO is writing solicitation documents, the PM has a few things to take care of before you can move forward. 29 | 30 | 1. The [IX]({{ site.baseurl }}/shared-data/ix/) also needs to be completed by the TTS Finance team before we can move forward. The PM usually takes care of getting this done. 31 | 2. Make sure the [IA]({{ site.baseurl }}/shared-data/ia/) [Part A]({{ site.baseurl }}/shared-data/ia-part-a/) and [Part B]({{ site.baseurl }}/shared-data/ia-part-b/) between TTS and NCR is done and signed. 32 | 33 | ### How long does this process usually take? 34 | A few days to a week or two to create the documents. A few weeks to a few months depending on client reviews. 35 | 36 | ### Who is involved in this stage? 37 | 38 | - TTS CO 39 | - TTS Product Lead 40 | - TTS Technical Lead 41 | - Client product owner 42 | 43 | ### What needs to happen to get us out of this stage? 44 | 1. Tasks done 45 | - Clients have reviewed the documents and given the go ahead to continue. 46 | - [IX]({{ site.baseurl }}/shared-data/ix/) is generated and submitted to NCR. 47 | 2. Documents created 48 | - [Executive Summary]({{ site.baseurl }}/shared-data/executive-summary/) 49 | - [Performance Work Statement (PWS)]({{ site.baseurl }}/shared-data/pws/) 50 | - [Independent Government Cost Estimate (IGCE)]({{ site.baseurl }}/shared-data/igce/) 51 | - [Market Research]({{ site.baseurl }}/shared-data/market-research/) 52 | - [Evaluation Criteria]({{ site.baseurl }}/shared-data/eval-criteria/) 53 | - [IX]({{ site.baseurl }}/shared-data/ix/) 54 | 55 | 3. Approvals needed 56 | - Initial client approval of solicitation documents. 57 | - IX approved by OCFO and TTS Finance 58 | - IA part A and B signed and approved by, in the folllowing order: 59 | - [TTS OGC]({{ site.baseurl }}/shared-data/tts-ogc/) 60 | - [NCR OGC]({{ site.baseurl }}/shared-data/ncr-ogc/) 61 | - [TTS OCFO]({{ site.baseurl }}/shared-data/tts-ocfo/) 62 | - [TTS Assistant Commissioner]({{ site.baseurl }}/shared-data/tts-assistant-commissioner/) for that program office 63 | - FAS/NCR OCFO certifying official (unclear what or who this is???) 64 | - [NCR Commissioner]({{ site.baseurl }}/shared-data/ncr-commissioner/) 65 | 66 | 67 | ### What can go wrong in this stage? 68 | The IA Part A and B and the IX documents have historically been difficult to get signed in a timely manner without significant effort. NCR OGC requires a very specific format, but that format does not always apply or contain all the necessary information. Efforts are underway to address this. 69 | 70 | There are a lot of approvals to get just to start work. Expect unexpected delays. 71 | 72 | Client approval of documents is something we have no control over, and is a significant watchpoint. 73 | 74 | You should also over-communicate to the client how the work will be done (open source, agile, etc), and get clear buy-in from all releavnt stakeholders. It is very easy to not do enough here, then be met with resistance later on when stakeholders realize what's happening. 75 | 76 | ### What is the next step? 77 | NCR Contracting Officer and Contracting Specialist are assigned. 78 | 79 | -------------------------------------------------------------------------------- /_pages/backup/advanced-features.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Advanced features 3 | --- 4 | These features are not necessary to produce a guide, but are available if you 5 | need them. 6 | 7 | ### Checking the build log 8 | 9 | If your site did not rebuild after pushing an update, see the latest build log 10 | at `https://pages.18f.gov/MY-SITE/build.log`, where `MY-SITE` is the name of 11 | your Guide's repository. For example, the latest build log for this site is 12 | [`https://pages.18f.gov/guides-template/build.log`](https://pages.18f.gov/guides-template/build.log). 13 | 14 | ### Server-generated defaults 15 | 16 | The [18F Pages Server](https://www.npmjs.com/package/18f-pages-server) will 17 | generate an additional configuration file, `_config_18f_pages.yml`, that will 18 | contain the following configuration values: 19 | 20 | * **baseurl:** This sets `{% raw %}{{ site.baseurl }}{% endraw %}` to the 21 | repository name without the organization prefix, e.g. `/guides-template` 22 | for the `18F/guides-template` repo, resulting in 23 | `https://pages.18f.gov/guides-template/`. See the 24 | [Understanding the `baseurl:` property](/update-the-config-file/understanding-baseurl/) 25 | section for details. 26 | * **asset_root:** This sets the location from which the guide will load its 27 | CSS and JavaScript assets. 28 | 29 | ### Understanding `asset_root` 30 | 31 | When developing locally, this value is empty, so your assets are loaded from 32 | your local instance. When hosted on `https://pages.18f.gov/`, this value is 33 | set as `/guides-template`. This allows all pages on the host that use this 34 | style template to receive CSS and JavaScript updates automatically whenever 35 | `https://pages.18f.gov/guides-template` is updated. 36 | 37 | ### Overriding server-generated defaults 38 | 39 | If you _really_ want, you can prevent the 18F Pages server from generating its 40 | own configuration by adding a `_config_18f_pages.yml` file to your site. The 41 | 18F Pages server will use that file instead of generating its own. 42 | 43 | ### Additional scripts and styles 44 | 45 | If you'd like to add additional scripts or styles to every page on the site, 46 | you can add `styles:` and `scripts:` lists to `_config.yml`. To add them to a 47 | particular page, add these lists to the page's front matter. 48 | 49 | ### Overriding the theme's built-in styles 50 | 51 | To override the built-in styles, create a new file in `assets/css` and add it 52 | to the `scripts:` list in `_config.yml`. 53 | 54 | However, consider sending a pull request to update the contents of 55 | [`lib/guides_style_18f/sass/`](https://github.com/18F/guides-style/tree/master/lib/guides_style_18f/sass) 56 | if your changes may be beneficial to all 18F-themed sites. 57 | 58 | ### Experimenting with the `guides_style_18f` gem 59 | 60 | To try out changes to the common 18F theme, clone the [18F/guides-style 61 | repository](https://github.com/18F/guides-style/) into the same parent 62 | directory as your guide. Then update your `Gemfile` to point 63 | `guides_style_18f` to this clone: 64 | 65 | ```yaml 66 | group :jekyll_plugins do 67 | gem 'guides_style_18f', path: '../guides-style' 68 | end 69 | ``` 70 | 71 | Then run `bundle install` and `./go serve` to begin using the local version of 72 | `guides_style_18f`. Any changes within your `guides-style` clone will appear 73 | in your locally-hosted guide upon reload. 74 | 75 | ### Publishing to internal sites 76 | 77 | There are several 18F Pages hosts that require OAuth2 authentication to 78 | access. To publish to one of these hosts, push changes to the following 79 | branches: 80 | 81 | - **`18f-pages-staging`**: publishes to `https://pages-staging.18f.gov/` 82 | - **`18f-pages-internal`**: publishes to `https://pages-internal.18f.gov/` 83 | - **`18f-pages-dev`**: publishes to `https://pages-dev.18f.gov/` 84 | 85 | There is one other internal host, `https://pages-releases.18f.gov/`, which 86 | does something special. If you publish to a branch matching the pattern 87 | `v[0-9]+.[0-9]+.[0-9]*[a-z]+`, your site will appear on this host with 88 | `baseurl` set to `REPOSITORY/BRANCH`. For example, pushing to a branch called 89 | `v0.9.x` within `18F/guides-template` would publish 90 | `https://pages-releases.18f.gov/guides-template/v0.9.x`. 91 | 92 | ### Publishing to internal and external sites from the same branch 93 | 94 | By adding an optional `_config_internal.yml` file to your guide, your site 95 | will appear at `https://pages-internal.18f.gov/` as well as 96 | `https://pages.18f.gov`. If the contents of this file contain: 97 | 98 | ```yaml 99 | internal: true 100 | ``` 101 | 102 | then you can ensure that sections formatted with the following markup only appear on 103 | `pages-internal.18f.gov`, and are stripped out of the public-facing 104 | `pages.18f.gov`: 105 | 106 | 
107 | {% raw %}{% if site.internal %}TEXT TO BE REDACTED FROM PUBLIC PRODUCTION + STAGING{% endif %}{% endraw %}
108 |
109 | 110 | For more details, see the [`18f-pages-server` 111 | README](https://github.com/18F/pages-server#publishing-to-internal-and-external-sites-from-the-same-branch). 112 | --------------------------------------------------------------------------------