Wrapping text around images takes care of itself since the images are set to float either left or right in the stylesheet and given a suitable margin and padding. When you want to insert an image into a div you would add an image tag like this...
<img class="floatimgleft" src="url to the image file" alt="alternative title" height="300" width="450" />
... and the text will flow around it to the right.
If you need to break the text and have the image between it and the next paragraph, you place it in a div which is center aligned...
<div align="center">
<img src="url to the image file" alt="alternative title" height="300" width="450" />
</div>
It doesn't get much simpler than that and the HTML file is a lot faster loading because you don't have all that posotioning data the apps like iWeb need to add just to allow you to drag and drop.
This site has examples of basic html and its corresponding stylesheet. This page shows a basic single column layout...
http://www.maxdesign.com.au/articles/css-layouts/one-fixed/
The main reason that I decided to use a code entry style editor and against using Flux is that web design is changing towards mobile designs which need to be very efficiently coded. Apps like iWeb can't do this. With Flux you can but not if you use its drag and drop features and fall for its ability to add all these inline styles!
When you move on to designs using frameworks - which appear to be the way of the future - all the code for several pages is in one html doc. Imagine what its like trying to find anything in these docs if you are adding all the inline styline and positioning info!
Those who talk about switching to RapidWeaver, Sandvox, Freeway etc or importing iWeb built sites into code entry style software have got their heads stuck in the sand and are going to wake up one day and find that hardly anybody is visiting their dinosaur website.
Hopefully, some day soon, an application will appear that makes it easy to create websites using the new javascript frameworks but, until then, you either get left behind or have to get your brain cells around some code. You can produce good basic websites with very little knowledge of code and they will be far more efficient than anything a template based editor can achieve.
I did consider using Flux but decided that it was easier to learn how HTML and CSS fit together than get to grips with the way Flux works. On the other hand, Old Toad finds he gets on way better with Flux. Others may not find either suitable but they won't know that until they try.
Here's an example of a mobile website design adapted to appear OK on computers...
http://www.ezmacwebdesign.com/jquery-mobile-test/index.html
If you had told me a few months ago that I could built a site like this I would have written you off as being as insane as me!