FYI, I personally am not in favor of using a Wiki for the entire web
site. Using it for the documentation/faq section, and theming it to
match, is a good idea, though, and what we currently do. However, as it
stands now, changing a few things in a include file changes the entire
web site, which is a change that's not easy to propogate through a wiki
with the same ease.
Ryan
(who uses a wiki for several web sites)
Robert Staudinger wrote:
>Well done!
>
>In the past however, suggestions to improve the website have sometimes
>been dismissed by maintenance concerns. It has been mentioned that if
>the site was implemented as a wiki keeping it up to date would be much
>easier.
>
>Do you have any experience with wiki skinning? Would it be possible to
>implement your suggestion as a (e.g.) MediaWiki design?
>
>Best,
>Rob
>
>On 1/9/06, Kiddo <nekohayo@gmail.com> wrote:
>
>
>>Hello,
>>I have a website prototype running for those interested... sorry if I
>>might offend anyone with its "simplify everything" approach :). Maybe
>>you've never heard of me before, I just got around here and thought
>>that the website could benefit a little love.
>>
>>http://open-source.nanokron.info/projets/abiword/
>>
>>I just hacked that together last night. The support and participate
>>sections are not done, since I wanted to ask for feedback before
>>diving into that, as I plan to merge+simplfy things again (you might
>>have noticed I did my best to kill "small" pages and create unique,
>>solid sections, in a perspective to confuse the newbie user less).
>>
>>Regards
>>Jeff Fortin ~ aka nekohayo on bugzilla and IRC
>>
>>
>>
>
>
>
-- Ryan Pavlik AbiWord Win32 Platform Maintainer www.abisource.com "Optimism is the father that leads to achievement." - Helen KellerReceived on Mon Jan 9 19:12:10 2006
This archive was generated by hypermail 2.1.8 : Mon Jan 09 2006 - 19:12:10 CET