Thanks for the PR,@JoshuaKGoldberg!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint.

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	33cf02a
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/6679ac1ec46bf20007a1094d
😎 Deploy Preview	https://deploy-preview-9024--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (🟢 up 1 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 90 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify site configuration.

☁️ Nx Cloud Report

CI is running/has finished running commands for commit33cf02a. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

Sent with 💌 fromNxCloud.

PERSONALLY I don't love having valuable content on a page that's accessible via an expandable header.
EG/troubleshooting/faqs is accessible via theFAQs menu item and that menu item is expandable.
It's a confusing UX paradigm, IMO. Cos if I click on the arrow to expand then I see no menu item for "general FAQ"s

I think that either:
a) there should only be cursory information in the link for the expandable item. eg/users and/developers just has a summary of the section. Or
b) there should be a concrete menu item for that page so that it shows up in the expanded list. EG if you click on the "Getting Started" heading it is also available as the "Quickstart" sub-item.

I personally find all the time that I click the arrow and don't find what i'm looking for - only to realise that I actually wanted to click 10px to the left on the item itself.
The UX confusion is that so many sites treat an expandable section header purely as a button to expand the section. Others also do what docusaurus does and treats it as its own menu item AND as a button to expand the section.

I hate it, personally!
One other point against it. On mobile if you click on the heading instead of the arrow (which is really easy to fat finger and do accidentally) then the entire menu disappears and you see the page. So if you were trying to view a sub-menu item you need to re-open the menu again.

I do this all the time on my phone and I hate it. For example I've done this a few times:

1. open typescript-eslint.io
2. tap the hamburger to open the menu
3. tap docs
4. the menu disappears and I'm on the "getting started" page
5. tap the hamburger
6. tap to expand the "contributing" section
7. accidentally fat-fingered it and tapped the heading instead of the arrow
8. the menu disappears and I'm on the "contributing" page
9. tap the hamburger a 3rd time
10. now I can get to the sub items

Super clunky UX - I hate it.

So I'd suggest adding a "General" item beneath FAQs which allows you to see the "general FAQs".

So I'd suggest adding a "General" item beneath FAQs which allows you to see the "general FAQs".

Following up explicitly: I did this, so that when you click eitherTroubleshooting & FAQs orFAQs, it takes you to the childGeneral page. 👍

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.17%. Comparing base(23e6468) to head(5e8c5c3).
Report is 1 commits behind head on main.

❗Current head5e8c5c3 differs from pull request most recent head33cf02a

Pleaseupload reports for the commit33cf02a to get more accurate results.

@@            Coverage Diff             @@##             main    #9024      +/-   ##==========================================- Coverage   88.17%   88.17%   -0.01%==========================================  Files         415      415                Lines       14363    14362       -1       Branches     4187     4187              ==========================================- Hits        12665    12664       -1  Misses       1381     1381                Partials      317      317

Ugh. I messed up the Git merges. Will fix this in a bit.

Edit: done, I think.

I'm going to merge this now, because it's been sitting for a while and the merge conflicts keep getting more painful 😅. I think as a followup we'll want to do two things:

• Set up url shorterner permalinks, both for shorter log messages and to make the pages more resilient to these changes:Docs: Use a URL shortener for links printed by code #9023
• Do a more general docs audit for v8