The bare bones version on the Codex uses classes from the editor on the front-end as well as the screen-reader-text class.
I talked about the screen-reader-text class in my earlier post, Accessible Links by Handbook, and it's used in variety of places including skip links, read more links, post pagination and more.
WordPress will apply class to your content.
The reason why I used to wipe style css was I did not want the styles to interfere with my custom styles.
If this sounds like you, I recommend looking into starter themes and WPShout posted great article about child themes Child Themes, Template Heirarchy and One Sanity Saving Hack..
In Underscores theme for example, their styles css has the bare bones version we're talking about now, and includes classes for clearing, widgets, gallery and even Jetpack's scroll.
Anyway, I also would wipe style css because when using Sass, I wanted to have my own stylesheet structure and keep style css only as reference for WordPress to pick up the theme on the dashboard..
Styling all the variations that can happen due to the user playing around with the text-editor is one of those things that slip the mind when building theme for client.
Anyway, getting off topic, and this is why I keep WordPress generated classes or ensure that there is some version of it in my custom themes.
stays working and the client is not surprised or hindered due to any customizations..
Read more
Related items:
