New product icon > Operate

Description

A new icon is needed to represent the Operate navigation collection.

  • Both Operate and Operations exist in the nav
  • Operate is using the deployment icon
  • Operations uses the cloud-gear icon
  • Deployments will now become its own top-level nav item and will need its icon back

Related: gitlab#405011 (comment 1385991427)

Concept

A cloud-only or cloud as the basis approach to generally represent simple data operation concepts. Because of the variety of items in the collection, the icon has a 1:many relationship.

operate_D.svg

All concepts…
Concept Icon Notes
A operate_A.svg A simple cloud
B operate_B.svg A data cloud
C operate_C.svg A cloud with embedded server- or data-like container
D operate_D.svg A cloud with a pod or container
E data.svg A database

Figma file

❖ View working file in Figma →

Checklists

Make sure the following are completed before closing the issue:

Assignee tasks:

See tasks:
  1. Create or update an icon
    • If you’re a community contributor, please fork the GitLab Product Icons file when updating or creating an icon.
    • If you’re a GitLab team member, please create a branch of the GitLab Product Icons file. Prefix the branch name with the issue, MR, or epic number, and add your GitLab username as the suffix. For example, #860-new-icon-lvanc. Then update or create an icon.
  2. Update the link to the working file under the Figma link section above.
  3. If work was not done in a branch (a merged branch will automatically be archived), move your working file to the shared Figma project:
    1. For all other changes, move your file to the Misc archive project.
    2. If you’re a community contributor, please consider transferring ownership of your draft file to the maintainer so they can move it to our archive, along with its version history and comments.
  4. When applicable, follow our iconography guidelines.
  5. Ask a Foundations designer to review your design.
    • If you’re a community contributor, ensure the designer that will be reviewing your file has edit permissions in Figma.
    • If you’re a GitLab team member, request a review in Figma.

Reviewer tasks:

See tasks:
  1. Review the icon in the author’s branch. Add design-specific comments in Figma to maintain context. Add general comments to this issue, including your approval status.
  2. Once review is approved, assign to a Figma maintainer for final review.

Maintainer tasks:

See tasks:
  1. Merge the branch to the GitLab Product Icons file, convert the icon to a component, add keywords and usage notes (optional) in the description, and view it in the Assets panel to ensure it aligns with what’s outlined in the document and asset library structure documentation.
  2. Publish the library changes along with a clear message about the update.

Library addition tasks:

Once the Reviewer or Maintainer has approved your icon design, consider the following tasks to add the icon the gitlab-svgs library.

See tasks:
  1. Create a new merge request (MR) from this issue.
  2. Checkout the new branch locally.
  3. Export the icon component from the Pajamas UI Kit (in Figma) to the /sprite_icons folder in your local instance of the repo. The file name should be lowercase, and use hyphens as a separator between terms.
  4. Open the SVG you just exported in your code editor and remove fill="none" from the <svg> element.
  5. In a terminal window, run yarn run dev to preview the SVG library locally. Find the new icon and test it out by changing settings in the Icon configuration panel of the site. The icon should change color and size with no issues.
  6. After you’ve committed the changes and the pipeline passes, double-check your icon in the review app and test that it matches your expectations.
  7. Assign the MR to be reviewed and merged by a maintainer, and proceed with any changes.
  8. Add a read only (FYI) agenda item to the next UX weekly call to inform everyone of the new icon, linking to this issue. Will be added to the UI kit release notes.

If you run into any problems, ensure that all other steps in the project README have been followed.

  1. 🎉 Congrats, you made it! You can now close this issue.

Links / references

Edited by Jeremy Elder