
The web is ALL ABOUT semantics, and if you're just using styled divs around paragraphs, sure, it'll validate, but not a search engine in the world will understand your site. There is most DEFINITELY something special about h1 - h7 tags and p tags, beyond "default styling". > I'm not sure why you put so much emphasis on the common HTML tags - there's nothing important or special about them.įirst-time poster, and I love your writing, so excuse me if this seems harsh, but WOAH. It at least seems to be well-formed (though I haven't run tests yet). No sense in trying to wedge your design into tags that don't really fit your needs.Īs for the overall quality of iWeb CSS and HTML output, it's a bit verbose but much better than what I've seen from other tools in the past. In fact, I encourage this if it fits the bill better. You're not violating any HTML spec by choosing to use generic tags (divs, spans) with custom styling. In fact, there's not much need for them when using a custom layout tool. It just so happens that they have some de-facto styling properties. I'm not sure why you put so much emphasis on the common HTML tags - there's nothing important or special about them. Text boxes are really a lot more friendly to the creator of the page. IWeb is built around the idea of resizable text boxes, which is not really what the H1-H7 tags do.

The only difference is P has some inherent styling and maybe some screen readers expect to see it (even thought they shouldn't). They're both fairly generic block-level elements. In any case, there really isn't much difference at the rendering level between a P and a DIV. Using divs instead of paragraphs? Not just ugly, totally wrongĭoes it only generate DIVs? I haven't looked. I'm guessing this because it's dependent on the dynamic HTTP requests (Ajax stuff). The main one is that the cool slideshow stuff doesn't work. No, you can export to a folder and upload the folder, but there are a few limitations. I would like to ask one question, does iWeb let you export to files as opposed to. It's so convenient that I'll probably use it at least for publishing some quick, one-off sets of photo albums and basic documents. It's not only useful to entry-level consumers, either.
#Apple iweb equivalent manual#
My girlfriend was able to take a whole bunch of photos and build a photo site without cracking any sort of manual and only very minimal intervention by me. It's most significant in the sense that it gives the average person the power to do some fairly sophisticated layouts without burdening them with any of the underlying issues. Overall, I think this is a solid first release. Most web editors have these issues, though they are a bit less pronounced in iWeb. Also, it would be nice if more of the styles were put into an external CSS file instead of all going inline. It's not clear to me why nested 5 divs with separate styling attributes can't be combined into one, but maybe the answer is there if I look deeper.
#Apple iweb equivalent code#
The quality of HTML/CSS code is pretty good, even though it gets somewhat verbose in terms of number of divs. On the photo engine side of things, a friend pointed out that some sort of search engine that looks for keywords entered in iPhoto would be really useful. There also doesn't appear to be a way to open existing HTML files, which is a little frustrating. It really seems like multiple sites should be displayed in separate document windows, but a multi-document approach might create synchronization challenges at the. I'm not sure the single window approach makes sense. I also found myself wanting a Re-apply template command - something that would perserve current content but choose another layout.

In fact, I think we also need an Add Page as Template or something of that nature. Once you've tweaked a basic template, there's a good chance you're going to want to reuse it. Next, a Duplicate Page command is desparately needed. Maybe a layer inspector or something would work here. It's too easy for one item to get "stuck" under another.

First, I need a key equivalent (tab) to cycle through all page elements. There are some thing I'd like to see addressed in an update. Creating an entire photo page and slideshow from iPhoto is ridiculously easy. It tastes similar to Flickr, but I find it easier to navigate and it's accompanied by a really nice reflection effect. iWeb seems to be pretty smart about only uploading things that have changed. Publishing to the service is incredibly easy with no need for user names, passwords and so on.
