SPIKE: Research & Design a way to fit the AI Site into the COE AI page

[sstatz]

COE Site Page: https://coe.gsa.gov/coe/artificial-intelligence.html Make a proposal for how to fit the new AI Site here. Run it by Danielle Gallant.
Set your hour limit ahead of time for this proposal.

As a team member, in order to get approval for how the AI guide for government content can fit into the COE AI page, I want to come up with a design and run it by Danielle Gallant & write stories to do the work.

[sknep]

This is a pretty straightforward Jekyll site.

Currently the page is a single markdown file with some yaml here: https://github.com/GSA/centers-of-excellence/blob/master/coe/artificial-intelligence.html

At one time, the AI COE had(?) it's own html layout (although it currently uses the default COE layout): https://github.com/GSA/centers-of-excellence/blob/master/_layouts/coe-ai.html so there's some precedence for AI being 'a little bit extra', though why it's not used now, I couldn't say.

It uses some data files to fill out a nav: https://github.com/GSA/centers-of-excellence/blob/master/_data/coe.yml#L17 which our proposed content won't fit nicely within.

The repo also has a few separate, unlisted, one-page experiences at https://coe.gsa.gov/coe/farm-loans/ and others, which use the site header and footer but page contents custom to the feature. We could put the proposed new AI site content in something like this easily, but the discoverability is the big thing here.

[sknep]

Using the existing Jekyll site and patterns, we should be able to work on a new template with an integrated side-nav that uses USWDS v1 and a new Jekyll Collection for the AI Site content formerly known as the body of knowledge. I pulled an existing template from the repo and put together this example in code locally this morning:

I'd still like to add prev/next links at the bottom of the page but that's trivial.

I wanted to see if the urls (currently things like '/module-3-1') were an artifact of the CMS integration or an intentional choice. We could pull the ordering from the filename itself, but for now I chose to use the existing metadata present on the docs in a bok_section_id field in YAML.

Once we have the content in this jekyll site, we'd still need to figure out discoverability. There's space for a link in the sidebar of the COE AI page. These other mini-experiences have the same problem — they exist at known urls but aren't linked to from the larger site nav (they are referred to from blog posts, but they're still basically unlisted). That could be ok, if we know that folks will be able to find these from other places.

@jonadecker thoughts?

[jonadecker]

💯

• I think the internal nav works well, and prev/next would be a good addition
• Yes to promo area on right rail
• Do we need to create a print style sheet or am I misremembering?
• Recommend getting someone on COE side to write a news item for AI page promoting it
• Maybe (?) recommend getting this added to AI Service Catalog PDF if someone has source document
• Touchpoints form (hosted) for feedback?

[sknep]

Still need to accommodate:

• adding a link to this section from the COE AI right-hand sidebar page via sidebar-extra-content in page YAML
• any design revisions requested by the client
• print styles
• /feedback: "AI Guide in Government is meant to be a living and evolving guide to the application of AI for the U.S. Federal Government. If you have feedback for existing content, or suggestions for additional content, submit via email at tts-ai@gsa.gov." or propose a Qualtrics form, etc
• some weird background image sections in some pages that need love
• The markdown parsers are different so we need to go through each page and make sure the formatting and typesetting are correct, as well as upload any missing images.
• Reformatting the big table to be accessible