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

chore: introduce o-colors to private foundation #1888

Merged
merged 98 commits into from
Dec 18, 2024

Conversation

frshwtr
Copy link
Contributor

@frshwtr frshwtr commented Nov 28, 2024

Describe your changes

This is still WIP. Raising to visually see changes

Issue ticket number and link

Link to Figma designs

Checklist before requesting a review

  • I have applied percy label for o-[COMPONENT] or chromatic label for o3-[COMPONENT] on my PR before merging and after review. Find more details in CONTRIBUTING.md
  • If it is a new feature, I have added thorough tests.
  • I have updated relevant docs.
  • I have updated relevant env variables in Doppler.

frshwtr and others added 14 commits November 7, 2024 11:46
* feat: introduce o-private-foundation

* feat: introduce o-private-foundation

* backstage: Add Sass token target

* backstage: Delete oPrivateFoundation mixin use, as it does not exist

---------

Co-authored-by: Lee Moody <[email protected]>
We decided to develop using traditional demos for this package, as the dev experience is better with Sass. We do not expect users to use this package
* feat: introduce o-private-foundation

* feat: introduce o-normalise to o-private-foundation

* feat: use o-private-foundation in origami components

* feat: introduce o-private-foundation

* feat: introduce o-private-foundation

* feat: introduce o-private-foundation

* chore: revert stories to use o-normalise

* chore: remove unused mixins and prefix remaining with private

* feat: use o-private-foundation's o-normalise

* fix: fix broken imports

* fix: fix buttons

* chore: use private foundation normalise

* chore: revert typography and buttons changes

* chore: correct errors

* chore: update package-lock.json

* chore: use main scss file

* chore: use imports as final approach, include o-colors

* chore: ensure private foundation is a peerDependency

* chore: remove tsx files

* chore: remove further cases of @use

* chore: remove unecessary variable

* chore: namespace variables

* chore: ensure original o-normalise is used in demos

---------

Co-authored-by: Lee Moody <[email protected]>
Takes o3-button and refactors to work in an o2 world. Slightly
odd use of Sass/CSS Custom Properties, with Sass conditionals
used to output duplicate CSS Custom Properties which override
each other in the same declaration. This was the safest way
to reuse o3 styles by effectively replacing class names for
Sass if statements. It's also more readable and simple than o2
Sass. Despite duplicating some properties, CSS output and
performance will be improved by moving away from the Origami
Image Service for coloured icons.

Currently supports:
- Types
- Themes
- Sizes
- Icons
- Icons only

Does not yet support:
- Custom theme maps

Will not support:
- Outputting CSS granularly. There are not many buttons left in
o2 components, and bundle size is reduced overall as noted above.

Other things of note:
- `o-private-foundation-get` allows other o2 components to grab tokens directly.
- Added Metric2 variable font
@frshwtr frshwtr requested a review from a team November 28, 2024 11:28
@frshwtr frshwtr requested a review from a team as a code owner November 28, 2024 11:28
@frshwtr frshwtr marked this pull request as draft November 28, 2024 11:28
@frshwtr frshwtr changed the base branch from main to 2025-release November 28, 2024 11:29
@notlee notlee temporarily deployed to origami-webs-2025-relea-looadm November 28, 2024 11:32 Inactive
components/o-forms/main.scss Outdated Show resolved Hide resolved
@notlee notlee temporarily deployed to origami-webs-2025-relea-diircq December 13, 2024 14:05 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-diircq December 13, 2024 14:45 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-diircq December 13, 2024 16:38 Inactive
@frshwtr frshwtr force-pushed the 2025-release-o-colors branch from 15c2a93 to 0add987 Compare December 16, 2024 15:49
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 16, 2024 15:52 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 17, 2024 09:46 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 17, 2024 10:35 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 17, 2024 11:10 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 17, 2024 11:20 Inactive
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 17, 2024 12:37 Inactive
@notlee notlee self-requested a review December 18, 2024 14:33
@notlee notlee temporarily deployed to origami-webs-2025-relea-0o0rqj December 18, 2024 14:33 Inactive
@notlee notlee merged commit 27b996e into 2025-release Dec 18, 2024
29 of 40 checks passed
@notlee notlee deleted the 2025-release-o-colors branch December 18, 2024 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants