these convenstions will allow everyone to find information easier. we are also planning on using these standardised page names to organise and sort wiki pages in useful documentation overview tables.
|
|
!!every package should have the following
|
-__<package>Package (required)__
|
-contains some generic information about the package and what it does. there should be a link to <package>Features, even if it doesn't exist, since it might encourage the creation of the page.
|
+__<package>Package (required)__ |
+contains some generic information about the package and what it does. there should be a link to <package>Features, even if it doesn't exist, since it might encourage the creation of the page. |
e.g.: LibertyPackage
|
|
-__<package>Features (optional)__
|
-contains information regarding various features that can be set in a particular package. should contain links to the existing <feature>Tutorial pages.
|
+__<package>Features (optional)__ |
+contains information regarding various features that can be set in a particular package. should contain links to the existing <feature>Tutorial pages. |
e.g.: LibertyFeatures
|
|
-__<feature>Tutorial (optional)__
|
+__<feature>Tutorial (optional)__ |
contains a basic tutorial on how to turn on and use a given feature.
|
+e.g.: ThemeTutorial |
|
-please keep names rather short. if you feel that the title is too short and you want to associate a note with the title, use the description line to do this. the description will appear when hovering over a given link.
|
|
+in addition, it is useful if page creators update the category and structure information as well. |
+ |
+ |
+please keep names rather short. if you feel that the title is too short and you want to associate a note with the title, use the description line to do this. the description will appear when hovering over a given link. |
|
|
|