Skip to content

Colorcard component#2122

Draft
marenhkj-vy wants to merge 3 commits intomainfrom
color-cards
Draft

Colorcard component#2122
marenhkj-vy wants to merge 3 commits intomainfrom
color-cards

Conversation

@marenhkj-vy
Copy link
Copy Markdown
Collaborator

Background

Mulighet for å legge inn colorcards når man skriver content til en page/article i Sanity for designmanual. Har tidligere vært et ønske om å legge inn dette under Fundementals > Illustration style.

Skjermbilde 2026-02-25 kl  08 56 29

(Har brukt dette litt som en "øve" oppgave)

Closes #


Solution


General Checklist

  • I have updated documentation if necessary
  • I have verified the design aligns with the latest Figma sketches.
  • I have created a changeset if publishing is required

Accessibility checklist

For changes impacting the user interface or functionality, ensure the following:

  • It is possible to use the keyboard to reach your changes
  • It is possible to enlarge the text 400% without losing functionality
  • It works on both mobile and desktop
  • It works in both Chrome, Safari and Firefox
  • It works with VoiceOver
  • There are no errors in aXe / SiteImprove-plugins / Wave

Screenshots

Before After

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Feb 25, 2026

⚠️ No Changeset found

Latest commit: 7d1ac5c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 9, 2026

Terraform Plan for Test 🔍

Show Plan
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.app.module.preview_url[0].aws_ssm_parameter.central_deployment_account_id will be updated in-place
  ~ resource "aws_ssm_parameter" "central_deployment_account_id" {
        id              = "/__deployment__/applications/preview-url-mapper/central-deployment-account-id"
        name            = "/__deployment__/applications/preview-url-mapper/central-deployment-account-id"
      ~ tags            = {
          - "application" = "digitalekanaler-admin" -> null
          - "repo"        = "digitalekanaler-admin-frontend" -> null
        }
      ~ tags_all        = {
          ~ "application" = "digitalekanaler-admin" -> "digitalekanaler-designmanual"
          ~ "repo"        = "digitalekanaler-admin-frontend" -> "spor"
            # (1 unchanged element hidden)
        }
        # (13 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Warning: Redundant ignore_changes element

  on .terraform/modules/app.preview_url/main.tf line 111, in resource "aws_lambda_function" "lambda_function":
 111: resource "aws_lambda_function" "lambda_function" {

Adding an attribute name to ignore_changes tells Terraform to ignore future
changes to the argument in configuration after the object has been created,
retaining the value originally configured.

The attribute qualified_arn is decided by the provider alone and therefore
there can be no configured value to compare with. Including this attribute in
ignore_changes has no effect. Remove the attribute from ignore_changes to
quiet this warning.

(and 2 more similar warnings elsewhere)

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

For commit 21cf91e
Plan generated at: 2026-03-09 08:04:00 UTC

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 9, 2026

Terraform Plan for Test 🔍

Show Plan
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.app.module.preview_url[0].aws_ssm_parameter.central_deployment_account_id will be updated in-place
  ~ resource "aws_ssm_parameter" "central_deployment_account_id" {
        id              = "/__deployment__/applications/preview-url-mapper/central-deployment-account-id"
        name            = "/__deployment__/applications/preview-url-mapper/central-deployment-account-id"
      ~ tags            = {
          - "application" = "digitalekanaler-admin" -> null
          - "repo"        = "digitalekanaler-admin-frontend" -> null
        }
      ~ tags_all        = {
          ~ "application" = "digitalekanaler-admin" -> "digitalekanaler-designmanual"
          ~ "repo"        = "digitalekanaler-admin-frontend" -> "spor"
            # (1 unchanged element hidden)
        }
        # (13 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Warning: Redundant ignore_changes element

  on .terraform/modules/app.preview_url/main.tf line 111, in resource "aws_lambda_function" "lambda_function":
 111: resource "aws_lambda_function" "lambda_function" {

Adding an attribute name to ignore_changes tells Terraform to ignore future
changes to the argument in configuration after the object has been created,
retaining the value originally configured.

The attribute qualified_arn is decided by the provider alone and therefore
there can be no configured value to compare with. Including this attribute in
ignore_changes has no effect. Remove the attribute from ignore_changes to
quiet this warning.

(and 2 more similar warnings elsewhere)

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.

For commit 7d1ac5c
Plan generated at: 2026-03-09 08:06:56 UTC

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.

1 participant