While gettings @jseppi up to speed, we noticed that a few instructions are missing from the guide on running Federalist locally

• Instructions on setting up the databases
• Instructions to run npm run build before npm start

• The main Federalist template builds pages using layouts with pre-made headers and footers, all created with HTML. These templates cannot be edited though the Federalist editor and must be modified by someone with knowledge of HTML.
• Some of the text on pages is adjusted using the front matter, not the text editing interface.
• Pages have titles, filenames, and names in the menu, which can all be configured separately.
• Files should be uploaded on different branches than those creating links to the files.
• Uploading files in bulk works best using a GitHub client that syncs between your local machine and GitHub

After cloud-gov/pages-core#987 is merged, federalist admins/devs will be able to add a sitewide error message. There should be docs on how to do this.

https://docs.google.com/document/d/1CNGxMVN_2asGWFfLfMLcAlMH0vUdn02ckCZqCRa9Hps/edit#

I was trying to spin up a new site on federalist today and couldn't figure out how to use one of the provided templates and also connect it to a repo in the 18F org.

Will Slack provided the answer (use the "Use this template/Create this site" button which creates a repo in your personal github account, move your repo from your personal account to the 18F org, delete the site off Federalist, re-add it using the "Or add your own Github repository" option).

It would be great if this workflow was included in the federalist support docs somewhere

• Edit docs site to have this information.

Cost of an ATO for a website: 95K
Cost of an ATO with a pentest: 135K

Per cloud-gov/pages-core#978, when we don't have TTL set in cloudfront, cloudfront caching causes application problems. We should add instructions on how to set the caching. (knowing these instructions are very AWS specific)

Per 18F/docker-ruby-ubuntu#7, people can now select their own Ruby version. We need to document how this is done.

Description

The image under the heading "Landing Page for Information about a Released Report" is not displaying.

Steps to reproduce the issue

1. Go here: https://federalist-docs.18f.gov/pages/using-federalist/#federalist-templates
2. Scroll to the second template.

Additional information [optional]

Screen shot:

Build containers should be launched with 1G memory and 2G disk space.

Per https://docs.google.com/document/d/1wG2tbJJ9u26nDRAlTnyvruTScTMHsGV5pykXzBHN_aU/edit#

Need link to https://search.digitalgov.gov/ and instructions.

I'd like to incorporate the USWDS into a federalist Jekyll site but have not found any documentation on how to do this.

It still references 18f-pages, for example.

Hey! The methods cards are in Federalist now - might be a good candidate for your list of examples.

homepage screenshot:

This page is old and unclear

The Custom Templates section seems to say it's possible to make custom templates, but how one would do such a thing is hard to understand. Would be nice to make it clear for users who want to go away from the provided templates what the path looks like should they choose to make (1) simply static content, (2) jekyll-built sites, or (3) hugo-built sites.

The break for https://federalist-docs.18f.gov/ to switch to a tablet layout seems too wide. If the window is even slightly narrower that full screen on my laptop, the side nav drops to the bottom of the page, which hides a lot of the page content.

This fix is above my technical level, but it seems like the break happens much earlier than on other 18F sites.

I didn't find this noted anywhere. A good place to put it is probably the "Adding a new site" section of "Using Federalist."

I personally am often frustrated by not being able to search our docs website. I often resort to using my code editor's find functionality to search my local clone of this repo. Integrating search in the site itself would be really nice.

I'm not very familiar with the landscape, but I think some options are:

• Digital.gov search (ref https://github.com/18F/federalist-docs/issues/85)
  • This seems like a pretty nice option to me
  • further notes: https://docs.google.com/document/d/1wG2tbJJ9u26nDRAlTnyvruTScTMHsGV5pykXzBHN_aU/edit#
• Some kind of jekyll-lunr.js integration

it seems like the line length control is inconsistent between standard text and lists or bullets: https://federalist.18f.gov/preview/18f/federalist-docs/uswds/pages/using-federalist/launch-checklist/

change single page template and multi page template to landing page template and modern team template.

This will make the names the same as on federalist - create a site page as well as the github repos

Done in https://github.com/18F/federalist-docs/pull/116

Now experimental support of hugo has landed in federalist-staging, and will soon be in production, we should update the docs here to include relevant information about using hugo with federalist.

This came up with @konklone's recent problem while trying to add a repo from the uspki org.

Basic steps to make it work:

1. Owner/admin of org goes to their Settings > Authorized OAuth Apps and selects "Federalist (GovCloud)" from the list of apps.
2. On that page, they will see a list of apps under the "Organization access" heading. They will need to click the "Grant" button next to the org:

I can't find where in the code/data this is set to file a PR for, but the "Edit this page" link, on the bottom of pages like this one, is broken:

https://federalist-docs.18f.gov/pages/using-federalist/customer-responsibilities/

It links to https://github.com/18F/federalist-docs/edit/18f-pages/pages/using-federalist/customer-responsibilities.md, but the correct link replaces 18f-pages with master.

Also, the text in the footer says "Hosted on 18F Pages", which is now incorrect.

@shawnbot, what do you think about upgrading to the guides_style gem on display here?

@shawnbot, where do I go for documentation on how to get items into the mobile/topbar menus for the site now?

This is a reminder that we should document how cloud-gov/pages-build-container#13 works once the feature has been deployed to the production environment. It would be good to point at some working examples. @wslack has suggested that we put it on the using Federalist page.

https://federalist-docs.18f.gov/pages/included-with-federalist/ gives me a 404, which is linked in the opening paragraph of https://federalist-docs.18f.gov/

Apply styling to search.gov results page to match the styling of the Federalist Docs site.

I just checked and it looks like some old builds of Federalist had this issue:

https://federalist-proxy.app.cloud.gov/preview/18f/federalist-docs/update-clair-instructions/pages/using-federalist/instructional-demos/

Not sure when it was introduced or how to make the title text link back to the homepage.

https://github.com/18F/guides-style forces the "edit this page" link at the bottom to point to an incorrect branch and a Hosted on 18F Pages message. We should reconfigure to avoid these issues or stop using the gem.

I think there are three places in code that call this:

• https://github.com/18F/federalist-docs/blob/master/assets/css/styles.scss
• https://github.com/18F/federalist-docs/blob/master/go
• https://github.com/18F/federalist-docs/blob/master/_config.yml

Hello! As @line47 noted over in the 18F Content Guide repo, there is some confusion about the Federalist Content Guide vs. the 18F Content Guide. After some discussion with the content guild, we realized that the "Content guide" within the Federalist docs is actually more about how to use specific templates, rather than general content best practices.

To avoid confusion, we'd like to recommend changing the name of the "Content guide" within the Federalist docs to something else — perhaps "Template guide," "Using the templates," or "Page sections"?

We should add documentation that makes it explicitly clear that users must have 2FA enabled for their GitHub account in order to access Federalist

re: cloud-gov/pages-core#817

https://federalist-docs.18f.gov/pages/about-federalist/example-sites/

We don't write down anywhere instructions about how to merge in code-changes. These should be in federalist-docs in the short term and linked from the repo readmes.

I realized that it'd be nice if my site built using a production configuration when running on Federalist, which made me wonder if NODE_ENV is set to production or anything. If it's not, that's ok--I can just modify my federalist NPM script to e.g. set that environment variable, or something else. But if it does, it'd be nice to document that in the Federalist node docs!

Description of feature or bug

Someone non-technical that wants to "get" Federalist would do better with a very basic diagram of the entire system.

Definition of done

• New diagram is added to the docs repo

After evaluating, edit this part:

Level of effort - low