Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: NOF to DreamWeaver

  1. #11
    Leslie Allan
    Guest

    Default Re: NOF to DreamWeaver

    Thanks for the new comments that are coming in about moving our site
    www.businessperform.com from NOF 9.1 to DreawWeaver.

    Yes, the site has a lot of links and yes, many pages are overcrowded. And
    yes, we have a professional designer redesigning the site. But with 350+
    pages, I'm looking for an efficient way to move the core content from our
    current site to DW.

    Imagine creating 350+ files names in newly created directories. Imagine
    copying and pasting 350+ titles and metatags. Imagine copying over thousands
    of image attributes (alt, title) and thousands of hyperlinked urls and <a
    href> attributes. And then imagine paying someone do all of this grunt work.

    What if I can get NOF 9.1 or NOF 11 to output reasonably clean code for each
    html file, code that can then be imported into DW. One option I think worth
    considering is stripping our NOF file to the bare bones unique content for
    each page. This means deleting the master borders, setting site style
    attributes for p, headings, etc to their defaults or zero and deleting
    ancillary adverts and other "clutter" on each page. This would strip out
    bags of JavaScript and nested tables, leaving basically one main text box on
    most pages. The whole site structure with stripped down htmls could then be
    imported into DW and reworked from there.

    Does this sound like I'm dreaming or could this be the way to go?

    Les


    "Leslie Allan" <lesvic@optusnet.com.au> wrote in message
    news:g4husj$b0n1@flsun90netnews01.netobjects.com.. .
    > I'm planning on moving over to DreamWeaver. My 350+ page site is in NOF
    > 9.1 (with lots of nested tables). I'm moving to DreamWeaver to get lean
    > and mean code with css positioning and to get total control over the code.
    >
    >
    >
    > Is it better to upgrade to NOF 11, convert to css based layout, publish
    > and then import into DW compared with biting the bullet and basically
    > starting from scratch in DW? What do you think?
    >
    > Les
    >
    >




  2. #12
    Garret Mott
    Guest

    Default Re: NOF to DreamWeaver

    > Does this sound like I'm dreaming or could this be the way to go?
    >


    It is "DreamWeaver", isn't it?

    Sorry - it was there & I just had to ;-)

    Garret


  3. #13
    Steve Thackery
    Guest

    Default Re: NOF to DreamWeaver

    > Imagine creating 350+ files names in newly created directories. Imagine
    > copying and pasting 350+ titles and metatags. Imagine copying over
    > thousands of image attributes (alt, title) and thousands of hyperlinked
    > urls and <a href> attributes. And then imagine paying someone do all of
    > this grunt work.


    Point well made. But this shows to me that you aren't really thinking in
    terms of a ground-up redesign. More like a new coat of paint and a polish.

    Nothing wrong with that, of course!

    SteveT


  4. #14
    Nancy O
    Guest

    Default Re: NOF to DreamWeaver

    http://www.massimocorner.com/
    Productivity > Tag Stripper
    ------------------------------------------
    I just discovered this free DW extension from Massimo Corner. It's a quick
    way to remove deprecated tags from your old web pages. Like table, font,
    td, tr. Tested on an NOF8 page for insertion into a new site. It won't do
    it all for you, but it provides a good start for stripping out unwanted
    junk. And it will do an entire site or folder in a few seconds. I used one
    page only for testing.

    http://www.notetab.com/index.php
    NoteTab Pro
    -----------------
    NoteTab Pro will further strip your code to bare bones. It can do this
    while preserving URLs. You end up with a zillion clearpixel or spacer.gifs.
    But these can be removed with minimal effort using global find and replace.
    Another great feature in NoteTab pro is the ability to convert upper case
    html to lowercase xhtml. A Huge timesaver. And if you use shortcut keys,
    you can strip 350 pages very quickly.


    --Nancy O.
    Alt-Web Design & Publishing
    www.alt-web.com

    "Leslie Allan" <lesvic@optusnet.com.au> wrote in message
    news:g4p9gk$9ut1@flsun90netnews01.netobjects.com.. .
    > Thanks for the new comments that are coming in about moving our site
    > www.businessperform.com from NOF 9.1 to DreawWeaver.
    >
    > Yes, the site has a lot of links and yes, many pages are overcrowded. And
    > yes, we have a professional designer redesigning the site. But with 350+
    > pages, I'm looking for an efficient way to move the core content from our
    > current site to DW.
    >
    > Imagine creating 350+ files names in newly created directories. Imagine
    > copying and pasting 350+ titles and metatags. Imagine copying over

    thousands
    > of image attributes (alt, title) and thousands of hyperlinked urls and <a
    > href> attributes. And then imagine paying someone do all of this grunt

    work.
    >
    > What if I can get NOF 9.1 or NOF 11 to output reasonably clean code for

    each
    > html file, code that can then be imported into DW. One option I think

    worth
    > considering is stripping our NOF file to the bare bones unique content for
    > each page. This means deleting the master borders, setting site style
    > attributes for p, headings, etc to their defaults or zero and deleting
    > ancillary adverts and other "clutter" on each page. This would strip out
    > bags of JavaScript and nested tables, leaving basically one main text box

    on
    > most pages. The whole site structure with stripped down htmls could then

    be
    > imported into DW and reworked from there.
    >
    > Does this sound like I'm dreaming or could this be the way to go?
    >
    > Les
    >
    >
    > "Leslie Allan" <lesvic@optusnet.com.au> wrote in message
    > news:g4husj$b0n1@flsun90netnews01.netobjects.com.. .
    > > I'm planning on moving over to DreamWeaver. My 350+ page site is in NOF
    > > 9.1 (with lots of nested tables). I'm moving to DreamWeaver to get lean
    > > and mean code with css positioning and to get total control over the

    code.
    > >
    > >
    > >
    > > Is it better to upgrade to NOF 11, convert to css based layout, publish
    > > and then import into DW compared with biting the bullet and basically
    > > starting from scratch in DW? What do you think?
    > >
    > > Les
    > >
    > >

    >
    >




  5. #15
    Leslie Allan
    Guest

    Default Re: NOF to DreamWeaver

    Thank you everyone again for your input. It looks as if I was stressing out
    for nothing. We can retrieve the title and metatags quickly by copying the
    entire <head> area and pasting into DW code view. Link and img and
    attributes are all copied over when you copy a block from a browser into DW
    design view. It's still a massive amount of work, but it is nowhere near as
    bad as I envisaged.

    Les


    "Leslie Allan" <lesvic@optusnet.com.au> wrote in message
    news:g4p9gk$9ut1@flsun90netnews01.netobjects.com.. .
    > Thanks for the new comments that are coming in about moving our site
    > www.businessperform.com from NOF 9.1 to DreawWeaver.
    >
    > Yes, the site has a lot of links and yes, many pages are overcrowded. And
    > yes, we have a professional designer redesigning the site. But with 350+
    > pages, I'm looking for an efficient way to move the core content from our
    > current site to DW.
    >
    > Imagine creating 350+ files names in newly created directories. Imagine
    > copying and pasting 350+ titles and metatags. Imagine copying over
    > thousands of image attributes (alt, title) and thousands of hyperlinked
    > urls and <a href> attributes. And then imagine paying someone do all of
    > this grunt work.
    >
    > What if I can get NOF 9.1 or NOF 11 to output reasonably clean code for
    > each html file, code that can then be imported into DW. One option I think
    > worth considering is stripping our NOF file to the bare bones unique
    > content for each page. This means deleting the master borders, setting
    > site style attributes for p, headings, etc to their defaults or zero and
    > deleting ancillary adverts and other "clutter" on each page. This would
    > strip out bags of JavaScript and nested tables, leaving basically one main
    > text box on most pages. The whole site structure with stripped down htmls
    > could then be imported into DW and reworked from there.
    >
    > Does this sound like I'm dreaming or could this be the way to go?
    >
    > Les
    >
    >
    > "Leslie Allan" <lesvic@optusnet.com.au> wrote in message
    > news:g4husj$b0n1@flsun90netnews01.netobjects.com.. .
    >> I'm planning on moving over to DreamWeaver. My 350+ page site is in NOF
    >> 9.1 (with lots of nested tables). I'm moving to DreamWeaver to get lean
    >> and mean code with css positioning and to get total control over the
    >> code.
    >>
    >>
    >>
    >> Is it better to upgrade to NOF 11, convert to css based layout, publish
    >> and then import into DW compared with biting the bullet and basically
    >> starting from scratch in DW? What do you think?
    >>
    >> Les
    >>
    >>

    >
    >




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •