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.

Sign up for GitHub

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

Jump to bottom

Token and CSS layout implementation #7488

Open
2 of 3 tasks
geospatialem opened this issue Aug 8, 2023 · 0 comments
Open
2 of 3 tasks

Token and CSS layout implementation #7488

geospatialem opened this issue Aug 8, 2023 · 0 comments
Assignees
@alisonailea
Labels
1 - assigned Issues that are assigned to a sprint and a team member. Calcite (dev) Issues logged by Calcite developers. calcite-components Issues specific to the @esri/calcite-components package. design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p - medium Issue is non core or affecting less that 60% of people using the library spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Milestone
2025-02-25 - Feb ...

Comments

@geospatialem
Copy link
Member

Check existing issues

Description

We're working towards supporting our users, in particular around layout and what was previously provided in Calcite Web.

Once a story is complete, we can work towards directing folks to resources and guidance in moving from Calcite Web to Calcite Design System.

cc @macandcheese @jcfranco @brittneytewks

Acceptance Criteria

  • Support similar to what is provided in Calcite Web deprecated
  • Provide tokens/css classes as part of the animation story
    • Maybe something like @esri/calcite-css-utils (or something along those lines)?

Relevant Info

Should be considered as part of the design token phase II effort in #7180.

Which Component

Across the design system and all components

Example Use Case

No response

Priority impact

p2 - want for current milestone

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react

Esri team

Calcite (dev)
@geospatialem geospatialem added enhancement Issues tied to a new feature or request. design Issues that need design consultation prior to development. p - high Issue should be addressed in the current milestone, impacts component or core functionality 1 - assigned Issues that are assigned to a sprint and a team member. labels Aug 8, 2023
@geospatialem geospatialem added this to the Design Sprint milestone Aug 8, 2023
@github-actions github-actions bot added calcite-components Issues specific to the @esri/calcite-components package. Calcite (dev) Issues logged by Calcite developers. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone labels Aug 8, 2023
@geospatialem geospatialem mentioned this issue Aug 8, 2023
Open
@brittneytewks brittneytewks added the figma changes Issues that require additions or updates to the Figma UI Kit where no `design` label exists label Sep 12, 2023
@brittneytewks brittneytewks added the spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. label Nov 13, 2023
@alisonailea alisonailea added 2 - in development Issues that are actively being worked on. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Dec 9, 2023
@brittneytewks brittneytewks removed the figma changes Issues that require additions or updates to the Figma UI Kit where no `design` label exists label Dec 12, 2023
@geospatialem geospatialem modified the milestones: 2024-01-17 - Jan Main Release, 2024-01-19 - Jan Maintenance Release Jan 17, 2024
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 2 - in development Issues that are actively being worked on. labels Jul 1, 2024
@brittneytewks brittneytewks added p - medium Issue is non core or affecting less that 60% of people using the library and removed p - high Issue should be addressed in the current milestone, impacts component or core functionality labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alisonailea alisonailea

Labels
1 - assigned Issues that are assigned to a sprint and a team member. Calcite (dev) Issues logged by Calcite developers. calcite-components Issues specific to the @esri/calcite-components package. design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p - medium Issue is non core or affecting less that 60% of people using the library spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Projects
None yet
Milestone
2025-02-25 - Feb Milestone
Development

No branches or pull requests
5 participants
@alisonailea @geospatialem @SkyeSeitz @ashetland @brittneytewks