Hey Brian -- Dana here (my old @danagilliann is no longer accessible) 😄 I'm happy to start working on this. I can start of with

I propose that we eliminate the "Core IO and DSP" top-level heading, and replace it with the following:

• Signals (includes load, stream, resample, and any signal generators and helper utilities)
• Spectral representations
• Magnitude scaling
• Unit conversion (time, frequency)
• Music notation
• Pitch and tuning
• Harmonics
• Phase recovery
• Miscellaneous (collects current misc + frequency range generators)

👋 Thanks @dana-gill , that'd be great!

I do have to admit: Building the documentation is not very easy since the documentation for it was a bit scattered 😅 Would it make sense to propose the following issues?

1. Have a Contributing section within the sidebar. I think the easiest would be to just link it to the Contributing Page on GitHub. Maybe it could be converted to .rst some time in the future.
2. Reference Compiling Documentation in the Contributing Page that way there's a clear path for those working on the documentation. I thought about moving the content of the Compiling Documentation into the Contributing Page, but since the Makefile does more than build the website, I think it's fine staying there

Let me know what you think :)

Building the documentation is not very easy since the documentation for it was a bit scattered 😅

Yeah, I know, sorry for that! It's a complicated process because we need to maintain historical doc builds, and readthedocs isn't viable for us due to the computational overhead of running all of the examples.

Have a Contributing section within the sidebar. I think the easiest would be to just link it to the Contributing Page on GitHub. Maybe it could be converted to .rst some time in the future.

If there's a way to auto-include the doc, rather than linking or converting it, that would be better. Github wants it to be CONTRIBUTING.md (though other formats might be supported) so that it's discoverable and checks off the community guidelines box.

2. Reference Compiling Documentation in the Contributing Page that way there's a clear path for those working on the documentation. I thought about moving the content of the Compiling Documentation into the Contributing Page, but since the Makefile does more than build the website, I think it's fine staying there

Yeah, that's a good idea. It could also be expanded a bit to cover the doc linting and link checking we added to the CI so that people can run that locally if they want.

Hi @bmcfee! I created a draft PR #1801 with a preview of a possible solution to restructure the documentation side bar. Before I completely proceed with a full makeover of the sidebar, could you let me know if the general idea was what you had in mind? Here's what Phase Recovery looks like, for example:

Thanks! 🌻

👋 @dana-gill sorry this got buried in my notifications (I'm phasing back into full-time this week). But yeah, this looks like what I had in mind - thanks!