But it’s only as good as the participating devs.
All my apps and drivers will make it to my website, and the content will be maintained but I can’t speak for others.
As @csteele says, he tried the same idea with a github based repository and received little interest from developers.
It wouldn’t be much of a ‘portal’ if other devs are not interested in putting their apps/driver info there.
I could see a portal being useful, but threads aren't terrible for announcing new apps and drivers. Ideally the the hub itself should be able to check for updates, perhaps via remote repository integration, and should be able to load relevant metadata (release notes, version info, etc.) from the app/driver repository.
Documentation and release notes should ideally stay near the source code, and developers shouldn't have to update this information in multiple places unless there's a significant benefit. Basically, I recommend keeping developer effort in mind as well as user effort when coming up with a distribution platform. The easier it is to maintain something, the more likely it will be well maintained.
I agree. Update support in the hub would be great, and threads are great for discussing different drivers and apps.
Perhaps each "App" in the App Portal could link back to the parent threads for discussion & support. I should start including that URL in the header section of my releases...
I'd presume most of us keep our code updated in GitHub (I've only ever seen that, and code copied/pasted into threads). So another link to the code (or a button that can automatically copy the text to your clipboard from github?) would be cool to see, as well.
In either case---I'd be sure to include support for an app/driver portal into whatever I release