Yeah, I went back and forth with a few different possibilities of how to do all this stuff (namespaces, subpages, parenthetical suffixes, etc), and they've all got plusses and minuses..
One thing I wanted to point out, BTW: If you have a page which has a parenthetical suffix (such as a SDK version), you can use the Mediawiki "pipe trick" to make linking to other pages in the same area easier:
For anyone who's not familiar, in Mediawiki, you can make links of the form [[foo|bar]], which will link to page "foo", but the link text will say "bar". If, however, you completely leave out "foo", but leave the pipe character ([[|bar]]), Mediawiki will automatically construct it for you by taking a page name of "bar" and:
- Tacking on any parenthetical phrase at the end of the current page's title
- Tacking on any namespace prefix that the current page has
So, for example, if the current page is "my_func (IoT RTOS SDK 0.9.9)" and you put in a link to "[[|other_func]]", Mediawiki will automatically fill that out to be a link to "[[other_func (IoT RTOS SDK 0.9.9)|other_func]]" when you save the page. (this is part of why I chose the parenthetical method for identifying the SDK in the page name, because it makes linking easier using this trick)
(I really need to make a page of editing tips and tricks for this sort of thing.. Sigh.. tack it onto the ever-growing todo list, I guess..)
In general, however, I think it's generally best to just name pages with plain, descriptive names (i.e. "Memory Map"), and then let the organization be taken care of just by what other pages link to them. That's the way most other wikis handle it and it seems to work pretty well (and it makes it a lot easier to reorganize things later if we want to). I think we probably only need special designations when it's likely that there might be multiple versions of the same (or similar) pages which need separation/clarification..
Though I'm all in favor of using the categories feature, too, particularly once things get more fleshed out..
--Alex