Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

The landing page of console should offer users customizable ways to get to where they want, see favorites, see bookmarked learning resources, see widgets of there support cases and beyond. I should be able to X out of things i don't want, and add things i do want.

https://www.sketch.com/s/bb96734a-0839-4776-9344-c7705dd3e560

Research - https://docs.google.com/presentation/d/1ae4EChrYKQivNFmVaP8Nc1cE0LjU32UT6bU5ZYqIXOw/edit?usp=sharing

What widgets do we pick doc - https://docs.google.com/document/d/1UjFAKAoxAFrjfKPiFV9d5aWauAQ3-eKRtCHWeBI4qMg/edit?usp=sharing

1. Your open support cases widget
2. Favorites
3. Recently visited
4. Bookmarked Learning
5. Event log
6. Subscriptions (make it look cool) (team tramaine) 
7. Explore Capabilities (words instead of getting started)

• Rbac/ integrations include / set up 3rd party idp? General shiz

1. Product Family the big 3 at top by default

• RHEL (not saying insights)
• Openshift
• Ansible

Acceptance Criteria 

These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.

1. The marketing banner is gone.
2. Ability to drag and drop widgets.
3. I can X out of widgets.
4. I can re add the widgets I Xd out of.
5. It is customizable to ME, and my user.

Checklist

Open Questions

Ability for Red Hat to add new widgets, how does that look when we introduce a new one.