Typo on "cognitive walkthrough" card

[brittag]

The "cognitive walkthrough" card says "Facilitate a walkthrough a solution where probing questions", which seems to be missing a colon (or another piece of punctuation or a word). Tiniest of issues!

[wslack]

Thanks @brittag! I think we can remove "a solution" but I'm not 100% sure and will defer to the team. :) I also notice that we may not need the comma in that sentence.

[jameshupp]

Thanks for catching that @brittag. There are actually a couple areas on this method where I think we can clean the language up a bit. I'll file a pull request on it shortly.

[jenniferthibault]

@jameshupp suggestions for a good way to make changes on the site & the printed cards, without losing track? Keeping the print cards up to date is definitely important, but it takes ~20 min each time we need to re-export and upload, so minimizing the number of times we do that would be 👍

[wslack]

@konklone does something similar for Pulse, he might have thoughts.

[jameshupp]

Eagerly awaiting ^. In the meantime, @jenniferthibault I think we do a few things.

• Apply a tag like, say, cards lang to any PRs that include language updates that affect the cards.
• Specify in each PR exactly which methods are affected. I know the file changes themselves will show it, but this way it'll be easier to see when multiple PRs affect the same method. A small language change on one method will usually not be worth re-exporting, but six or seven small changes on the same method might be.
• Create a regular cards update schedule for pulling in non-urgent changes. Biweekly? Monthly? Quarterly?
• Make sure the INDD files are in the shared folder so other visual designers can address if/when such issues arise in the event you aren't available. 😢

[jameshupp]

Oh! Question per ^:
Do we want to include something related to the 2nd and 3rd bullets in the contributing guidelines? (If, you know, we agree on the suggestions in the first place.)

[konklone]

@konklone does something similar for Pulse, he might have thoughts.

@wslack I do? :) Not sure what you mean. CCing @juliaelman.

[wslack]

Best practices for managing a painful manual update process when data might be changing (which I think is - @konklone regularly updates it regularly each month)

[konklone]

Oh, well, I run an update script that does all the work, but I do have to remember to trigger it every week, which I do with a calendar reminder. The updated results are versioned in GitHub week to week, and memorialized/managed with a pull request. It's not an awesome process, and something we hope to more fully automate later this year.

[jameshupp]

With this commit both the digital copy and the card are on staging and ready to deploy. Moving discussion of how to handle the printed cards to #32.