Migrate federalist marketing and documentation site to cloud.gov

[amirbey]

User Story

A pages user can access user documentation at pages domain.

Background (Optional)

Questions

• [x] What will be the domain? (cloud.gov/pages/documentation)
• [x] Will current docs migrate over to the cloud.gov wide docs template? Yes
• [x] Multiple sites using a shared template? No, one site ~Find a static site generator built for documentation?~ ~Should the docs and marketing be on the same site?~

Acceptance Criteria

• [x] pages is logo is used on marketing site
• [x] pages is logo is used on docs site
• [x] references to Federalist do not exist unless for historical context
• [ ] update pages compliance memo (post SCR) (already drafted)
• [ ] federalist.18f.gov redirect to cloud.gov/pages (post SCR)
• [ ] federalist.18f.gov/documentation redirects to cloud.gov/pages/documentation (post SCR)
• [ ] Change made live via cg-site deploy

After evaluating, edit this part:

Level of effort - High

Implementation outline (if higher than "low" effort):

• [x] copy content from federalist.18f.gov to cloud.gov/pages
• [x] copy content from federalist.18f.gov/documentation to cloud.gov/pages/documentation
• [x] change the logo
• [x] replace "Federalist" text with "Pages"
• [ ] setup redirect from federalist.18f.gov to cloud.gov/pages
• [ ] setup redirect from federalist.18f.gov/documentation to cloud.gov/pages/documentation

[amirbey]

Feedback cloud.gov PM: https://gsa-tts.slack.com/archives/G7EFTFW03/p1631651171004000?thread_ts=1631628452.002400&cid=G7EFTFW03

[amirbey]

• [x] How do we want to handle case studies? They still say Federalist in-line.
• [x] Will the Federalist inquiries email be updated to something like [email protected]?
• [x] Federalist interest form needs to be updated to say Pages
• [ ] How Pages Works System Overview refers to Federalist
• [x] Under "get started", we say that you can use our ATO
• [ ] StatusPages still refers to Federalist (to be updated in statuspage.io settings during migration)
• [x] Documentation-->Why use Pages?: under "compliance out of the box", it refers to Federalist, the system overview - image refers to Federalist
• [x] Using Pages--> Access and permissions: refers to e-mailing [email protected]
• [ ] Using Pages --> Getting started with Jekyl: update screenshots of GH repos with new images once Pages repos are moved to cloud.gov org
• [x] Using Pages --> Included with Pages: depending on the outcome of discussions with GSA IT, this will change. The way it's currently written, it gives the impression that the customer doesn't need to do anything for the ATO.
• [ ] Using Pages --> Instructional Demos: videos need to be updated to reflect Pages
• [ ] Using Pages --> Builds and Previews: screenshots need to be updated to reflect Pages
• [ ] Using Pages --> Custom domains --> configuring your DNS includes a Federalist example
• [ ] Using Pages --> Custom domains --> update your site settings screenshots need to be updated to reflect Pages
• [ ] Before you launch--> launch process--> email and Slack channel will need to be updated to reflect Pages
• [ ] Using Pages --> Federalist.json: navigation needs to be updated to reflect Pges