Moving child pages in navigation not displaying correctly

[Miles]

Guidance appreciated:

Have vertical navigation bar based on navigation structure positioned in
left hand shared border displaying pages beneath home page. Many of these
pages have child pages. In order to allow people to navigate to these child
pages an additional horizontal navigation bar has been placed on the page
proper inside a single cell table. All works great, however, when attempting
to move a child page to a different parent page and viewing in browser it
appears to insert itself at a level between the parent and child pages. When
navigating to any of the other child pages in the parent structure the newly
linked page does appear as a hyperlink but does not display the other child
links. The pages of the site will more than likely be moved around a fair bit
and we do not have the luxury to rebuild the navigation from scratch each
time.

Secondary question... site will need to be published to a corporate
SharePoint site, are there any specific considerations I need to keep in mind
i.e. am I allowed to have DHTML, will style sheets etc publish across, will
sharepoint be able to pick up the site in let's say a page web viewer part?

Many questions but will settle for an answer on the first one at this stage
- tks

p.s. am running on Win XP prof and using Frontpage 2003

 

[Tom Miller]

Have vertical navigation bar based on navigation structure positioned in

left hand shared border displaying pages beneath home page. Many of these
pages have child pages. In order to allow people to navigate to these
child
pages an additional horizontal navigation bar has been placed on the page
proper inside a single cell table. All works great, however, when
attempting
to move a child page to a different parent page and viewing in browser it
appears to insert itself at a level between the parent and child pages.
When
navigating to any of the other child pages in the parent structure the
newly
linked page does appear as a hyperlink but does not display the other
child
links. The pages of the site will more than likely be moved around a fair
bit
and we do not have the luxury to rebuild the navigation from scratch each
time.

If I am understanding you right, your using the FP navigation feature. But
your also using a manually added navigation bar for the child pages under a
paticular page.

I thought you could drag the child pages in navigation view to where-ever
you need them rather than hand coding it.

If that is true, you shouldn't need the extra manually added coding which in
turn might take care of the funny behavior issue I think I understood.

I hope I understood you correctly.

Secondary question... site will need to be published to a corporate
SharePoint site, are there any specific considerations I need to keep in
mind
i.e. am I allowed to have DHTML, will style sheets etc publish across,

As far as I understand it, a Sharepoint website will be serving the pages
exactly like an regular webiste on IIS would. Sharepoint runs more code to
run the portal on the server, but the page it actually serves is still
html/javascript etc. My understanding is the pages don't work very well
with non-IE browsers. So Sharepoint is a perfectly good Intranet portal but
not a real good public access portal.

will
sharepoint be able to pick up the site in let's say a page web viewer
part?

Sorry, I'm clueless on this. I don't know what "...page web viewer
part...." means. That is why I list myself as an "Occasional
PowerUser"....not an MVP wannabe ;-)