When designing a web page, measurements are performed in pixels, which is the number of color placeholders, but not a measurement. Image resolution baffles many, many graphics designers, so please let me give you more of an answer than your question
When you say Adobe Fireworks “uses 72 dpi for the web”, em, it does and it doesn’t. Image resolution is only relevant to design work when you’re printing something—in the real world, we express image resolutions as “so many color placeholders (pixels) per “how many real world units (inches)”. A pixel has no fixed size because it is not a unit of measurement—it’s a placeholder and Adobe Systems chose 72 as the default resolution because traditionally figuring out text, as measured in points, is easier to reconcile when pixels and points are evaluated according to the same scale. In other words, if there are 72 points to an inch, and 72 pixels to an inch, the math becomes easy.
But image resolution is completely irrelevant for web work. An image that is 300 pixels wide onscreen, is 300 pixels wide on everyone else’s screen. I’m attaching a basic template for the Web in CDR file format here. It’s geared for today’s screen resolution, it’s 955 pixels wide, and what is left on the right and left sides is “padding” within which the page is floated.
People use what they use to design webpages, and I’m sure many, many folks use CorelDRAW. However, a “web page” isn’t all that meaningful unless you have a good foundation, an HTML structure that allows customization, HTML 5 is basically available now and web browsers such as Google Chrome already can read HTML coded pages, and unfortunately, far too often, web designers believe the job is done after they’ve posted neat columns of text and some images. That’s naïve: a website is supposed to serve a community function beyond eye candy, and all the pretty graphics on earth won’t make a website successful if the underlying code is poorly written or broken.