| @@ -5,7 +5,7 @@ |
|
|
|
|
| ! Disabling packages
|
| -If your site gets one gazillion clicks a day, you need a forum ''and'' a blog for sure. Until then ... do your users ''really'' want to ((TagsPackage|tag)), ((LibertyPackage#LibertyComments|comment)), ((StarsPackage|vote)), ((RecommendsPackage|recommend)), have their own ((BlogsPackage|blog)), post to the ((BoardsPackage|forum)), ((MessagesPackage|message)) each other, subscribe to your ((NewslettersPackage|newsletter)), ((TreasuryPackage|upload)) their podcasts and videos, post and share ((FisheyePackage|images)), and save their ((WikiPackage|wiki)) pages as ((PdfPackage|PDF)) files? It's a good idea to focus on ''one'' thing. If that thing is a "social web platform", well, in that case you probably do need all packages. If you are looking to setup Bitweaver as a personal blog, it might be better to install that package first, and enable other packages as you go along. Packages don't have to be 100% available to the public. In a blog, you'll still want to post pictures or podcasts, and use ((FisheyePackage|Fisheye)) and ((TreasuryPackage|Treasury)) to collect and manage them. Yet the existence of these package does not have to be known to your readers beyhond their ability to look or listen or vote (or recommend, and so on). Lining up extended functionality behind one major hook can be a great way to channel the attention of your visitors.
|
| +If your site gets one gazillion clicks a day, you need a forum ''and'' a blog for sure. Until then ... do your users ''really'' want to ((TagsPackage|tag)), ((LibertyPackage#LibertyComments|comment)), ((StarsPackage|vote)), ((RecommendsPackage|recommend)), have their own ((BlogsPackage|blog)), post to the ((BoardsPackage|forum)), ((MessagesPackage|message)) each other, subscribe to your ((NewslettersPackage|newsletter)), ((TreasuryPackage|upload)) their podcasts and videos, post and share ((FisheyePackage|images)), and save their ((WikiPackage|wiki)) pages as ((PdfPackage|PDF)) files? It's a good idea to focus on ''one'' thing. If that thing is a "social web platform", well, in that case you probably do need all packages. If you are looking to setup Bitweaver as a personal blog, it might be better to install that package first, and enable other packages as you go along. Packages don't have to be 100% available to the public. In a blog, you'll still want to post pictures or podcasts, and use ((FisheyePackage|Fisheye)) and ((TreasuryPackage|Treasury)) to collect and manage them. Yet the existence of these package does not have to be known to your readers beyhond their ability to look or listen or vote (or recommend, and so on). Lining up extended functionality behind one major hook can be a great way to channel the attention of your visitors. If you selected too many packages at installation, just go to the Administration -> kernel -> packages page, and deselect the one you want to disappear. |
|
|
|
|
| ! Reading the docs
|
|
|