Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Things you need to know:

  1. The Wiki is organized as a tree. So each page has a parent and can have children.
  2. Versions and conflicts are being tracked.
  3. You can apply security to pages so that e.g. only SAP employees can see the page - and therefore the child pages.
  4. Think about the Wiki as book. You have a starting page with the Table of Content, each sub-chapter has ....
  5. Within the BO Wiki each page has to have a unique name. So if you would name your page "Chapter 1" nobody else in the entire BO Wiki can use that page name as well. Point is, rather use names that identify your topic, like I did with the sub-pages.
  6. When you change the page name, all related links are changed as well within the Wiki. But external references, in forums, in external blogs are not changed. So rather pick a good name at the beginning.

Page layout

Each page should consist of a summary explaining what this chapter is about in a few sentences.
Syntax:
{panel:title=Summary}blablabla{panel}
Example:

Summary

We should agree on a common set of layout options so that the entire Wiki has a consistent look and feel - as much as possible.


Then there will be some text and if another heading is required it should be the h3. heading.


A single page should not be too long to simplify navigation, rather create sub-chapters - or child pages as we call them in the wiki. You can add new child pages by viewing the master page and on the top menu select ADD -> Page.

At the end of each page we have a list of all child pages using the {children:depth=2} macro. This kind of acts as a navigational help to get to the next pages with more detailed information. In most cases the depth=2, but for pure index pages you do not want to show the sub-chapters within the chapters, so you use only depth=1 then.

And below should be the {pagetree:root=main chapter} macro to support navigation to the siblings of the current page. As root pick the the main chapter of the entire section. A nice example on how this is organized can be seen in the
BusinessObjects Data Services Tips and Tricks....the Index page, hence depth=1, root=itself
Then you navigate to the
How To - typical questions about DataServices....which is another index page, depth=1, root=itself
And finally look around in the chapter
Access to previous row values....the main page of this chapter, so this page and all its child pages have depth=2, root=Access to previous row values so you can navigate freely between the different options.

To go back to the parent page you use the page hierarchy at the top of each page, which is built automatically. If that hierarchy is too deep it will show "..." which you can click on to expand to the full hierarchy.



  • No labels