Skip to content
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

table of contents with lengthy ordered lists has very tight left padding #184

Open
thescientist13 opened this issue Feb 8, 2025 · 1 comment · May be fixed by #202
Open

table of contents with lengthy ordered lists has very tight left padding #184

thescientist13 opened this issue Feb 8, 2025 · 1 comment · May be fixed by #202
Assignees
Labels
docs Greenwood specific content like docs and guides enhancement New feature or request good first issue Good for newcomers

Comments

@thescientist13
Copy link
Member

If you go to a page with a length list of items in the right side Table of Contents component like the Plugin API docs page which has nine items on it, by the time the content gets to the bottom of the ToC container, the padding on the left starts to get super tight, almost getting cut off
Image

Would be good to make sure that this text always has a little room to breath on the left.

@thescientist13 thescientist13 added docs Greenwood specific content like docs and guides enhancement New feature or request good first issue Good for newcomers labels Feb 8, 2025
@thescientist13 thescientist13 changed the title table of contents with lengthy order lists has very tight left padding table of contents with lengthy ordered lists has very tight left padding Mar 30, 2025
@darragh4
Copy link

I submitted a pull request; I've centred the text to remove the tightness on the left-hand side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Greenwood specific content like docs and guides enhancement New feature or request good first issue Good for newcomers
Projects
Status: 👀 In review
Development

Successfully merging a pull request may close this issue.

2 participants