Improve remaining workshop events to follow SF 4-step lab pattern#14
Open
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
Open
Improve remaining workshop events to follow SF 4-step lab pattern#14devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
Conversation
- enterprise-demo-track: Replace 'What to Demo' with 'What to Try', 'Key Talking Points' with 'Key Takeaways', add 4-step format (Get Started Fast, Level Up with AskDevin, Explore with DeepWiki, Review PR and Give Feedback) to all 3 labs, remove facilitator email - workshop-variant-2: Add 4-step format to all 4 labs, remove facilitator email, use hands-on participant-centered language throughout - platform-microservice-decomposition: Restructure from 4-phase format to 4-step lab format, remove facilitator email, consolidate facilitator notes into main content - cobol-modernization-workshop: Add 4-step format to all 4 labs, preserve existing 'What to Try' and 'Key Takeaways' language, remove facilitator email - oslo: Remove facilitator email from event details
Contributor
Author
🤖 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:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restructures all remaining workshop event READMEs to follow the San Francisco workshop's 4-step lab format, reducing cognitive load and creating a consistent participant experience across all events.
Pattern applied to each lab:
Files changed:
events/2026-03-09-oslo/README.md— removed facilitator email only (already followed SF pattern)events/cobol-modernization-workshop/README.md— replaced Abstract/Structure/What-to-Try format with 4-step labs; added Accelerated Variant table for different durationsevents/enterprise-demo-track/README.md— replaced "What to Demo"/"Key Talking Points" with "What to Try"/"Key Takeaways" and 4-step formatevents/platform-microservice-decomposition/README.md— consolidated 4-phase facilitator-oriented format into single deep-dive lab with 4-step formatevents/workshop-variant-2/README.md— added 4-step format to all 4 labs, removed facilitator-specific sectionsAlso across all files: removed facilitator email addresses from event details tables, removed "Repo Duplication Notes" and "Post-Event" checklists (facilitator-specific), standardized target outcomes format.
Review & Testing Checklist for Human
MM12,MM13,MM14(COBOL System Understanding, Migration Planning, Migration Test Harness). The platform decomposition referencesDA8. These are newly introduced links — confirm the corresponding files exist undermodules/or the links will be broken@cognition.aior any email patternsRecommended test plan: Open each modified README in a markdown previewer and click through all relative links (
../../modules/...) to confirm they resolve. Spot-check 2–3 Step 1 prompts by verifying the referenced repo names and file paths exist in the org.Notes