I suggest testing by setting window width = 1791px (e.g. CTRL+shift+M on Firefox), and then passing to window width = 1792px. So we can see that the content max width at the moment always seems ~ 800px.

Uhm - but looking at your screenshot, at looking here T15920, it seems a regression

Patch welcome, with "Ref T15920"

When reading the wiki at a resolution of 3440x1440 (34 inch monitor), there is still a lot of white space.

(Damn Phorge that auto-claims also for wontfix)

Maybe we can wontfix this. The current "workaround" D25485 by @waldyrious is just great and effectively fixed the super-confusing root problem.

The sublevels of the tree can be made hidden, and they can be revealed when clicking on a specific parent. And if the user expands the tree to a large size, then it is worth limiting the maximum size of the panel and showing a vertical scroll when the maximum is reached.

Having the wiki's tree of contents on the side would indeed be pretty nice, I gotta say. This is especially the case on the landing pages of a given instance's wiki, at least until it inevitably sprawls to be gigantic ;)

This project is now abandonware without you. 😆

Gents, you’re both nothing short of geniuses

Gents, you’re both nothing short of geniuses—fixed before I’d even blinked! Thanks. Will look at fixing it permanently in T15513.

I can reproduce, looks like the change in src/applications/conpherence/controller/ConpherenceViewController.php is the culprit.
No clue what's a correct fix, thus proposing to revert the entire commit.

Eventually please try reverting this change in your local copy:

Tip: activate DarkConsole and check requests there 👍

From checking the network requests when I load an unrelated page and the dialog appears, I can see a POST request to /conpherence/edit/1/ which returns the dialog. I've attached both the request and the response, with light redactions, to P48 and P49.

@aklapper we are talking specifically about documents that are under another document, that is, about the hierarchy of pages in the wiki.
The screenshot F3250825 just shows that the visualization of the document hierarchy is not very convenient in my opinion, and I ask if it can be moved to the side.

I now realize that this is not about hierarchy (documents below other documents) but about the Table of Contents within a single wiki page? You may want to edit the title.

What you see is 100% normal regardless of your pixel density, display size and resolution.
With a similar approach to T15920, this can be achieved. However, I think there is one disadvantage: text may be crammed with a side hierarchy, resulting in lots of newlines for documents with long titles.
You can create a task now that you are member of Trusted Contributors.

Changed the policy for file F3250825 to Public.

@vabocharov please set the view policy of F3250825 to Public.

Good afternoon!
I get it, if you go to Phriction > Welcome to the Forge Wiki, then the hierarchy of documents will be displayed at the bottom (the screenshot below is attached). You won't see this in your example, as there are no attached documents.

Hej hej and welcome! I'm afraid I cannot really follow... In my understanding the hierarchy is expressed via the breadcrumbs navigation right below the top bar and not at the bottom, at least for a screen width of 513px and more?
For example if I go to https://we.phorge.it/w/changelog/next_up/ , see the Phriction > Welcome to the Phorge Wiki > Change Log > Next Up breadcrumbs.

P.S. - useful snippet shared by Daimona from Wikimedia:

Increasing a bit the priority since this is feasible, simple to reproduce, and really frustrating in 2025.

I agree that the hover behavior could be improved. Showing only after a delay could help here, though that would make it slightly worse for the times you actually want to interact with the hover.

OK lol no, this has nothing to do with D25898. Need another task for the "Missing input descriptions"

@deric you should land this revision, right?
If you're having troubles, ask on Z1 for help or ask somebody else to land.

Uhm, right. A quick fix would be removing the margin-left: 300px; CSS rule for div.phui-document-content-outer which might invalidate related screenshots on https://we.phorge.it/w/changelog/next_up/.

Decreasing priority since this happens only if you have not any posts.

(Sorry @mturdus I didn't want to assign this to you. It was automatically assigned by sub-task.)