Hi
Could you please explain bit more what do you mean by HTML plug-in for content editor ?
Is it that, we need to write HTML inside content finder?
And, if your aim is to use pre-filled component then please refer to this slimier forum post :- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...
//
Please refer to this Community Article:- http://blogs.adobe.com/experiencedelivers/experience-management/default-components-in-your-parsys/
// Make Component part of Template. It is pre-filled template, so when you create a page, it would have pre filled component. So all the pages create by template would have same content.
When you make changes to content of template, the changes would get reflected across the pages.
Reference links:-
http://stackoverflow.com/questions/22392147/cq5-preload-a-parsys-with-components
http://suryakand-shinde.blogspot.in/2015/01/how-to-create-page-with-predefined.html
Option 2 could be:- if you want to have it configurable on one page and reuse it everywhere one option would be iparsys, which is an inheriting parsys that traverses up the page hierarchy until it finds a component in it.
Link:- http://stackoverflow.com/questions/21053131/how-do-we-define-global-properties-in-cq5
Reference article on CF:- https://helpx.adobe.com/experience-manager/using/content-fragments.html
~kautuk
Kautuk Sahni