The Script Editor Web Part (SEWP) is a damned-handy tool for front-end designers/developers. I find myself using it in the following scenarios:
- I need to quickly test CSS solution prior to rolling it into a global CSS file.
- I need a page-specific solution (okay, a dirty hack) that doesn’t deserve to be in a global CSS file.
- I need an immediate solution to a page-specific problem and, for whatever reason, can’t yet roll it into a global CSS file.
The SEWP seems almost like a gift and apology from the SharePoint development team. It’s a frank acknowledgement that a lot of things about SharePoint, especially from a UX perspective, leave a lot to be desired as well as a useful tool for fixing some of those problems.