Gary

I am a complete newbie to Expression (and I've really not used Front Page
much, either) so this is a very basic question.

I've worked on web sites using web-based site builders that were included at
no cost with the web hosting. One of the great features with these is the
fact that when you add a new page it automatically shows up on the
navigation bar on every page on the site. Then if you rename the page or
change the order of the pages the navigation bar changes also. My question
is, does Expression do this also or do you have to adjust these things
manually?

TIA!
--
Gary
Visit Lucy & Gary and do the jigsaw puzzle at
www.under-1-roof.com/PuzzlePage.html

Rob Giordano \(Crash\)

manually.
in FP there was that feature though, but not in EW.

--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression






"Gary" <gary@under-1-roof.com> wrote in message
news:#Ck9cDjqIHA.4716@TK2MSFTNGP06.phx.gbl...
> I am a complete newbie to Expression (and I've really not used Front Page
> much, either) so this is a very basic question.
>
> I've worked on web sites using web-based site builders that were included
> at no cost with the web hosting. One of the great features with these is
> the fact that when you add a new page it automatically shows up on the
> navigation bar on every page on the site. Then if you rename the page or
> change the order of the pages the navigation bar changes also. My
> question is, does Expression do this also or do you have to adjust these
> things manually?
>
> TIA!
> --
> Gary
> Visit Lucy & Gary and do the jigsaw puzzle at
> www.under-1-roof.com/PuzzlePage.html
>
>
>

Christoph Schneegans

"Gary" wrote:

> Then if you rename the page or change the order of the pages the
> navigation bar changes also. My question is, does Expression do
> this also or do you have to adjust these things manually?

If you have ASP.NET available on your server, the common approach
would be a web.sitemap file and ASP.NET controls such as asp:TreeView,
asp:SiteMapPath or asp:Menu. See
<http://msconline.maconstate.edu/tutorials/ASPNET2/ASPNET10/aspnet10-03.aspx>
for an example of an web.sitemap file.

Otherwise, there are some add-ins to create navigation bars, e.g.
<http://www.frontbox.de/> (in German, though).

--
<http://schneegans.de/sv/> · XML Schema Validator

Falcon42

"Rob Giordano (Crash)" wrote:

> manually.
> in FP there was that feature though, but not in EW.
>
> --
> ~~~~~~~~~~~~~~~~~~
> Rob Giordano
> Microsoft MVP Expression
>
>
>
>
>
>
> "Gary" <gary@under-1-roof.com> wrote in message
> news:#Ck9cDjqIHA.4716@TK2MSFTNGP06.phx.gbl...
> > I am a complete newbie to Expression (and I've really not used Front Page
> > much, either) so this is a very basic question.
> >
> > I've worked on web sites using web-based site builders that were included
> > at no cost with the web hosting. One of the great features with these is
> > the fact that when you add a new page it automatically shows up on the
> > navigation bar on every page on the site. Then if you rename the page or
> > change the order of the pages the navigation bar changes also. My
> > question is, does Expression do this also or do you have to adjust these
> > things manually?
> >
> > TIA!
> > --
> > Gary
> > Visit Lucy & Gary and do the jigsaw puzzle at
> > www.under-1-roof.com/PuzzlePage.html
> >
> >
> >
>

