I think the video suggestion is the best cost-effective.
Two issues I had from moving from 6 to 7:
1. I was used to having my own text file, so I would only compare it to yours upon updates, rather than using yours. I liked my custom settings, organization etc.
2. Sometimes the changelog would have vague information (e.g. "increased amount of time spent on panels") and I'd like to see the actual number.
1. Bring the documentation as forward as possible. At least when version 7 was the current one, I had to dig into GitHub to find the raw version of the vpk file. Sure, I could open the vpk, but it didn't have the comments, as already brought up by others.
2. Centralize the resources on one place. I'm a Discord user. I'm used to browse GitHub. I browse webpages (duh). But not many players are used to these different tools, so it can be a bit overwhelming as well. "You can download it here, ask questions there and browse the documentation over there". I know you use GitHub for hosting and Discord makes conversations quicker than a forum like tf.tv, but I believe it even burdens you to keep so many resources up to date with the changes. I think you can structure Discord to act as everything, with their fancy tree server structure and bots, and leave GitHub as nothing but backend.
3. Parallel to the suggestion of dropping the site, for example, while at it, the landing page is beautiful. Not the quickest of tours, but it does have its goals: to sell the product, I get it. But when you go to the docs (https://docs.mastercomfig.com/en/stable/) the information feels cramped. Sure, there's the left bar menu, but doesn't look inviting to skim through each item.
4. One tiny complaint I have: whenever there's an update, if I feel like there's a small chance of it affecting a specific optional file, I just redownload them all. So having a "last updated:" to the right of each module would be great.