http://www.google.com/search?q=content+editor+web+parts

there is stuff on the net!

If you haven't, it's a must-read for the SharePoint developer/admin.

I think my favorite trick is using it as a style sheet overrider.

A better question would be: Can the group share the difefrent type  of
customizations that they have used content  editor for?

If it helps, I've also used the CEWP to create the HTML form elements, DHTML/JavaScript and CSS to create a custom Boolean search page to hit the SPS Search page with a custom "where" clause.

IMPORTANT: Be sure to consider how to make CEWP type  changes
maintainable by doing one of the following (from memory):

1. Link to a single, common file rather than embedding the code in the
CEWP
2. Consider upgrading from an instance page to the direct-mode page (be
careful to position the CSS and JavaScript in the proper place in the
page). Also note that customized (unghosted) pages will not be affected.
3. Consider upgrading from an instance page to all pages in your site
definition using attributes of the Project element in the ONET.XML file.
Customized (unghosted) pages WILL be affected.
4. Consider upgrading to a Farm level solution.

See my blog for detailed instructions and examples.

Your question should really be "What can't the CEWP do?". ;

Basically, the Web Part was designed to add HTML to a Web Part Page.
This gives you the ability to add any kind of static text that you want
in any format that you want. What I discovered was that although you
cannot have a <Form> tag lots of other tags are also supported.

So, you CAN have <script> tags and you CAN have <style> tags. This opens
up a world of opportunity to apply CSS and JavaScript to the page to
effect how the page renders. Since these technologies cascade (use the
attributes scoped closest to the rendering) and the CEWP is placed on
the page AFTER all other CSS and JavaScript are defined, you can have
significant client-side impact on nearly every aspect of the page.