I noticed this in your iOS implementation and immediately liked it better. This is an unquestionable improvement over the current naming but let's try to think if there's even better names in light of all the modules identified in the audit. If not, I'm all for these names! Way to go!

@Mhurd, for example, what should we call the transform for lazily loaded images? I was thinking LazyImageTransformer. I kind of like the idea of using a Transformer suffix on everything or at least a common suffix of some kind since we have so many transforms.

@Niedzielski

What if we just name the files by noun, then the functions themselves are the verbs?

Then it reads really nicely. For example, on iOS it would read like this:

wmf.links = require('wikimedia-page-library').links
wmf.paragraphs = require('wikimedia-page-library').paragraphs
wmf.images = require('wikimedia-page-library').images

...and...

window.wmf.links.hideRedlinks( document );
window.wmf.paragraphs.moveFirstGoodParagraphUp( document );
window.wmf.images.widenImages( document );

@Mhurd, I like it! What do you think about keeping the modules tho? Like:

const paragraphCollapseTransformer = new transform.paragraph.ParagraphCollapseTransformer()
paragraphCollapseTransformer.transform(document)

const paragraphRelocationTransformer = new transform.paragraph.ParagraphRelocationTransformer()
paragraphRelocationTransformer.transform(document)