What Has It Got in Its Pocketsess?
Now is a good time to prepare customers for Pockets eventually being left by the wayside. Yes, it'll be ages before they're fully gone, but since they won't load at all on the new layouts, I honestly think its in our customer's best interest to start migrating away from them now. And I think support can start a culture of change with our customers long before Implementation needs to have an official project to get everyone to finally abandon them.
I've already begun this work with regards to Custom HTML Pockets. Sometimes by subtly changing my language, other times by being very up front about the situation.
For example:
Refer to placing code in Custom HTML pockets as a work-around.
Encourage customers to place any site-wide JavaScript in their style guide, not in a pocket and explain that this will ensure the code will run site-wide (since Pockets already don't load on KB, Search, and Groups pages).
Encourage customers to set their font via the style-guide editor and not CSS placed in pockets. If they want to use their own font files, that's great - they just need to link to a font descriptor file (this is basically CSS) they create themselves.
Hype the heck out of the layout editor and the power this will provide customers to fully customize pages on their site.
Mention that the new pages created in the layout editor will be faster, more secure, and more stable.
Explain that widgets will be replacing pockets on the new layout pages and will be self-contained, meaning any CSS or JavaScript you place in them will not be able to affect the page as whole.
Explain that all of these changes are being done in the interest of stability, security, and performance.
Stress that it'll be a long while before Pockets are taken away. But if they want to use the new layout editor (which will eventually allow them to fully customize every page on their site), pockets won't work on those pages anyway, so it's good to plan ahead.