How about simply using the fact the wiki is currently in a subdomain,
and having a simple (few page) static site which looks a bit less
intimating that serves out of the root (
http://paparazzi.enac.fr/).
What it is, how to get it, how to build it, what it looks like (maybe).
Something like
http://git-scm.com/, or the rails
site (
http://rubyonrails.org/)?
That way, the manhours required are much less, the initial impact will
be improved, the manager will be impressed, the engineer/student only
has the click the wiki (or documentation) link, and everyone is happy?
Cheers,
--G
On 03/05/10 15:25, Chris Gough wrote:
So I'm just a superficial decision? Ouch. :)
Whoops, sorry, I didn't write that with a capital B but "hyperbole"
might have been a better word to use :).
Chris Gough
Buzz
On 05/03/2010 05:54 PM, Chris Gough wrote:
...
appealing to people who make superficial decisions (high impact web
sites, persuasive spin, scalable training/support, buzz).
...
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel