Guide post-MVP

[desigonz]

We implemented guides in #2600. Now let's make improvements. Using this issue to compile all the ideas.

• [ ] Minimum required section behavior
• [ ] Download checklist
• [ ] Download application documents
• [ ] Checklists
  • [ ] Bullet style with checkbox
  • [ ] Need to not have to use code to create line breaks
• [ ] Documents section behavior
  • [ ] Lists all the documents that are linked to within the guide. Note that this includes CoA documents that are pointed to within pages, but not documents that are linked to that are not CoA.
  • [ ] Headings correspond to the sections in which the documents originated
  • [ ] ❓Clicking on a document name opens the file in a new tab
  • [ ] ❓(For MVP?? This could be curated by a content editor, so instead include this in style guide/content governance documentation) In the case of duplicate documents (found on one or more pages), the preferred behavior would be to show the document where its first referenced within the guide. We want to avoid duplicating links because that's confusing to users. For example, if an application doc is linked to in Section 1 and then again on a different page in Section 3, then only show that document in Section 1 of Documents, but not again in Section 3.

[desigonz]

From #1871: The guide type has a couple of proposed new features: Joplin

• [ ] ability to add a checklist (component type?) Janis
• [ ] print one or all
• [ ] local favoriting

More details to come.

[desigonz]

See full discussion in #2936

Describe the bug Our acceptance criteria includes "When user selects browser back button when menu is opened, menu collapses" but I wasn't able to replicate on mobile.

Acceptance criteria

• [ ] When user selects browser back button when menu is opened, menu collapses

URL

To Reproduce

1. Go to https://janis.austintexas.io/en/health-safety/healthcare-prevention/disease-prevention/mobile-food-permitting-process-guide/
2. Click on table of contents
3. Try clicking back button

Current behavior goes back to the page I was on BEFORE going to the guide

Expected behavior ToC closes and I see the guide

Screenshots

Device iPhone 6

Browser Safari AND chrome

Additional context

[desigonz]

3445

As a resident, I want a phone number for a complicated City process so that I can access help if I need it.

As a content editor, I want contact info on guides to require phone numbers so that I can make sure residents have that information when they need it.

Is your feature request related to a problem? Please describe. This is what happens when you add a contact to a guide but don't have a phone number added.

• We want to require phone numbers for guides
• However, we don't want to require phone numbers for other contacts

Describe the solution you'd like Possibly could decouple guide contacts, like we are doing on locations.

Describe alternatives you've considered

Additional context Add any other context or screenshots about the feature request here.

[desigonz]

Documenting some guide IA thoughts from @srigdon to tackle in the future:

Is a guide an end node? A guide is a collection of pages (end nodes). It functions both as an end node (I want to read this guide) and a directory of pages related to a complex service (Get a mobile food vendor permit).

But is putting a guide in the same level as the end node it collects going to be a problem?

Level 1: themes Level 2: topic collections
Level 3: topics Level 4: pages or end nodes --> Does this include guides? For now, yes.

Would people have use for a landing page for guides? Like so: https://www.boston.gov/guides This seems functional only in the "Related information" sense.

[toribr]

Guide creation issue: #4359