Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Documentation Strategy
11-25-2012, 12:30 PM
Post: #11
RE: Documentation Strategy
The best options I know of are:
  • Install a wiki of our choice on and make it open to public registration
  • Grant all those interested and trusted access to the wings website (wordpress)
  • Use Wikibooks
For those who know about the Sourceforge Wings Wiki, it is going to disappear at some point because Sourceforge is ending its support of Mediawiki. All the info was ported to the home page anyway.

But one of oort's comment made me think; is it better to have a single long page, or many linked pages with a table of contents?
11-25-2012, 09:18 PM
Post: #12
RE: Documentation Strategy
(11-25-2012 12:30 PM)optigon Wrote:  But one of oort's comment made me think; is it better to have a single long page, or many linked pages with a table of contents?

My vote'd be for the latter option.
(different ppl could work on partic. subjects without affecting t'other pages ...and less chance of messing up the whole lot when adding / editing content)

11-25-2012, 09:21 PM
Post: #13
RE: Documentation Strategy
It comes down to the choice of tool: Wordpress vs Wiki.
When/if you reply to this - note the tool and syntax used is very much like a wiki, so it's not that bad - is it? Biggrin

I would vote for the wiki approach, but that's from a user point of view; apart from familiarity with wikis, not much in it for me.

If you (note the 'you' Wink ) set up a separate public wiki using, say, Mediawiki, then there's the additional admin and access management to consider.
But perhaps you're thinking of Wordpress wiki plug-in. Advantages include: admin of single platform, same access control to content and same defence against spam bots etc. I think you'd still have to grant trusted access to the WP wiki.

The Wikibooks option advantages include: Its there. And wide open.
(But if the Wingswiki is set up, we must transfer and 'shutdown' the wikibooks stuff to point to new material.)

Single long page vs linked pages. ??
Isn't that like asking whether Erlang modules should be written as one long single module or written as , er, modules? Tongue
(Seriously though, why would you go for a single long page?)
11-26-2012, 01:53 AM
Post: #14
RE: Documentation Strategy
I would go for the subject per page format as well, just notice that some wiki pages end up being super long.

Looking at wikibooks again, I have only part of it linked on the home page.
Here is the parent link:

Looking at that link I am reminded of what I used to think of as blender spam. Does Further Reading about Wings3d really require reading about Blender? Tongue

A wiki is better than wordpress if we have the documentation open to be edited by the public. Wikis keep a history of all revisions, so if we get spammed, vandalised, or misinformation gets added, the page can be restored.

I like the idea of setting up our own wiki because then we can control the branding.
11-26-2012, 03:05 AM
Post: #15
RE: Documentation Strategy
Wordpress does have past revisions available, but they are viewed in html.. so not very readable.

So if we go with a wiki, then the two contenders are Mediawiki and Dokuwiki.
11-26-2012, 05:27 AM
Post: #16
RE: Documentation Strategy
Never heard of Dokuwiki before but it sounds the part; the clue is in the name. Seems a good fit.
Plus points claimed on the Dokuwiki website are ease of use and admin, better than Mediawiki. Plus the ACL list looks easier to manage. I see that they use Wikimedia's actual spam blacklists (sneaky, but why not?).

I noticed that 'Blender Spam' too. Perhaps that could work both ways Wink. But I can see why you lean towards a controlled approach to branding.
11-26-2012, 06:11 AM
Post: #17
RE: Documentation Strategy
Not to jump the gun, but I just installed MediaWiki on the wings website.

Dokuwiki intrigues me, but Mediawiki is probably more familiar to most.

No direct link from the main site yet and I haven't tested the registration either.
02-17-2013, 07:36 AM
Post: #18
RE: Documentation Strategy
I've been working on converting/updating the Old User manual to get it on to the Wings 3D site. Optigon - who should be VERY VERY BUSY elsewhere at the moment ;-) -has kindly let me in to the WordPress engine and I've started to upload some pages. Still a WIP - and a long ways to go!

At some point you may see things appearing - assuming I press the right buttons - and I'd appreciate comments and corrections. Either here or send me a private message.

I've previously tried editing material in the Dokuwiki but the response/performance was abysmal. I'm getting old, and don't have so much time to waste waiting for the next 503 error. So that's why I'm using WordPress.

05-07-2013, 01:08 AM
Post: #19
RE: Documentation Strategy
I was just looking around on and noticed how much work you have done. Thanks! I will look more closely when I have time but the bits I glanced at looked great.

05-07-2013, 05:10 AM
Post: #20
RE: Documentation Strategy

Thanks. I'm getting slower as a) the summer kicks in, and b) I realise how big a job this is!! The old manual and even your later updates don't cover the work that has been done with the plugins and other bits n'pieces that have gone into vsn 1.4.1. - let alone the changes happening in 1.5.
So there's a few gotchas along the way. But it's been a great journey along my personal learning curve. From a standing start, I even have strong opinions on Erlang now!- or Arlang as the Swedes say.

Earlier optigon was promised that I was set for finishing in February. I'm still on track - I didn't tell him WHICH February.
Any comments here or private appreciated.


Forum Jump:

User(s) browsing this thread: 1 Guest(s)