Skip to content
This repository was archived by the owner on Jul 1, 2026. It is now read-only.

feat(design-system): Integrate Inkline component library as baseline#308

Open
tkaragianes wants to merge 9 commits into
mainfrom
feat/integrate-inkline
Open

feat(design-system): Integrate Inkline component library as baseline#308
tkaragianes wants to merge 9 commits into
mainfrom
feat/integrate-inkline

Conversation

@tkaragianes

@tkaragianes tkaragianes commented Jan 25, 2023

Copy link
Copy Markdown
Contributor

Summary

We plan to integrate the Inkline Vue component library as a starting point to speed component creation. We will wrap Inkline components in an Eterna components and use the Eterna components in our pages. This gives us an escape hatch should we need to replace the Inkline library in the future, and lets us define Eterna-specific details for each component.

Implementation Notes

Inkline uses CSS variables to style components. Eterna uses an override file that allows us to globally reassign Inkline's variables with our design-system standards. We can also locally override Inkline variables on a per-component basis.

Related Issues

Closes #40.

We plan to integrate the Inkline Vue component library as a starting
point to speed component creation. We will wrap Inkline components in
an Eterna components and use the Eterna components in our pages. This
gives us an escape hatch should we need to replace the Inkline library
in the future, and lets us define Eterna-specific details for each
component.
@tkaragianes tkaragianes requested a review from a team as a code owner January 25, 2023 20:31
@tkaragianes tkaragianes changed the title feat[design-system]: Integrate Inkline component library as baseline feat(design-system): Integrate Inkline component library as baseline Jan 25, 2023

@luxaritas luxaritas left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It doesn't look like this closes #40 - there's still a lot of Inkline global variables that aren't mapped to tokens

Comment thread packages/design-system/vue/package.json
Build:watch on the token-transformer now runs the tranform script
on initial call, and then watches tokens.json and retriggers the
transform script on changes.
Token transformer now splits multi-property values into separate css
variables. This commit also removes the font-family hack now that
Figma supports comma separated values.
Our TS rules don't allow variable shadowing. In correcting the issue,
I missed one `key` that should be `property`.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement Inkline theme

2 participants