Comment 2 for bug 287943

If you think it's worth, you should create a blueprint with this complete specification in the blueprints section, adding screenshots and more information about each feature. This is, imo, too detailed for a simple feature request and it's definitely not a bug.

I'd like to add some comments though:
I'm working in web design and I really can't find relevant differences between working for the web in inkscape or in illustrator (keep in mind that the right comparison would be between inkscape and illustrator, not between inkscape and fireworks).
Inkscape is a vector illustration program, like Adobe Illustrator, and you'll find some issues when you work with vectors with bitmap output in mind, like pixel precision (if you don't take care of working with integer pixel units).

If you work using pixels units and export at 90 dpi as PNG you'll get a nice bitmap output from Inkscape. You can open the png file in GIMP and use the save for web plugin. If you're not happy with the antialias you can use the sharpen filter (or the refocus plugin) to get sharper results before exporting.
You can use solid pixel positions and solid pixel dimensions. Just use the numeric inputs to specify the desired integer value and you'll get an accurate conversion when exporting (remember to export to 90 dpi, not 72 or other resolutions because if you do it, you'll have to rescale the exported bitmap and loose precision).
About the limit of the blurred shapes, it has been fixed in the development versions and will be in the next stable release (now the bounding box extends to the limits of the blur, avoiding unwanted clippings).

About the text part:
You already have tools to align to text baselines.
The other items you've requested are already filed in other bug reports/wishlist items.
Anyway, there is much place for improvements in the inkscape's text tools, I agree. A well developed blueprint would be a good starting point.