Skip to content
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

feat(page-header): add site-wide components - FRONT-3546 #2337

Merged
merged 46 commits into from May 2, 2022

Conversation

@github-actions
Copy link

github-actions bot commented Feb 15, 2022

Copy link
Contributor

@emeryro emeryro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should use another image at least for the core page header (blue on blue isn't very nice)
image
(there are several images already available on the server, just change the number at the end https://inno-ecl.s3.amazonaws.com/media/examples/example-image2.jpg)

export const MetaTitle = (args) =>
pageHeader(prepareData(demoMetaTitleContent, args));

MetaTitle.storyName = 'meta-title';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of having multiple stories here we should follow the same logic as other component: a single story and controls for optional elements

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

import { withNotes } from '@ecl/storybook-addon-notes';
import withCode from '@ecl/storybook-addon-code';
import { correctSvgPath } from '@ecl/story-utils';

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same remark as on the footer: there is no EU page header harmonised?
This is strange as there is a site header...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

const argTypes = {};

argTypes.breadcrumb = {
name: 'breadcrumb',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should keep the same kind of structure/naming for the optional controls:
show_breadcrumb, and put in an "optional" group
(check the content-item for instance)

{% spaceless %}
{#
Parameters:
- "variant" (string) (default: '') core, standardised or harmonised
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of having variant for the families, we should have two possible displays ("positive" and "negative")
then one of the other will be used to create a family specific page header

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

/*
* Core - Negative Variant
*/
.ecl-page-header--core {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be named "ecl-page-header--negative"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done, we will also change the breadcrumb include in the same way when we redo that component 👍

@@ -0,0 +1,12 @@
module.exports = {
title: 'Page title',
description:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of having multiple data files we could have just one containing everything and handle it in the stories to display some elements or not.
that's how we handled latest component

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@emeryro emeryro merged commit 75acda6 into v3-dev May 2, 2022
@emeryro emeryro deleted the feat/FRONT-3546 branch May 2, 2022 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants