You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Adding New "End User" Documentation to RHDH Local to help with onboarding etc. - #127
This PR adds a new getting started guide intended to help brand new Developer Hub users get started quickly. The guide covers essential first-day tasks:
Core Platform Features
📦 Software Catalog
Discovering and browsing components, services, APIs, and resources
Filtering by kind, type, owner, lifecycle, and tags
Viewing component details, relationships, and dependencies
Adding components via templates, manual registration, or bulk import
Official Red Hat Developer Hub documentation links
Backstage community resources
Plugin and template libraries
Tools and utilities
The content is written for complete beginners, uses engaging language with emojis and callouts consistent with other getting started guides, and includes practical tips and "Next Steps" sections linking to related documentation.
This addresses a gap identified in the documentation review where new users lacked guidance on basic first-day tasks like logging in, understanding the homepage, and personalizing their experience.
Which issue(s) does this PR fix or relate to
Fixes #issue_number
PR acceptance criteria
Tests updated and passing
Documentation updated
Built-in TechDocs updated if needed. Note that TechDocs changes may need to be reviewed by a Product Manager and/or Architect to ensure content accuracy, clarity, and alignment with user needs.
How to test changes / Special notes to the reviewer
Testing the Documentation
Preview the new page:
Build and serve the TechDocs locally (or view in MkDocs preview)
Navigate to "RHDH Guide" in the left hand navigation and open the getting started guide section
Verify the page renders correctly with proper formatting, callouts, and links
Verify content accuracy:
Check that the content matches the actual Developer Hub functionality
Check consistency:
Verify the tone and style match other getting started guides
Confirm emoji usage and callout types are consistent
Check that "Next Steps" section follows the same pattern as other guides (where used)
Test navigation:
Verify all internal links (e.g., navigation.md, software-catalog.md, etc.) are correct
Check that application routes (e.g., /catalog, /create) are properly formatted
Ensure external links (e.g., official documentation) are valid
Special Notes
This is a new section - but some existing content was moved/modified
Content is based on actual Developer Hub UI screenshots provided during development
The guide is intentionally beginner-friendly and focuses on first-day essentials rather than comprehensive feature coverage
Description
This PR adds a new getting started guide intended to help brand new Developer Hub users get started quickly. The guide covers essential first-day tasks:
Core Platform Features
📦 Software Catalog
📋 Software Templates
📚 TechDocs
🧩 API Browser
🔍 Global Search
🧭 Navigation
🔌 Extensions (Plugins)
⚡ Developer Lightspeed
User Experience Features
🌅 Your First Day
🏠 Homepage & Dashboard
⭐ Starred Items
👤 Profile & Settings
Platform Information
🎯 Platform Overview
💡 Best Practices & Tips
📖 References & Resources
The content is written for complete beginners, uses engaging language with emojis and callouts consistent with other getting started guides, and includes practical tips and "Next Steps" sections linking to related documentation.
This addresses a gap identified in the documentation review where new users lacked guidance on basic first-day tasks like logging in, understanding the homepage, and personalizing their experience.
Which issue(s) does this PR fix or relate to
PR acceptance criteria
How to test changes / Special notes to the reviewer
Testing the Documentation
Preview the new page:
Verify content accuracy:
Check consistency:
Test navigation:
navigation.md,software-catalog.md, etc.) are correct/catalog,/create) are properly formattedSpecial Notes