-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cc-header-orga: tweak the design to make premium more subtle and allow extra content #869
Comments
Imo, I think I like the first option more:
I tend to also like the second option but a bit less. Indeed, if we're in the last case there's a lot of information within the block and might lack some space. And finally I'm really not into the third option, the color of the link with color of the lower "block" background makes it a big no for me. |
1 > 2 > 3 🌞 |
From a design perspective, I think I prefer option 1 the most: overall most balanced in my opinion. 👌 But from a content perspective, there's a case with option 3: in the page where the component will be integrated, it will be displayed above with the content below it. Which is maybe less obvious with option 1. Or maybe it's just me? 🤔 |
@Galimede @roberttran-cc thanks for your input, what do you think of the two options below? |
With these two options, I think I prefer the alignment of the first option. I also think that I prefer this version over the previous first idea 👍 |
Nice proposal: it tackles a lot of use cases and behaves well on all scenarios. 👍 PS: I expect the footer content being slotted and its background customisable with a CSS custom property 👀 |
Thanks for your differents proposals. |
First poll: option 1 I like to have the orga details in the main area and the contextual stuffs in the bottom grey banner. |
Context
In the
cc-credit-consumption
component, we want to use thecc-header-orga
component but we would also like to add extra information within it:The current design of the
cc-header-orga
is not really adapted for this.We would need to make the premium info a little bit more subtle and add a slot to the component.
Solutions
I think a simple solution would be to get closer to the design of our other
cc-header
components with a footer to free up some space within the header itself.The text was updated successfully, but these errors were encountered: