Globalization is the process of designing apps that support different cultures. Globalization adds support for input, display, and output of a defined set of language script that relates to specific geographic areas.
Localization is the process of adapting a globalized app, which you have already processed for localizability, to a particular culture/locale.
Step-by-step Creating SharePoint Team Site
- Plan Overall Site Architecture
- Plan Site Collection Structure
- Plan on Web Parts that will make up the Team Site
- Common Web Parts for Team Site
- Decide the Layout of the Team Site
- Create the Team Site
- Configure the Web Parts
- Create a “Compact View” for each Web Part
- Add the Web Parts to the Site
- Setup Security for the Site
- Setup Quick Launch Navigation
- Never present the Site Contents link on the navigation menu
- Remove “Recents”
- Create a Site Template
The best practice is to keep the SharePoint Site structure as flat as possible.
It is best practice to define all custom columns (metadata properties) at the very top site (Site Collection).
The best practice is to never break the inheritance of security from the site the web parts sit on.
Common Web Parts for Team Site
- Document Library
- Configure it w/ metadata, instead of folders
- Sync to Outlook
- Contact List
- Discussion Board
- Issue Tacking
- SharePoint Project Dashboard
- Sync SharePoint Task List w/ MS Project
- Project Risk Register in SharePoint
- SharePoint External Sharing
- Change Request Log in SharePoint
- Calednar Color Coding
- Calendar Sync w/ Outlook