refactor(theme-classic): make tag text visually certered

[Kosai106]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

The tag content was visually offset which looked out of place. This fixes it.

Test Plan

Manually verified.

Before	After

[facebook-github-bot]

Hi @Kosai106!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	3bffc92
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62e7d79e57c64c000834b25d
😎 Deploy Preview	https://deploy-preview-7876--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 68	🟢 98	🟢 100	🟢 100	🟠 80	Report
/docs/installation	🟠 75	🟢 100	🟢 100	🟢 100	🟢 90	Report

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	358d4b4
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62e7d83d2d6cf400086f1f6e
😎 Deploy Preview	https://deploy-preview-7876--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[Josh-Cena]

Interesting. I don't like the idea of hacking dimensions just so things appear "visually aligned", because if you use a font with different baseline height then everything is misaligned again. But I'm not master with CSS so I'll defer this to someone else to review.

[slorber]

Thanks.

I'll merge because it looks better by default and with many fonts.

However, this is not a good generic solution to this problem.

The problem is that fonts have different ascenders/descenders.
Different fonts will give you different results here, and this change may even annoy some Docusaurus users that are using fonts that are already more "balanced".

See for example what the "fantasy" font looks like (no padding change) compared to the original:

This is a good lib to work with ascenders/descenders, or just to understand the problem: https://seek-oss.github.io/capsize/

[Kosai106]

@slorber absolutely it's not a perfect solution by any means. However it is the simplest and quickest, short term at least.