[EPIC] As a site visitor, I'd like the information in the Engineering guide to reflect up-to-date practices

[christophermather]

A description of the work

In the interest of iterative improvement, we should keep the content on the Engineering Guide up to date and ensure that it reflects our current practices.

There are a number of issues that have suggestions for updating site content. Find them in the task list below.

Reproduction steps (if necessary)

• Review issues and decide which ones should move forward and in what order
• Complete the issues as-able (likely through TLC increments)

Tasks

Beta Give feedback

1. 🟢 Ruby article is a stub (expand it) #321
   Engineering Guides Initiative 2 +3
2. 🟡 Document Credential management practices #322
   Engineering Guides Initiative 2 +3
3. 🟡 Update on-call recommendations for PHI/PII concerns #324
   Engineering Guides Initiative 2 +3
   
4. 🟡 Update with information related to Crypto #325
   Engineering Guides Initiative 2 +3
5. 🟡 Add post-incident response template #326
   Engineering Guides Initiative 2 good first issue +4
6. 🟢 Document various declarative, text-based diagram tools we use #327
   Engineering Guides Initiative 2 +3
   
7. 🟢 Add guidance on secret management for cloud.gov apps #329
   Engineering Guides Initiative 2 +3
   
8. 🟡 Create a new TTS engineer page #330
   Engineering Guides Initiative 2 +3
9. 🟢 Add content for Infrastructure as Code #331
   Engineering Guides Initiative 2 good first issue +4
   

[bpdesigns]

@cantsin are these still relevant? Is this something we should consider prioritizing?