feat: The headline is not in the right place.

[YasinSpace]

Describe the feature

As you can see,

the state in the title is not positioned correctly when we click on a title!

And specify this or add in the feature: Please add this : in config file we can change the size of the sidebar, for example, set it more forward or more backward ( resize ) by default. =)

Additional information

• Would you be willing to help implement this feature?

[kalix127]

I’d like to help fix it, but I could use a bit more info:

1. Could you share a clearer screenshot of the issue with the title’s state position?
2. If possible, a quick code snippet of how the titles or sidebar are handled would help me understand the issue better.

I’ve tried reproducing the issue on my end with the same icon and text, but I didn’t notice any problems. Maybe I’m missing something.

Let me know, and I can start working on this.

[Ast3risk-ops]

I’d like to help fix it, but I could use a bit more info:

1. Could you share a clearer screenshot of the issue with the title’s state position?

2. If possible, a quick code snippet of how the titles or sidebar are handled would help me understand the issue better.

I’ve tried reproducing the issue on my end with the same icon and text, but I didn’t notice any problems. Maybe I’m missing something.

Let me know, and I can start working on this.

I've noticed it with the official site on smaller screens (on components > package manager)

[kalix127]

I found the problem, and it doesn't seem like a real or actual problem.
There are 2 reasons:

1. Users are not very likely to browse docs on mobile.
2. Even if a user is on mobile, they must have a screen smaller than 290px, which is really unlikely nowadays.

That said, it is fixable but... is it really worth it?

[Ast3risk-ops]

I found the problem, and it doesn't seem like a real or actual problem. There are 2 reasons:

1. Users are not very likely to browse docs on mobile.

2. Even if a user is on mobile, they must have a screen smaller than 290px, which is really unlikely nowadays.

That said, it is fixable but... is it really worth it?

Speak for yourself, plenty of people browse the internet on mobile (especially in places like China). That said, this is still a really small problem.

[YasinSpace]

As you mentioned, the issue is minor and small! However, as you can see, I am on the desktop, and when I increase the submenus, they are displayed correctly in normal mode. But when the mouse hovers over them, they turn red. This hover effect has become extremely thin, and unlike the others, there's no extra space around it for aesthetic purposes. This happens even when there's some protrusion, and in the first image I sent, I was on the desktop, not on mobile! You can see that the word "Google Dorking" has clearly protruded.

VS.

[kalix127]

it makes sense.
If I have time later I'll try to fix it
(initially I didn't think about the fact that a user can potentially have infinite sub-menus)

[kalix127]

@YasinSpace I'm working on it now, i'll open a PR soon.
Obviously by greatly increasing the size of the sidebar, it becomes almost mandatory to remove the "toc" section on the right otherwise there is very little space left for the docs themselves.

Ignore the item names and section, I simply pasted the sections to simulate many sub-menus.

[Ast3risk-ops]

@YasinSpace I'm working on it now, i'll open a PR soon. Obviously by greatly increasing the size of the sidebar, it becomes almost mandatory to remove the "toc" section on the right otherwise there is very little space left for the docs themselves.

Ignore the item names and section, I simply pasted the sections to simulate many sub-menus.

Which means this is more of an issue with organization than anything else. If you have that many subsections you may need to reorganize your pages. (Folders with a _dir.yml will appear above the pages and are better for organizing).

This should be a choice or conditional.

[kalix127]

Yes of course it's optional, that's a new prop to the aside in the app config.

[Ast3risk-ops]

VS.

Basically, I'm just saying this could be organized better (still a good idea to add the option)

[kalix127]

Do you have any suggestions?

With TOC:

Without TOC:

I think this solves the problem presented by @YasinSpace , if you want to have 20 levels of indentation you will have tradeoffs obviously.

[Ast3risk-ops]

Do you have any suggestions?

obv. introduction should be a root-level folder.

The Methodologies section seems to be their attempt to create section index pages (which the theme should have, but doesn't) and should be reworked with less sections (i.e. do we need to specify pentesting methodologies under methodologies when we only discuss pentesting?)

edit: there's a reason the official docs do not use many subfolders, they're organized properly.

[kalix127]

Having introduction as root-level is ok, but the problem remains. You have only removed 1 level of indentation no?
I hope I didn't misunderstand

[Ast3risk-ops]

Having introduction as root-level is ok, but the problem remains. You have only removed 1 level of indentation no? I hope I didn't misunderstand

It's possible to remove more by cutting out subfolders. I explained we can cut out methodologies for pentesting as well. (methodologies too since that would be a root-level folder)

That would likely be enough to fix the issue (still nice to have that option tho).

[kalix127]

Yes, I understand the meaning and I agree that it is better, but I don't have the time to do it now.
In the meantime we can use this new option, then we'll see.

[Ast3risk-ops]

Yes, I understand the meaning and I agree that it is better, but I don't have the time to do it now. In the meantime we can use this new option, then we'll see.

You didn't make the site? The OP did.

[kalix127]

No i didn't

edit: ok no, maybe it makes more sense to wait and do it as you say.