MediaWiki is primarily developed for sites like those
Wikimedia and Wikia, where either the whole site is viewable, or almost
none of it is.
I understand that, per my initial post.
As far as I know, there is no effort, besides any
development work on the various existing extensions, that is working
toward such restrictions.
Right, I just wonder why so many extensions are developed, which, in
fact, do not provide what they are written for. If all these people
would combine their effort to fix MediaWiki, a more acceptable result
might come out of it.
There are some efforts to make the UI code
more separate from the backend code, which could help with this, though
I don't believe that permissions is one of the main reasons for it.
Right, there are many reason for a good software design, and a good
design will make implementing permissions (and other features) easier.
fully close all the potential gaps would probably require substantial
work, and there's no guarantee that any changes to core code that may be
necessary won't be broken by updates in future versions.
A good design should not break things, at least not between minor
releases. Every serious peace of software works in some combination with
other, and they do not break each other daily.
For what you want, it would probably be better and far
easier to use 2
separate wikis - like a management wiki for the hidden stuff and another
wiki that has most of the content.
Yes, this seems a reasonable solution.
Thank you, everyone!