Display and navigate wiki pages on SharePoint site (in web part)
How can I display the content part of a wiki page (no navigation) on a SharePoint web page,so that you can navigate the wiki page without leaving the SharePoint site.
The idea is to display a central web part (visually) where the user can select a link to go to a new wiki page (still displayed in the central web part) to gain additional information (a kind of flow)
The wiki pages in question resides in the same wiki page library if that's relevant for a solution.
The idea is to display a central web part (visually) where the user can select a link to go to a new wiki page (still displayed in the central web part) to gain additional information (a kind of flow)
The wiki pages in question resides in the same wiki page library if that's relevant for a solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hmmmm - I'm not sure how this can be used to handle my little wizard:
Idea is: show an information page, where you can select one of two options/pages - on each of those you can choose another 2 options, which will send you to external pages or a new information page... (still inside the web part)
Idea is: show an information page, where you can select one of two options/pages - on each of those you can choose another 2 options, which will send you to external pages or a new information page... (still inside the web part)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
that would leave an entry every time someone goes through the wizard - that's not needed and would just add clutter to the solution. Just need to guide users to the correct page - no data collection is needed (or wanted)
We have chosen to create a small hard coded html wizard - but good suggestions - even if they did not hit spot on the issue.
The solutions were valid but not as "cheap" to implement as the solution we ended up using
ASKER