Skip to content

fix(website): Fixed documentation badges space on documentation #23229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

melinoix
Copy link
Contributor

Summary

fix(docs): Fixed documentation badges space on documentation

This change adds a mr-1 (margin-right) class to the badge container span to properly space badges when displayed inline, improving readability and visual layout in the documentation.

Change Type

  • Bug fix
  • New feature
  • Non-functional (chore, refactoring, docs)
  • Performance

Is this a breaking change?

  • Yes
  • No

How did you test this PR?

I built and previewed the documentation locally to verify that badges now have consistent spacing between each other without collapsing. The badges render correctly across different browsers and screen sizes.

Does this PR include user facing changes?

  • Yes. Please add a changelog fragment based on our guidelines.
  • No. A maintainer will apply the "no-changelog" label to this PR.

Notes

  • Please read our Vector contributor resources.
  • Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
  • The CI checks run only after we manually approve them.
    • We recommend adding a pre-push hook, please see this template.
    • Alternatively, we recommend running the following locally before pushing to the remote branch:
      • cargo fmt --all
      • cargo clippy --workspace --all-targets -- -D warnings
      • cargo nextest run --workspace (alternatively, you can run cargo test --all)
      • ./scripts/check_changelog_fragments.sh
  • After a review is requested, please avoid force pushes to help us review incrementally.
    • Feel free to push as many commits as you want. They will be squashed into one before merging.
    • For example, you can run git merge origin master and git push.
  • If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
    run cargo vdev build licenses to regenerate the license inventory and commit the changes (if any). More details here.

References

@melinoix melinoix requested a review from a team as a code owner June 18, 2025 15:13
@bits-bot
Copy link

bits-bot commented Jun 18, 2025

CLA assistant check
All committers have signed the CLA.

@thomasqueirozb thomasqueirozb added the no-changelog Changes in this PR do not need user-facing explanations in the release changelog label Jun 18, 2025
@thomasqueirozb thomasqueirozb changed the title fix(docs): Fixed documentation badges space on documentation fix(website): Fixed documentation badges space on documentation Jun 18, 2025
@thomasqueirozb thomasqueirozb enabled auto-merge June 18, 2025 15:16
@pront
Copy link
Member

pront commented Jun 18, 2025

Much better
image

Thanks!

Copy link
Contributor

@thomasqueirozb thomasqueirozb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@thomasqueirozb thomasqueirozb added this pull request to the merge queue Jun 18, 2025
Merged via the queue into vectordotdev:master with commit aded15b Jun 18, 2025
70 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants