First and foremost: a plugin that seems to hit the nail on the head when it comes to “taming WP WYSIWYG” (thanks to Stephen Cronin for the heads up on this):
“Raw HTML Plugin for WordPress” – “To prevent some part of your post or page from being processed and “texturized” by WordPress, wrap it in <!–start_raw–> … <!–end_raw–>” by Janis Elsts at W-Shadow.com
By way of context: I’ve been having an on-going exchange with Stephen Cronin in his blog about WYSIWYG being over-bearing and also I’ve put together what I hope is a pretty comprehensive resource list at codex.wordpress.
Update: the plugin’s author answered my inquiry with this:
The plugin doesn’t “tame” the editor in any way (that’s why I say that using the visual editor is “not recommended” in my post).
Actually, it only runs when a post is <em>displayed</em>. The plugin intercepts the content surrounded by the special tags and saves it in internal variables before WordPress can “prettify”. Then, after WP is done messing with the rest of the post, it adds back the “raw” content in the right places.
So the visual editor is still at large
WP-chgFontSize allows readers to change the page’s font size dynamically , storing their selection in a cookie. “It can be used as a widget or directly as a PHP call in the theme.”
13 plugins that will make WordPress into a CMS
“WP PHP 101”
“the quickest, simplest PHP tutorial around, and the only PHP tutorial written specifically for the average WordPress user, covering only the minimal amount of PHP necessary to competently modify your themes (and maybe even to modify plugins).”