[Page Header] Create Page Header component

[landitus]

Give this component, we can call it 'Page header':

Has an option to show additional help:

Or can show a video tutorial

• Should it be in the DS? Is it part of Manage's internal components? We've seen shopify has this kind of organisms (or bigger components).
• If we added to the system, should it be as 'open' or 'closed' component?
• Does this logic apply to all organisms?

[landitus]

Kind of relates to issue: #40

Rigid components will help make it easier to test and maintain components. This can feel limiting at first, but it will help us build consistent UIs and remove some of the decision fatigue while picking components. (Bonus: easier to test + maintain)

I'm sure we can debate about flexibility and rigidity here as well 😁

[landitus]

I think that for the PoC we could change the tutorial video and add it as a modal. This way, the Page header component will be more simple

[siddharthkp]

I don't think the helper text should be part of the PageHeader component as well, we want to control the layout not the content

In my head, the API should be:

<PageHeader title="Clients" actions={[...]} descriptionComponent={whateverYouNeed}/>