This repository has been archived by the owner on Mar 11, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 48
SharePoint 101 A. SharePoint A Bird's Eye View (through click programming)
Philippe Lavoie edited this page Mar 11, 2020
·
1 revision
Functional overview of SharePoint's capabilities and infrastructure.
##Central Administration
- Services & Service Applications
- Term Store (Plan managed metadata in SharePoint Server 2013)
- Search (Plan search in SharePoint Server 2013)
- User Profile Service (Plan user profiles and identities)
- Monitoring
- Using ULSViewer
- How to turn on Verbose logs (Overview of monitoring in SharePoint 2013)
- Alternate Access Mappings & Host-named Site Collection
- Zones
- Authentication Providers
- How the execution model maps to IIS
- Site definitions vs. Web Templates
- Site collection vs Site
- Managed paths
- SPSite == Site Collection
- SPWeb == Site == Root Web + Sub Webs
References:
- Blog: A guide to Alternate Access Mappings Basics in SharePoint 2013
- Technet Download: The final guide to Alternate Access Mappings
- MSDN Blog: Alternate Access Mappings Explained
- Technet: Host-named site collection architecture and deployment (SharePoint 2013)
- MSDN Blog: Beware crawling the non-Default zone for a SharePoint 2013 Web Application
- Technet: ADFS setup
- Single-server
- Distributed farm: DB + APP + WFE roles
- The SharePoint file system:
- 14 + 15 hive:
C:\Program Files\Common Files\microsoft shared\Web Server Extensions
- Virtual Directories:
C:\inetpub\wwwroot\wss\VirtualDirectories
- 14 + 15 hive:
References:
- Site vs List fields
- Content types
- How to associate multiple content types to a single list
References
- Why avoiding folders is generally a good idea:
- Document versionning and the simple moderation/approval process
References:
- Wiki vs Publishing Pages
- Web Part Pages
- Content Editor Web Part
References:
- Language packs drive the language of SharePoint's "chrome" (menu elements, settings pages, etc.)
- When you create a site, you must specify a default language. You can also activate alternate languages (if you have the language pack installed)
- How the user's browser language and User Profile is used to determine which of the alternate languages will be shown
- The MUI is NOT meant for content translation - for this, you must use SharePoint Variations.
- How to translate list titles, content type names and other "content container titles" by toggling between the various MUI languages
- How to activate alternate languages in the Term Store
- Don't confuse the MUI Language and the Regional Settings' locale
- MUI == Site Languages == Language Packs == en-US + fr-FR ==
CultureInfo.CurrentUICulture
- Regional Settings == Locale == en-CA + fr-CA == date and money formats ==
CultureInfo.CurrentCulture
- MUI == Site Languages == Language Packs == en-US + fr-FR ==
References: