Connect - Partner Experience Hub (Portal)
- Dominant language
- No language data
- Stars
- 0
- Forks
- 4
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
**Goal**: Create a central hub where different audiences can learn about Connect services and determine how to engage with the platform.
**Scope**
• Landing page strategy
• Audience segmentation
• Navigation and routing
• Service catalog
• Platform overview
• Onboarding entry points
• Resource library
**Key Questions**
• Where will users access the hub from?
• Public vs internal access?
• Single landing page or multiple audience-specific landing pages?
• How will users navigate to relevant content?
**Deliverables**
• Information architecture
• Landing page design
• Audience journeys
• Navigation model
• Service catalog integration
Contributor guide
Research direction
Start by reviewing the issue's scope and key questions to define the portal's audiences, access model, navigation, and content structure. Produce the listed information architecture, landing page design, audience journeys, navigation model, and service catalog integration; completion should address each stated deliverable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100