Review all `h1` font sizes

The following discussion from !22155 (merged) should be addressed:

• @annabeldunstone started a discussion: (+1 comment)

  @matejlatin is this the size all h1 elements should be? I see it specified for markdown h1s, but there are a lot of variations in other files. Maybe we should create a separate issue to fix these.

Proposal

All h1 elements should be 28px

1.75em is the correct size, it matches the 28px size in our library.

@matejlatin So should the other h1 sizes be fixed?

added Manage [DEPRECATED] UX devopsmanage navigation labels

@annabeldunstone hmmm, I haven't paid much attention to the h1 sizes so far... if they're different from what's in the library yes, they should be updated.

changed title from Follow-up from "Resolve "Change single-item breadcrumbs to page titles"" to {+Review all h1 font sizes+}

changed the description

@matejlatin Do we have a preference between px or em? We currently use both

changed title from Review all h1 font sizes to Review all h1 font sizes test addition

changed title from Review all h1 font sizes test addition to Review all h1 font sizes

@annabeldunstone em is definitely better than px. It's a relative unit, based on the default font size (either browser default or user setting). How come we don't use rem? em can get confusing sometimes, especially in such large systems...

I believe we are using rem in csslab. cc @ClemMakesApps

Yes, rem in csslab.

What's csslab?

@matejlatin it's our in-progress CSS framwork! https://gitlab.com/gitlab-org/csslab

mentioned in issue #51944 (closed)

added [deprecated] Accepting merge requests label

added groupoptimize label

removed [deprecated] Accepting merge requests label

mentioned in merge request gitlab-org/quality/triage-ops!268 (closed)

added 1 deleted label and removed devopsmanage groupoptimize labels

Setting devopsmanage based on Manage [DEPRECATED].

added devopsfoundations label

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue