This is rather interesting - just came across this thread and it ties in very closely with some ideas I've been having for the AmigaWiki.com domain (which, frankly, isn't doing anything much now).
Problem: There are loads of small Amiga-related sites out there with really cool information - e.g. tutorials on specific hardware upgrades, support sites for old 68k software that's still usable, historical information etc. But over time, a lot of these websites become unmaintained and at risk of being removed by the host; link rot sets in. Also, there are probably loads of members of the community who have knowledge they'd like to share but don't want to bother learning HTML and getting a server.
Potential solution: Rebrand AmigaWiki.com (or set up a new site entirely like amigasites.com) that lets any Amigan create their own microsite. It'll include some sort of basic CMS (or wiki-style markup) so there's no technical knowledge required, and users can customise the look of their site using CSS etc. Sites will all have simple domains of the form [amigawikiorwhatever.com]/[sitename] which we guarantee will stay static. It would be made clear that, in the event of the site closing down, a full backup would be made available to anyone else interested in running the service. We'd be able to offer services particularly relevant for Amigans, such as the ability to automatically download the contents of the microsite as an AmigaGuide file (this is really easy to do providing we limit sites to wiki-style markup). The main page of the site would also act as a directory for all the microsites, which otherwise might just get lost on the web. It'd also be possible for microsite owners to open up any pages as a wiki for anyone to edit.
Interestingly enough, the more active pages on the existing Amiga Wiki tend not to be the encyclopaedic articles (which are obsoleted by Wikipedia these days) but pages that would work well on the site I've described - for example:
OS4 68k compatibility list - back in the very early days of OS4, and before anyone had created a dedicated compatibility list, this was an easy way for people to see and update the list of working applications without going through thousands of forum posts
The Amiganisation of FOSS - original article by someone on ways in which AmigaOS-type features could be carried over to Linux and friends
SpamFryer - the author of this package updates this page with new rules between releases
I'd guess that some people would want greater freedom than a basic CMS can provide. So they'd be able to get a standard account like Wayne mentioned, along with a subset of the features provided to CMS users - e.g. the guaranteed persistent domain and promotion on the front page of the site.
Any thoughts?
