On 3/23/11 1:16 PM, Samuel Klein wrote:
You could allow each biblio page to decide who its audience is. If
there is ever a conflict between a lay and a specialist audience, you
can have two sets of annotations. I'd like to see this happen in
practice before optimizing against it.
I think that is workable if the two sides don't step on each other's
toes too much. I am also coming around to the view that we should just
try it and see what happens.
* It
doesn't look like a MediaWiki. Since the MW software is so
This is easy to fix -- people who like the current acawiki look can
use their own skin.
Well, my concern is for newcomers who by definition don't have a skin
configured. What I want this this reaction:
<browse to
http://acawiki.org/whatever>
"Hey! This is MediaWiki! I know how to use this!"
<edit stuff>
But now I think the following reaction is more likely:
<browse to
http://acawiki.org/whatever>
"Hmmm, what's this?"
<browse browse>
<leave>
These small barriers to entry matter. My basic argument is that
leveraging familiarity by making it look like something people have seen
before is more important than branding.
Reid
--
I work for IBM, and sending this e-mail might be part of my job.
However, I speak for myself only, not the company.