Skip to content

Draft: Add UX category to GitLab blog

Rayana Verissimo requested to merge rayana-master-patch-85617 into master

Why is this change being made?

This MR proposes creating a high-level category for UX (User Experience) in the GitLab blog.

Design influences everything we do at GitLab. Even though the UX department consists of 4 areas that support designing and building the GitLab product (UX Research, Technical Writing, Product Design, UX Foundations - Pajamas), we are just humble facilitators of user experience design. Everyone at GitLab is a designer. Behind the scenes, design shapes our work, how we build our product, how we interact with one another and with our community.

The intention of the UX category is to showcase, at the corporate level, stories that share offer insights into our thinking, process, research, creative work, and collaboration with the wider GitLab community that inspire and influence our work. Today, UX and UI are simple blog tags that can be attached to Unfiltered blog posts.

  • With a dedicated space to sharing stories, we create narratives to discover and engage with UX Department as a result of our experiences building GitLab.
  • Communication benefit: a more direct line of communication with customers and potential customers, the community, and candidates interesting in joining the UX department.
  • Reputation benefit: a design-focused blog (category) is an industry standard.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)

Links/references

Edited by Rayana Verissimo

Merge request reports