Showroom Namespace Setup
Complete setup guide for Red Hat Showroom workshop and demo content creation.
Overview
The showroom namespace provides AI-powered skills for creating Red Hat Showroom workshop and demo content. These skills focus purely on content creation without infrastructure provisioning.
Target Audience: Content creators, technical writers, workshop developers
Installation
Install the showroom namespace:
Claude Code
/plugin marketplace add rhpds/rhdp-skills-marketplace
/plugin install showroom@rhdp-marketplace
Cursor
curl -fsSL https://raw.githubusercontent.com/rhpds/rhdp-skills-marketplace/main/install-cursor.sh | bash
Included Skills
/showroom:create-lab
Generate workshop lab modules with Red Hat Showroom structure
- Know/Do/Check pedagogical structure
- Multi-module workshops
- Proper AsciiDoc formatting
- Dynamic content placeholders
/showroom:create-demo
Generate presenter-led demo content
- Know/Show demo structure
- Presenter notes
- Show-first approach
- Time estimates per section
/showroom:verify-content
AI-powered quality validation for workshop and demo content
- AsciiDoc syntax checking
- Know/Do/Check structure validation
- Exercise clarity checks
- Red Hat style guide compliance
/showroom:blog-generate
Transform completed lab/demo content into blog posts
- Blog-appropriate formatting
- Key takeaways extraction
- Call-to-action generation
- Red Hat Developer blog style
Prerequisites
Required
- Claude Code or Cursor installed
- Basic understanding of AsciiDoc (helpful but not required)
Optional
- Red Hat Showroom template repository
- GitHub account for publishing
- Red Hat Developer account (for blog publishing)
Typical Workflow
/showroom:create-labor/showroom:create-demoReview and edit generated content
/showroom:verify-contentFix any issues identified
/showroom:blog-generate(optional)Publish to Showroom and/or blog
Example: Creating a Workshop Lab
Run /showroom:create-lab
In Claude Code or Cursor: /showroom:create-lab Answer prompts: - Lab name: "CI/CD with OpenShift Pipelines" - Abstract: "Learn cloud-native CI/CD using Tekton pipelines on OpenShift" - Technologies: Tekton, OpenShift, Pipelines - Module count: 3Generated Structure
content/modules/ROOT/ โโโ pages/ โ โโโ index.adoc โ โโโ module-01.adoc โ โโโ module-02.adoc โ โโโ module-03.adoc โโโ partials/ โ โโโ _attributes.adoc โโโ nav.adocVerify Quality
/showroom:verify-content Reviews: โ AsciiDoc syntax โ Know/Do/Check structure โ Exercise clarity โ ๏ธ Suggestions for improvementGenerate Blog (Optional)
/showroom:blog-generate Creates: - Blog post from workshop content - Introduction and conclusion - Key takeaways - Call-to-action
Content Structure
Module Format (Know/Do/Check)
Each module follows this structure:
= Module Title
== Know (2 minutes)
Brief explanation of the concept...
== Do (8 minutes)
Hands-on exercise:
.Procedure
. Step 1
. Step 2
. Step 3
.Verification
After completing...you should see...
Placeholder Attributes
Use these in your content:
| Attribute | Usage |
|---|---|
{openshift_console_url} |
Console URL |
{user} |
Username |
{password} |
Password |
{user_namespace} |
Namespace |
{api_url} |
API URL |
Defined in partials/_attributes.adoc
Tips & Best Practices
Content Creation
- Start with clear objectives - Know what learners should achieve
- Keep modules focused - One concept per module
- Use active voice - "Create a pipeline" not "A pipeline is created"
- Test exercises - Ensure steps work as documented
- Add verification - Help learners confirm success
Using Skills
- Be specific with prompts - More detail = better output
- Iterate on content - Run /showroom:create-lab multiple times if needed
- Verify early - Run /showroom:verify-content before extensive edits
- Leverage examples - Ask skills for similar examples
Troubleshooting
Skill Not Found
Problem: /showroom:create-lab not recognized
Solution:
- Restart your editor
- Verify installation:
ls ~/.claude/skills/orls ~/.cursor/skills/ - Reinstall if needed
Generated Content Has Issues
Problem: Content doesn't meet quality standards
Solution:
- Run
/showroom:verify-contentto identify specific issues - Edit content based on suggestions
- Re-verify after changes
Attributes Not Rendering
Problem: {openshift_console_url} shows as literal text
Solution:
Ensure _attributes.adoc is defined in partials/:
:openshift_console_url: https://console-openshift-console.apps.cluster.example.com
:user: user1
:password: openshift
Next Steps
View All Skills
Explore skill documentation
Quick Reference
Common commands & workflows
Troubleshooting
Common issues & solutions