[Suggestion] Implementing H1 Headings without coding

[covoxer]

It has maybe something to do with SEO, but much more with following Web Standards and using semantically meaningful HTML tags.

There is no HTML in XWD. There is no HTML semantics in XWD. You work with XWD design and WEB semantics.
On the other hand - if you are experienced enough to understand and create high quality HTML, you shouldn't use XWD for a resulting product, only for prototyping.
Once again - XWD is not there to compete by the HTML code quality with professional web design specialists. It is impossible. And if it was possible, such a product would cost about 10 times more than the most expensive web authoring tool.
If you've got a microwave oven you don't expect it to immediately produce food of the restaurant quality. Do you?

[pauland]

-

[pauland]

John, on an H1 related issue - I'm curious about how XWd handles text for wysiwyg.

I haven't really looked, but my guess is that for various font sizes used in XWD/Xtreme you can match the font size and styles in the browser just by using CSS. So, if I choose a font size of 18 in XWD, you will set a CSS font style of 18 for that text in html.

For H1 support - or any other style - the user could select text and pick a style (H1 or even perhaps one of their own choosing) and have XWD create the CSS style required (just as it does now) on html export.

So perhaps in some lifetime, XWD could have a list of styles - which might include H1.. style presets (and maybe allow users to define new styles), allow users to apply styles to selected text and on export generate the CSS for those styles.

I can't really see that it's a huge change to XWD.

Anyway, I realise it's a sensitive subject but it's only a discussion that can easily be ignored.

A great approach to dealing with unwanted requests is used by many companies and it quickly resolves the issue: "Great idea Paul, we'll add it to our list of requested enhancements for future consideration".. .. and file it in the WPB.

Paul

[covoxer]

Paul, we are walking in circles.... And this irritates. All your arguments were told many times in different forms, as well as mine. It was already stated before that styles concept may be implemented in future as is it relatively highly rated improvement on the wish list.........
How many times do we have to repeat all this again?
And yes, every next time the cycle loops I'm getting more upset and shall react as I usually do when someone asks the same question on and on - simple answer, then extended answer then louder in case I'm not heard and finally I'll start to ignore it once and for all....

[pauland]

OK, though is it just my comments or anyone raising the H1 issue at all?

[covoxer]

This issue is already discussed down to bare bones. There's nothing more to discuss. Unless someone will bring any new argument not mentioned before, there's no point of debating about it. All questions are already answered, it's enough to read this thread from the start or other threads about <h1> here.

[remi]

There is no HTML in XWD.

I know.

There is no HTML semantics in XWD.

I know.

You work with XWD design and WEB semantics.

No, I don't work with XWD designs at all, because of the lack of semantically meaningful HTML and the very limited absolute positionized layout approach.

On the other hand - if you are experienced enough to understand and create high quality HTML, you shouldn't use XWD for a resulting product, only for prototyping.

I'm very experienced and I create hand-crafted websites. But I don't use XWD for prototyping, because of the lack of semantically meaningful HTML and the very limited absolute positionized layout approach.

We are walking in circles... - we hear the same old arguments in order to learn something about the current status with the HTML export filter in Xara Web Developer and also Xara Xtreme 5.

Once again - the HTML export filter could be better, but we have to wait one or two more years for that. I can live with that, because I see no need to upgrade my old Xara Xtreme Pro 3 license in the next two years, as this is the timeframe Xara assumedly needs, in order to change their product policy (code word "developing new innovative vector functions").

We don't have to repeat all this again and again - unless you're starting a new cycle loop. Do you follow me?

Remi