Every standard installation should come with content
Just add your ideas, on what content that could be:
- Your first steps in a wiki.
- How to run a wiki project.
- ...
Ups, where is the form for the task?
--
MartinSeibert - 14 Nov 2008 - 09:17
I'd rather not that we do that.
What you do is fill it up with content that 99% of all installer will need to delete. It will more be a pain than a help.
Imagine how it will be like to upgrade.
Instead consider making installable extensions of content that people can install via configure.
Such an extension would add a demo web with content. And only when you want it.
--
MichaelCorbett says: I think there are two issues here.
- One is to ensure a good "out of the box" experience for new users. Given that wikis are an unfamiliar environment for many people - especially given that ours is an "application wiki" - I think they need all the help they can get.
- Second issue is the one regarding being able to delete it/upgrade it/ignore it. Perhaps this second issue could be satisfied by putting the content in a separate web? I would hope so because if we rely on the user to install an extension then the chances are they won't do it.
--
MichaelCorbett - 2 December 2008 - 14:29
Closing this No Action. we deliver the FAQ application, and there are other extensions now with sample applications.
--
GeorgeClark - 14 Mar 2011