feat(workshops/quality-engineering-security): add platform story coverage + delivery variants#116
Conversation
…rage + delivery variants - Add Platform Context section and cross-surface callout blocks to README.md (Cloud variant) - Add variant note linking to README.platform.md - Add Agent Command Center tip to Getting the Most section - Create README.platform.md (Desktop + Cloud variant) with Desktop-first workflow for each lab: explore locally with Cascade, delegate to Cloud, monitor in Agent Command Center, review PRs with one-click checkout
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
🚩 Post-Event section also exists pre-PR in README.md (same pattern)
The Post-Event checklist flagged as a bug in README.platform.md:217-222 also exists at README.md:178-183 (unchanged by this PR). It's a systemic pattern across all workshop READMEs (enterprise-security-automation/README.md:201, cobol-modernization/README.md:278, etc.). While the rule violation is clear, this is a repo-wide convention that would need a coordinated cleanup across all workshop files, not just this PR.
(Refers to lines 178-183)
Was this helpful? React with 👍 or 👎 to provide feedback.
| ## Post-Event | ||
|
|
||
| - [ ] Collect participant feedback | ||
| - [ ] Archive any event-specific branches | ||
| - [ ] Update challenge modules if issues were discovered | ||
| - [ ] Share session recordings/artifacts with participants |
There was a problem hiding this comment.
🟡 Facilitator-only post-event checklist in attendee-facing repo
The new README.platform.md includes a ## Post-Event section (lines 217–222) containing a facilitator checklist ("Collect participant feedback", "Archive any event-specific branches", etc.). REVIEW.md explicitly states: "Flag any facilitator-only content (MCP setup, presales positioning, timing guides, pacing tips for facilitators, post-event checklists). These belong in the operator repo." Attendees do not collect feedback or archive branches — this section is directed at facilitators and should be moved to the operator repo.
| ## Post-Event | |
| - [ ] Collect participant feedback | |
| - [ ] Archive any event-specific branches | |
| - [ ] Update challenge modules if issues were discovered | |
| - [ ] Share session recordings/artifacts with participants |
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Acknowledged — the ## Post-Event section is indeed facilitator-facing. However, it's a pre-existing pattern carried forward from the base README.md (lines 161–166, unchanged by this PR) for structural consistency across variants. As the second comment notes, this same pattern exists across enterprise-security-automation/README.md, cobol-modernization/README.md, etc.
Removing it only from README.platform.md would create an inconsistency between variants. A repo-wide cleanup across all workshop READMEs would be the right approach — happy to do that as a separate PR if desired.
1 participant
Summary
Adds platform story coverage to the
quality-engineering-securityworkshop with two deliverables:README.md(Cloud variant — updated):## Platform Contextsection after the Abstract explaining this is a Cloud-via-web-app workshop, with a tip callout linking to the Desktop variantREADME.platform.mdREADME.platform.md(Desktop + Cloud variant — new):Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/75307981bd5943ad8273e5b352ba1088
Requested by: @bsmitches