You are joking right?!
Seriously, you're not telling me that the thousands of semantic arrangements
between pages in my multiplicity of FrontPage sites need to be manually
recreated?
This alone would prevent my being able to recommend migration to any FP user
(and indeed preclude my ever recommending EW2 - this is supposed to supersede
FP2003, no? Improved standards compliance at the expense of critical
functionality - on that basis I'd better off with DreamWeaver?!!!).
What seems to be being proposed entails hundreds of man-hours work to
implement using EW2 and is quite frankly neither an efficient nor
recommendable path forward from FP2003 for any of my clients.
Ludicrous!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Cheryl D Wise

Dreamweaver does not have any automatic navigation creation tools. As a
professional I have not used the FP navbots because they are far too
limiting when based on the navigation structure. If I'm going to create a
custom navigation bar I'd rather do it in a way that works well in every
single browser out there and is not bloated. The FP webbot didn't do that.
Heck, even my husband who only maintained a user group website complained
about the navbot and how once you get beyond a dozen pages it wasn't really
up to the job.

My personal preference is to use unordered lists since this both correct
semantic mark-up and something that will work in every browser and on every
device including screen readers, cellphones and other devices. I can then
style them to be dropdowns (with nested lists), rollovers or whatever I want
using simple CSS. Okay for IE I may have to add either javascript or an htc
(dom based manipulation) in order to get them to work properly but IE is
getting better at standards support.

Using includes (whether design time like the FP include function or server
side - my preference) and/or a DWT custom navigation is so much easier and
more versatile than anything you could do with an FP navbot.

--
Cheryl D Wise
MS MVP Expression
Author: Foundations of Microsoft Expression Web
http://by-expression.com
mail list: http://groups.google.com/group/by-ex...n-web-designer


"Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
news:16C61782-9856-476E-9C41-74275D8DF887@microsoft.com...
>
> You are joking right?!
> Seriously, you're not telling me that the thousands of semantic
> arrangements
> between pages in my multiplicity of FrontPage sites need to be manually
> recreated?
> This alone would prevent my being able to recommend migration to any FP
> user
> (and indeed preclude my ever recommending EW2 - this is supposed to
> supersede
> FP2003, no? Improved standards compliance at the expense of critical
> functionality - on that basis I'd better off with DreamWeaver?!!!).
> What seems to be being proposed entails hundreds of man-hours work to
> implement using EW2 and is quite frankly neither an efficient nor
> recommendable path forward from FP2003 for any of my clients.
> Ludicrous!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Falcon42

Whilst Dreamweaver may not have any navigation management capabilities,
removing such features from FP does not make EW2 compete with it any better!!!
Agreed, I too would prefer to "do it once, right first time", however manual
implementation in the manners suggested is certainly not it for me - or
rather, it's fine providing the logical organisation of a site will NEVER
change - once you're into having to maintain such a structure/reorganise and
all of a sudden a significant overhead is introduced.
Though I grant you that the innate non-standards compliance is a significant
issue, I don't agree with your husband's view - I personally have implemented
sites having thousands of pages with no problem, so I wonder quite where he's
been going wrong?!
Don't understand your comments RE includes/DWT custom navigation - neither
of these methods quickly and easily allows you to drag, drop and
(re-)organise a site's content, no?
I had expected EW2 to minimally match FP functionality, but in this area,
EW2 presents a huge downgrade. I'm no fan of having to manually do anything
so losing such significant automation in EW2 is a "show stopper" for me.
I should note that a number of my customers are SMEs who have absolutely no
interest in doing anything technical - FP allowed me to implement a site for
them (including navigation) then hand it over entirely for ongoing
maintenance.
An hour's training for an end-user and they're able to run with it -
reorganise it - add to it - all with not a glimpse of HTML and no requirement
to learn CSS/JavaScript/etc. - Navigation View makes it all too easy!
For a significant proportion of my target user base, all the alternative
approaches for implementing navigation in EW2 that I've heard proposed are
orders of magnitude more complex/onerous/technical than the end-user
requirements demand (previously I could say "(Whilst knowledge of web site
design/HTML is useful,) any user capable of effectively using Word can create
and manage web sites as easily in FrontPage". EW2 presents a very different
proposition).
Oh and whilst new approaches may be a great deal more flexible, this infers
nothing regarding _ease of use_ - a quality of FP that was a key
differentiator - now seemingly being sadly lost?
Alas!!

"Cheryl D Wise" wrote:

> Dreamweaver does not have any automatic navigation creation tools. As a
> professional I have not used the FP navbots because they are far too
> limiting when based on the navigation structure. If I'm going to create a
> custom navigation bar I'd rather do it in a way that works well in every
> single browser out there and is not bloated. The FP webbot didn't do that.
> Heck, even my husband who only maintained a user group website complained
> about the navbot and how once you get beyond a dozen pages it wasn't really
> up to the job.
>
> My personal preference is to use unordered lists since this both correct
> semantic mark-up and something that will work in every browser and on every
> device including screen readers, cellphones and other devices. I can then
> style them to be dropdowns (with nested lists), rollovers or whatever I want
> using simple CSS. Okay for IE I may have to add either javascript or an htc
> (dom based manipulation) in order to get them to work properly but IE is
> getting better at standards support.
>
> Using includes (whether design time like the FP include function or server
> side - my preference) and/or a DWT custom navigation is so much easier and
> more versatile than anything you could do with an FP navbot.
>
> --
> Cheryl D Wise
> MS MVP Expression
> Author: Foundations of Microsoft Expression Web
> http://by-expression.com
> mail list: http://groups.google.com/group/by-ex...n-web-designer
>
>
> "Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
> news:16C61782-9856-476E-9C41-74275D8DF887@microsoft.com...
> >
> > You are joking right?!
> > Seriously, you're not telling me that the thousands of semantic
> > arrangements
> > between pages in my multiplicity of FrontPage sites need to be manually
> > recreated?
> > This alone would prevent my being able to recommend migration to any FP
> > user
> > (and indeed preclude my ever recommending EW2 - this is supposed to
> > supersede
> > FP2003, no? Improved standards compliance at the expense of critical
> > functionality - on that basis I'd better off with DreamWeaver?!!!).
> > What seems to be being proposed entails hundreds of man-hours work to
> > implement using EW2 and is quite frankly neither an efficient nor
> > recommendable path forward from FP2003 for any of my clients.
> > Ludicrous!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
>

Cheryl D Wise

When you drag a file in folder view all links will be updated. Drag a link
from one part of the navigation to another and it will update.

I spent three hours teaching a novice computer user to maintain their
organization's website. This person didn't even know how to use Word,
couldn't set up an email account in Outlook (or Outlook Express). At the end
of which she could create structured web pages with proper headings, Apply
styles, add links to the site navigation, import images add them to web
pages complete with alt attributes and publish the site with changes. Along
the way she also learned how to set-up an email account, create a rule to
filter email oh and how to create a heading and use styles in Word.

To add a link to the site menu she would put her cursor at the end of the
link she wanted it to follow and hit the enter key. Type in the name she
wanted to show in the menu and right click to bring up hyperlink properties,
select the page she just created and that was it. Not exactly difficult,
especially since all the styles were automatically applied by the
stylesheet.

--
Cheryl D Wise
MS MVP Expression
Author: Foundations of Microsoft Expression Web
http://by-expression.com
mail list: http://groups.google.com/group/by-ex...n-web-designer


"Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
news:75DA5819-22D5-4006-9B9D-D8526675CC7E@microsoft.com...
> Whilst Dreamweaver may not have any navigation management capabilities,
> removing such features from FP does not make EW2 compete with it any
> better!!!
> Agreed, I too would prefer to "do it once, right first time", however
> manual
> implementation in the manners suggested is certainly not it for me - or
> rather, it's fine providing the logical organisation of a site will NEVER
> change - once you're into having to maintain such a structure/reorganise
> and
> all of a sudden a significant overhead is introduced.
> Though I grant you that the innate non-standards compliance is a
> significant
> issue, I don't agree with your husband's view - I personally have
> implemented
> sites having thousands of pages with no problem, so I wonder quite where
> he's
> been going wrong?!
> Don't understand your comments RE includes/DWT custom navigation - neither
> of these methods quickly and easily allows you to drag, drop and
> (re-)organise a site's content, no?
> I had expected EW2 to minimally match FP functionality, but in this area,
> EW2 presents a huge downgrade. I'm no fan of having to manually do
> anything
> so losing such significant automation in EW2 is a "show stopper" for me.
> I should note that a number of my customers are SMEs who have absolutely
> no
> interest in doing anything technical - FP allowed me to implement a site
> for
> them (including navigation) then hand it over entirely for ongoing
> maintenance.
> An hour's training for an end-user and they're able to run with it -
> reorganise it - add to it - all with not a glimpse of HTML and no
> requirement
> to learn CSS/JavaScript/etc. - Navigation View makes it all too easy!
> For a significant proportion of my target user base, all the alternative
> approaches for implementing navigation in EW2 that I've heard proposed are
> orders of magnitude more complex/onerous/technical than the end-user
> requirements demand (previously I could say "(Whilst knowledge of web site
> design/HTML is useful,) any user capable of effectively using Word can
> create
> and manage web sites as easily in FrontPage". EW2 presents a very
> different
> proposition).
> Oh and whilst new approaches may be a great deal more flexible, this
> infers
> nothing regarding _ease of use_ - a quality of FP that was a key
> differentiator - now seemingly being sadly lost?
> Alas!!
>
> "Cheryl D Wise" wrote:
>
>> Dreamweaver does not have any automatic navigation creation tools. As a
>> professional I have not used the FP navbots because they are far too
>> limiting when based on the navigation structure. If I'm going to create a
>> custom navigation bar I'd rather do it in a way that works well in every
>> single browser out there and is not bloated. The FP webbot didn't do
>> that.
>> Heck, even my husband who only maintained a user group website complained
>> about the navbot and how once you get beyond a dozen pages it wasn't
>> really
>> up to the job.
>>
>> My personal preference is to use unordered lists since this both correct
>> semantic mark-up and something that will work in every browser and on
>> every
>> device including screen readers, cellphones and other devices. I can then
>> style them to be dropdowns (with nested lists), rollovers or whatever I
>> want
>> using simple CSS. Okay for IE I may have to add either javascript or an
>> htc
>> (dom based manipulation) in order to get them to work properly but IE is
>> getting better at standards support.
>>
>> Using includes (whether design time like the FP include function or
>> server
>> side - my preference) and/or a DWT custom navigation is so much easier
>> and
>> more versatile than anything you could do with an FP navbot.
>>
>> --
>> Cheryl D Wise
>> MS MVP Expression
>> Author: Foundations of Microsoft Expression Web
>> http://by-expression.com
>> mail list: http://groups.google.com/group/by-ex...n-web-designer
>>
>>
>> "Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
>> news:16C61782-9856-476E-9C41-74275D8DF887@microsoft.com...
>> >
>> > You are joking right?!
>> > Seriously, you're not telling me that the thousands of semantic
>> > arrangements
>> > between pages in my multiplicity of FrontPage sites need to be manually
>> > recreated?
>> > This alone would prevent my being able to recommend migration to any FP
>> > user
>> > (and indeed preclude my ever recommending EW2 - this is supposed to
>> > supersede
>> > FP2003, no? Improved standards compliance at the expense of critical
>> > functionality - on that basis I'd better off with DreamWeaver?!!!).
>> > What seems to be being proposed entails hundreds of man-hours work to
>> > implement using EW2 and is quite frankly neither an efficient nor
>> > recommendable path forward from FP2003 for any of my clients.
>> > Ludicrous!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>>
>>

Falcon42

Your responses very much appreciated Cheryl.
Some further in and amongst below.

"Cheryl D Wise" wrote:

> When you drag a file in folder view all links will be updated. Drag a link
> from one part of the navigation to another and it will update.
You refer to "the navigation" yet this concept does not seem to be directly
supported in EW2 at all.
Is what you mean: "when you make an amendment within your manually defined
navigation structure, links will update."?
Yet I don't seem to be able to find any clearly defined methods to manage
this.
Rather feels like it's everyone's best ideas forward and good luck devising
your own navigation system for yourself (or buy a 3rd party add-on/tool to
help accomplish)!
This frankly falls well short of an acceptable migration strategy from the
ease of use implicit in FP.
>
> I spent three hours teaching a novice computer user to maintain their
> organization's website. This person didn't even know how to use Word,
With FP it takes me less than a hour end-user training (including a few
extras!).
> couldn't set up an email account in Outlook (or Outlook Express). At the end
> of which she could create structured web pages with proper headings, Apply
> styles, add links to the site navigation, import images add them to web
"add links to the site navigation" - I think you mean: "make simple changes
to your previously devised and implemented system of navigation".
What happens when more extensive and/or complex changes are mandated?
I profoundly value FP's ability to see/manage all a site's logical
navigation structure in one place and publish any/all changes at a single
click!
Doubtless a million and one ways to work around this will emerge from the
market, each differing (and having its own technical requirements) - this
really does not strike me as the outcome of a well thought out product
strategy on this front...

> pages complete with alt attributes and publish the site with changes. Along
> the way she also learned how to set-up an email account, create a rule to
> filter email oh and how to create a heading and use styles in Word.
Super!
However I would not be in a hurry to give such responsibilities to a user
who had such an apparently low base of computing skills!
Axiomic - a little knowledge can be a dangerous thing!!
With more flexibility comes an accordant requirement for discerning,
knowledgeable use to avoid errors/problems inadvertently arising.
Presently I'm of the view that considerable, additional (preferably in
advance!) training is needed in order for a user to comprehend and
effectively use EW2, compared to FP.
>
> To add a link to the site menu she would put her cursor at the end of the
Sorry - "the site menu"? To what exactly are you referring? A (simple?)
navigation system you had already manually implemented for her?
How does this modus operandi work when one has multiple site sections, each
with its own contextual navigation (e.g. next/back/up links)?
> link she wanted it to follow and hit the enter key. Type in the name she
> wanted to show in the menu and right click to bring up hyperlink properties,
> select the page she just created and that was it. Not exactly difficult,
> especially since all the styles were automatically applied by the
> stylesheet.
This is not an issue concerning styling (that's the easy bit!!!!!!!!!), but
of the management capabilities of the tool. I'm far less concerned about how
the navigation is manifested in pages (minor tweaks to themes previously
neatly took care of this) but am focussed on how I'm supposed to manage a
navigation structure comprising links between hundreds of pages, whose
overall structure and organisation may need change from time to time?
Can't help feeling that having to implement and manage navigation manually
in EW2 infers considerable overheads not previously required using FP...

>
> --
> Cheryl D Wise
> MS MVP Expression
> Author: Foundations of Microsoft Expression Web
> http://by-expression.com
> mail list: http://groups.google.com/group/by-ex...n-web-designer
>
>
> "Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
> news:75DA5819-22D5-4006-9B9D-D8526675CC7E@microsoft.com...
> > Whilst Dreamweaver may not have any navigation management capabilities,
> > removing such features from FP does not make EW2 compete with it any
> > better!!!
> > Agreed, I too would prefer to "do it once, right first time", however
> > manual
> > implementation in the manners suggested is certainly not it for me - or
> > rather, it's fine providing the logical organisation of a site will NEVER
> > change - once you're into having to maintain such a structure/reorganise
> > and
> > all of a sudden a significant overhead is introduced.
> > Though I grant you that the innate non-standards compliance is a
> > significant
> > issue, I don't agree with your husband's view - I personally have
> > implemented
> > sites having thousands of pages with no problem, so I wonder quite where
> > he's
> > been going wrong?!
> > Don't understand your comments RE includes/DWT custom navigation - neither
> > of these methods quickly and easily allows you to drag, drop and
> > (re-)organise a site's content, no?
> > I had expected EW2 to minimally match FP functionality, but in this area,
> > EW2 presents a huge downgrade. I'm no fan of having to manually do
> > anything
> > so losing such significant automation in EW2 is a "show stopper" for me.
> > I should note that a number of my customers are SMEs who have absolutely
> > no
> > interest in doing anything technical - FP allowed me to implement a site
> > for
> > them (including navigation) then hand it over entirely for ongoing
> > maintenance.
> > An hour's training for an end-user and they're able to run with it -
> > reorganise it - add to it - all with not a glimpse of HTML and no
> > requirement
> > to learn CSS/JavaScript/etc. - Navigation View makes it all too easy!
> > For a significant proportion of my target user base, all the alternative
> > approaches for implementing navigation in EW2 that I've heard proposed are
> > orders of magnitude more complex/onerous/technical than the end-user
> > requirements demand (previously I could say "(Whilst knowledge of web site
> > design/HTML is useful,) any user capable of effectively using Word can
> > create
> > and manage web sites as easily in FrontPage". EW2 presents a very
> > different
> > proposition).
> > Oh and whilst new approaches may be a great deal more flexible, this
> > infers
> > nothing regarding _ease of use_ - a quality of FP that was a key
> > differentiator - now seemingly being sadly lost?
> > Alas!!
> >
> > "Cheryl D Wise" wrote:
> >
> >> Dreamweaver does not have any automatic navigation creation tools. As a
> >> professional I have not used the FP navbots because they are far too
> >> limiting when based on the navigation structure. If I'm going to create a
> >> custom navigation bar I'd rather do it in a way that works well in every
> >> single browser out there and is not bloated. The FP webbot didn't do
> >> that.
> >> Heck, even my husband who only maintained a user group website complained
> >> about the navbot and how once you get beyond a dozen pages it wasn't
> >> really
> >> up to the job.
> >>
> >> My personal preference is to use unordered lists since this both correct
> >> semantic mark-up and something that will work in every browser and on
> >> every
> >> device including screen readers, cellphones and other devices. I can then
> >> style them to be dropdowns (with nested lists), rollovers or whatever I
> >> want
> >> using simple CSS. Okay for IE I may have to add either javascript or an
> >> htc
> >> (dom based manipulation) in order to get them to work properly but IE is
> >> getting better at standards support.
> >>
> >> Using includes (whether design time like the FP include function or
> >> server
> >> side - my preference) and/or a DWT custom navigation is so much easier
> >> and
> >> more versatile than anything you could do with an FP navbot.
> >>
> >> --
> >> Cheryl D Wise
> >> MS MVP Expression
> >> Author: Foundations of Microsoft Expression Web
> >> http://by-expression.com
> >> mail list: http://groups.google.com/group/by-ex...n-web-designer
> >>
> >>
> >> "Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
> >> news:16C61782-9856-476E-9C41-74275D8DF887@microsoft.com...
> >> >
> >> > You are joking right?!
> >> > Seriously, you're not telling me that the thousands of semantic
> >> > arrangements
> >> > between pages in my multiplicity of FrontPage sites need to be manually
> >> > recreated?
> >> > This alone would prevent my being able to recommend migration to any FP
> >> > user
> >> > (and indeed preclude my ever recommending EW2 - this is supposed to
> >> > supersede
> >> > FP2003, no? Improved standards compliance at the expense of critical
> >> > functionality - on that basis I'd better off with DreamWeaver?!!!).
> >> > What seems to be being proposed entails hundreds of man-hours work to
> >> > implement using EW2 and is quite frankly neither an efficient nor
> >> > recommendable path forward from FP2003 for any of my clients.
> >> > Ludicrous!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> >>
> >>
>
>

Rob Giordano \(Crash\)

inline...


--
~~~~~~~~~~~~~~~~~~
Rob Giordano
Microsoft MVP Expression






"Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
news:2583D8FD-F890-4C06-8190-1235BA0423C6@microsoft.com...
> Your responses very much appreciated Cheryl.
> Some further in and amongst below.
>
> "Cheryl D Wise" wrote:
>
>> When you drag a file in folder view all links will be updated. Drag a
>> link
>> from one part of the navigation to another and it will update.
> You refer to "the navigation" yet this concept does not seem to be
> directly
> supported in EW2 at all.
> Is what you mean: "when you make an amendment within your manually defined
> navigation structure, links will update."?
> Yet I don't seem to be able to find any clearly defined methods to manage
> this.
> Rather feels like it's everyone's best ideas forward and good luck
> devising
> your own navigation system for yourself (or buy a 3rd party add-on/tool to
> help accomplish)!
> This frankly falls well short of an acceptable migration strategy from the
> ease of use implicit in FP.

Sure it does...links will be updated, same as in FP - as long as you're
working with a web site opened and not loose pages.

This is why Cheryl mentioned DWTs & includes...build your menu in one place
(DWT or include) update there...all links will be updated.

Falcon42

Thanks for your reply Rob.
Whilst having links update during manually crafting a web site's navigation
is good, this does not really detract from the primary issue being that EW2
requires such manual crafting/maintenance in the first place!
Regarding your other comment, can you advise as to how DWTs/includes
provides for complex site management (such as a site having multiple layers
of sub-sections, need for back/next/up links, etc.)? EW2 Help seems to be
ignorant of this?
Pending further, at present I sadly have to remain of the view that EW2 is
unsuitable for a significant proportion of FP users.


"Rob Giordano (Crash)" wrote:

> inline...
>
>
> --
> ~~~~~~~~~~~~~~~~~~
> Rob Giordano
> Microsoft MVP Expression
>
>
>
>
>
>
> "Falcon42" <Falcon42@discussions.microsoft.com> wrote in message
> news:2583D8FD-F890-4C06-8190-1235BA0423C6@microsoft.com...
> > Your responses very much appreciated Cheryl.
> > Some further in and amongst below.
> >
> > "Cheryl D Wise" wrote:
> >
> >> When you drag a file in folder view all links will be updated. Drag a
> >> link
> >> from one part of the navigation to another and it will update.
> > You refer to "the navigation" yet this concept does not seem to be
> > directly
> > supported in EW2 at all.
> > Is what you mean: "when you make an amendment within your manually defined
> > navigation structure, links will update."?
> > Yet I don't seem to be able to find any clearly defined methods to manage
> > this.
> > Rather feels like it's everyone's best ideas forward and good luck
> > devising
> > your own navigation system for yourself (or buy a 3rd party add-on/tool to
> > help accomplish)!
> > This frankly falls well short of an acceptable migration strategy from the
> > ease of use implicit in FP.
>
> Sure it does...links will be updated, same as in FP - as long as you're
> working with a web site opened and not loose pages.
>
> This is why Cheryl mentioned DWTs & includes...build your menu in one place
> (DWT or include) update there...all links will be updated.