> The syntax I'm working on eliminates them,
but otherwise they
> are semantically equivalent to == sections.
Please don't do that, they happen to be very
useful.
The particular instance which springs to mind is on talk pages for
templates, to demarcate between =Documentation= and =Discussion=. Because
the "Add a comment" function, available through the "+" button, adds
comments at the "==" level, it is handy to document the template at the
start of the talk page and insert "=Discussion=" after, so that further
comments fall properly into line.
The top-level header is a part of Mediawiki syntax, even if it is not used
in many places: please don't fiddle with it without considering all possible
consequences.
Any suggestions I make about the new syntax are just that--what gets
implemented is up to the real working developers, and I'm not really in
that loop anymore. I'm sure the developers will also listen to the
overall will of the users as well.
But your particular example does not convince me that H1s are a useful
thing--the exact functionality you cite could be made to work a level
lower. If an editor thinks he wants a heading that is indistinguishable
from the article title, and that splits the auto-toc, then that editor
just hasn't properly broken his subject into pages.
--
Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lee/>
<http://creativecommons.org/licenses/publicdomain/>