Prebundled wikis are definitely something useful to have. Something to avoid the terror of staring at all the recipes, some of which duplicate and/or conflict, trying to figure out which you need.
I'd say still have new users download and install the core first, but don't edit config.php or add any recipes. This emphasizes that they're still using the core wiki. Then they download and install the bundle, which includes a bundle-config.php. Similar in purpose to sample-config.php, but setting the defaults appropriate for the use. Still explain each line, but if they change nothing but the stuff labeled Important, it will work for the advertised use. List what recipes are included and briefly what it does. That way, when they're ready to do more customizing, they know what they've got. Include a skin or two that works with the bundle. Many of the skins out there (including mine) work for their purpose, but aren't fully compliant -- another frustration they don't need in the first hour. If it's not a fully-tested setup, say so up front. The audience for these bundles will be newbies. A bit nervous, easily scared off if a beta release, well, turns out to be beta. If anyone has one, or part of one, add it to the Cookbook/ListOfBundles page. My two cents. Sandy _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
