I have had some experience both with Google Sites and with Wikispaces. Wikispaces is used extensively by educators with children at the primary and secondary school level and offers collaboration and commenting tools for members but there is no way to keep selected content private in the free subscription for a publicly accessible site. A second subscription could be set to private and pages copied over. The free subscription provides 500MB capacity. A relevant example is my SQLite Tools for RootsMagic wiki at http://sqlitetoolsforrootsmagic.wikispaces.com/ . It is set up as a wiki; there is an option for a basic website, edited like a wiki - have not tried it. (BTW, that's where I have posted my RMpi utility for massaging a TMG GEDCOM into better shape for RootsMagic to digest). (and needs some updating... keeping menus and structured tables of content up-to-date is a chore) Google Sites is more powerful in some ways and maybe more of a learning curve. While restricted to 100MB for a free site, you can tie into GoogleDrive and Google+ Photos (15GB). I admin a public and a private Google Sites for our local genealogical society, the private one also links to Google Forums (albeit rather loosely). I have yet to get anyone to collaborate! Google Sites requires a Google Account (can be tied to your non-Google email as the primary email) for membership; with a Google Account you can access all things Google, more or less, with one sign-in. My public Google Site is at http://www.lakeshoregenealogicalsociety.ca/ (and needs some updating...) Good luck with your research and testing... Tom > *From:* Barbara Zanzig <bzanzig@gmail.com> > *Subject:* [TMG-REFUGEES] Collecting our wisdom > *Date:* Sun, 31 Aug 2014 10:30:09 -0700 > This deserves a new subject line. Barbara L. has given much food for > thought. See my comments interspersed below. > > > > On Sun, Aug 31, 2014 at 9:46 AM, Barbara Levergood <levergood@att.net> > wrote: > > > >> You make a good point about vetting information--we want an archive to > be > >> accurate, so perhaps we develop it privately and then publish an edited > >> document (using the term loosely) rather than publishing as we go along. > >> > > > > Good idea. That means controlling access to the unpublished version. > Would > > you be willing to do that? > > Yes, since I administer this group I have access to subscriber emails here, > and I'm willing to coordinate between here and a wiki/website/whatever. > > > I think Google Sites might do what we need--there's a blogging area, a > >> files area--it has templates for various kinds of websites, including a > >> wiki. It can be restricted access--I suspect much as one subscribes to a > >> mailing list or a Google group. After we've cleaned up our notes a > little, > >> I imagine we could make it public access, or we could publish it as > edited > >> articles here on this mailing list for future reference.. > >> > >