Front end API: HTML ids

[mflorea]

@surli

And then defining a naming rule for ID that are ok to be broken in the future (e.g. prefixing them with _).

@mleduc

for new code: define a class/id prefix (e.g., xwiki, or xwiki-${moduleName}) to make explicit what is public

I agree we need a naming rule for IDs and class names to clearly mark what is public and what is internal, for new code of course (and slowly transitioning the existing code). I’m leaning towards marking explicitly the public API (i.e. have everything internal by default), as Manuel said, instead of marking the internal API. The ‘xwiki-’ prefix sounds good to me.

Going back to #editPanels, I’m OK to remove it and document the breakage.

Thanks,
Marius