HTML versus xCards

[Alain Farmer]

Hello Ray and y'all,

> Yo troops,

Nice of you to join in!  ;-)

> With all this talk about the pleasures of
> working with HTML, I just couldn't resist
> sending this along...
> HOW TO BUILD A WEB PAGE IN 25 STEPS...

Hilarious but true!  ;-)

Playing devil's advocate for a moment, it could be
argued that most of these site-building steps apply
whether it's a web site or not. Selecting the images,
for example. Moreover, my approach of creating a stack
to update and manage an entire web site, given that it
is generating the HTML of a web site, is even more
work than just putting together the same site without
this site [re-]generator, but the advantages of this
extra work pay off big dividends when [unpredictable]
changes need to done, in terms of content as well as
appearance and structure. With the stack, changing the
bg image of all of the pages is as simple as changing
the content of one field (type it in and/or a "browse"
button) and then clicking on the "Regenerate this
site" btn. Very fast, very effective, no multiple
pages to change, no risk of human-error ... Pure joy!
And this is just an example, among countless examples,
of the power of managing and generating HTML with an
xCard. The web-savvyness of the xCards (with an XCMD
in HC/SC) pays off here because it means that the
generated web-pages can automatically be sent (via
FTP, HTTP) to the remote the server that hosts your
web site (e.g. if and when you are not your own web
server).

So, as you can see, it's not necessarily a matter of
completely replacing HTML with an xCard. And no hard
choices to make, either, because you can have BOTH at
the same time.  :))

I am really enjoying this thread,

Alain Farmer

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com