Add the name of the class/enum/etc in the page title

[MorganVonBrylan]

Which application is this bug report for?

Documentation

Issue description

Currently, all the title says is "discord.js", the version number, and then "discord.js" again.
This is not helpful at all when using the browsing history or when you have several tabs.

It would be much better if there were, for example, User:class | discord.js (version), UserFlags:Enum | discord.js (version), etc.

I remember that this had already been an issue in the past, and it had been fixed, so that's a regression.

Steps to Reproduce

1. Visit a page

Versions

• all

Issue priority

Low (slightly annoying)

[vaguul]

Not a maintainer, but the current website code seems to explain part of this.

In apps/website/src/app/docs/packages/[packageName]/[version]/[[...item]]/page.tsx, generateMetadata() parses the item path and then does:

const titlePart = decodedItemName.split(':')?.[0] ?? decodedItemName;

return {
  title: `${titlePart} (${packageName} - ${version})`,
};

So for a docs item like User:Class or UserFlags:Enum, the page title intentionally drops the :Class / :Enum part. Then the parent layout applies the template from layout.tsx:

template: '%s | discord.js'

That likely explains why tabs/history lose the item kind even when the route contains it. If the desired shape is closer to User:Class | discord.js (main) or User:Class (discord.js - main) | discord.js, the fix is probably in that metadata formatting rather than the doc generation itself: preserve the decoded item kind instead of splitting it off, or format name/kind separately before the layout template is applied.

A small regression test around metadata generation for User:Class and UserFlags:Enum would catch this without needing to render the full docs page.