Dear all, thank you so much for responding to this topic in such detail. I have many, many thoughts in response to this which I've tried to formulate below... and please remember that, like you, I'm coming from a place of loving AGS. And I've been in-and-out of the community over the years so will have some very significant gaps in my understanding of where/how things are organised... so some of the things I mentioned might already be well and truly sorted.

I think there's a few key points for me, some of which people have mentioned, that instigated this whole post in the first place:
- The incredible value of AGS vs the current state of online resources for newcomers.
- Having AGS's online presence reflect how alive & current the actual development on the software still is.
- To put to bed, once and for all, this nonsensical notion that AGS is for hobbyists only.
So with those 3 things in mind, let's take a look at this diagram with my thoughts/ideas/proposals:

And perhaps in response, people can refer to these in the same way? Or mention new ones (and I can update this diagram to help further conversation).
1. Overall Organisation1a. Steering GroupI would want to start with this one, which might be the most contentious one... but to establish, firmly, a steering group, that will guide all other areas listed in this diagram. Members can put themselves forth to join the steering group and are voted in on a two-yearly basis. Obviously it's all volunteering so if someone falls of the radar, they can be replaced if they are non-responsive to any communication after a month. The steering group would:
- Make decisions on all matters related to what is listed on this diagram.
- Have final say in what happens.
I understand it's quite democratic and authoritative, but in opinion, the only way forward. I would suggest the following roles: Chairman, Community, Website, Development, Finance&PR. Five people is nice (if there's a vote, there's never a tie). The Chairman is completely the wrong title for it, since they won't be any more "in charge" of the steering group, but it's that person's responsibility to organise online meetings (Zoom, Meet, whatever) and set the calendar for the year. The Community person would look after the forum, keep in touch with the Moderators, bring forum-issues to the steering group, etc. The Website person, obviously, would lead on the website. Development is for the actual technical development of AGS (Github, setting the release calendar, etc). Finance&PR would look after Patreon/Paypal funding, engaging with Itch communities, profiling AGS on Twitter, etc etc. All the social media stuff and engagement that will help build the word on AGS further.
1b. Succession planningBluntly put: Right now, if Crimson Wizard hangs up his wizarding hat and steps away... who's going to set the next AGS release? How long would it take for things to be reorganised? If AGA wins the lottery and rides off into the sunset, who can pick up the website? If Darth Mandarb is convicted of breaking too many blue cups and put in prison, who takes on the Games in Production moderation?
You get my point. The steering group would have to give these matters serious thought. It's the internet. It's volunteering work. Love for AGS can only take people so far before fatigue sets in. Love wanes (a honeymoon phase is exactly that) and then there needs to be something else to keep things going. A community is the best thing (just look at how AGS has survived/thrived over the past few decades). But it can also hit some real lows.
1c. Design PrinciplesThe first core rule, in my opinion, for the steering group is to set firm design principles. This prevents "everything and the kitchen sink" thinking and shapes a vision for the future of AGS. Some design principles can be, as an example:
1. We will refine and update the UI for AGS. But we will not move away from the core layout with the right-side menubar.
2. We seek to have AGS as accessible for all users interested. No one is more important than the other. We're an open source community where everyone can pitch in.
What I'm trying to say here is that these guiding principles relate to how AGS is designed & shaped. Good principles travel. They ensure the steering group stay on track and can also say "NO" to certain requests. Or better, say "No... not yet." since priorities will stem from good principles. Which we'll get to later on with the Roadmap.
2. Website2a. Front pagesAs Babar rightly pointed out, from a new user perspective, the website gives the impression that AGS isn't actively developed anymore. Through no fault of anyone, so much stuff is outdated. I think the problem is that so much of the site design is closed-source and needs some serious "fresh starts" to stay more nimble. And whether that's with Wordpress (the tool I'm just personally most comfortable with) or with something like Jekyll (which I like, since it's open-source and links directly to Github pages)... the more we choose an established open-source development project that's been around for a long time, the more we're likely to future-proof ourselves. And with something like Jekyll, we also make sure that the actual website content shifts into the open source domain.
2b. Wiki / ManualWhether we call it a wiki or a manual - having one place to go to for a manual would be best. The wiki's outdated, the online manual is improving, the ags-help.chm file that comes with the installation is still my personal go-to. It would be so, so much better if all of these just went to one place and one place only. Even if that means the .chm file is taken out of the installation and all AGS does is redirect you to a web-based version of it. One thing to maintain for everyone.
2c. AGS Game DatabaseAs much as I agree that the AGS website is a very different place now than 20 years ago, it's still so nice to have a games database. But bringing it into the modern era a bit more would perhaps be a good idea as well. The way it's linked to SMF right now is helpful though, which I'll raise some thoughts on later too...
2d. Plugins / ModulesThey... live on a webpage? On the forum? Or? I propose again, it's through a wiki-like setup that the official repository is kept up. The individual pages there can link to the individual forum topics. But with a good "added on", "age" and "last updated on" area there, with an automated message saying "warning, not been updated for 6+ months" will also alert people to the fact this particular one's probably not going to work anymore... The more we can have an automated upload/managing system for this, the better. The forum can be a place for discussion, but shouldn't be the repository for plugins / modules.
2e. Donation systemI'm not partial to Patreon. Or Paypal. But having both would be great, since I honestly do feel we can draw in more people to support AGS. And we
can have a think about what we do with the money. It can even be (pie in the sky thinking) similar to Godot, where we can employ people to actually write manual stuff or work on a MacOS / Linux / Android / iOS / whatever port.
2f. Main News sectionI do think a friendly "hello everyone, here's an update" message on the main website every few months or so is more than enough. But as a landing page for new people (and for SEO) it will definitely help to keep things alive.
3. Community3a. AGS ForumsI'm well aware the AGS community is active in many different places. However, "we" don't own any of the other platforms, as far as I'm aware. The forums however, are "ours". Having a look at the forum architecture, it seems to be SMF and not phpBB as someone mentioned earlier. I'm not too versed in the difference, but I see that phpBB is actively maintained (and had a plugin like BridgeDD for Wordpress to keep single-sign-on active, for example). SMF seems to be more niche so perhaps a transfer from SMF to phpBB at some point would be worth exploring.
I would also argue it'd be great to set up a "Archive" area on the forums and any topic over the active age of 1 year gets moved there. It would clean up a lot of the "old" and make space for the "new". Right now I feel the forums are an absolute treasure trove of information, but one does need to put on their spelunking hat to find anything. And whilst I love to play Indiana Jones & the Fate of Atlantis... during my actual life, archeology on a forum isn't really my hobby.
4. AGS Development4a. Bug FixingAGS Development, in my opinion, at its most basic level, sits in two different areas: bug fixing & future development. Bug fixing is pretty much a "Issue tracker" thing on Github as far as I'm concerned. If people have issues with AGS, that's where they should post it. Not on the forum. Again, github is where AGS is being developed/maintained, so let's make that the place where these things go.
4b. Future development via a RoadmapA core task for the steering group: establish a roadmap. But always be flexible depending on how things pan out. Based on the core principles set out earlier, the roadmap should be filtered out from there. This means that there's no longer that very tiring whiplash effect for core development (which I think is mainly Crimson Wizard as far as I can see?). Random suggestions pop up all over the forum and the more we can help guide these suggestions to the github Issue Tracker, again, the better. This can then be a moderator-task or stock reply. "Great idea, post it on github. We'll put it on the roadmap."
The roadmap consists of big milestones, with future version, but also minor additions / changes. And also, as decided by the steering group, fridged/shelved developments. Why? Because AGS can't be everything to all people. And it shouldn't be, since the field has changed significantly over the past few decades. By having a clear vision, guiding principles and a defined roadmap, there's clarity as to what AGS is and will be. Which can only bring a lot of peace of mind and as we work on clearer documentation / guidelines on the main website, can only help bring new people in. The whole onboarding thing for volunteers is such an important part to keep our community vital.
------------------------------------------------
I think that's my soapbox over and done with! Again, if people want to add different things to the diagram (for example, you want to discuss "3b. Some other community stuff Hobbes isn't aware of" then please do! I'll update the diagram).
I think personally speaking I would be more, more, more than happy to help out anywhere in 1-3. I just don't know how to program software, so 4 is not my area of expertise at this point in time. Gathering some more feedback on these points, at this point in time, is important. Judging by everyone's very positive engagement in this thread, I think there's so much love and life in this community that we can only improve that with these ideas.