Explains external facing SharePoint site development experience, techniques in agile manner

1. External facing SharePoint site By Manish Rawat http://www.linkedin.com/in/manishra

2. Architecture and Design Choices

3. Planning - Key Decision Points

5. Number (How many) and Types (What kind) needed

6. Host header needs

7. Managed Paths – Enables where site collection will get created & help interpret URLs to determine site paths

8. Separate Content Database per site collection possible.Helps Performance and Scalability but rolling up data (query)from multiple Site collection is not OOTB

9. Unique administrative & Security privileges per site collection

11. Search

12. BDC – Business Data catalog to connect to any Line of Business (LOB) apps e.g. SAP

13. User Profiles

14. Usage Reporting …..

15. Scripting

16. Reusable Script needed. Useful in medium to large teams.

17. STSADM is main scripting tool. Free Extensions available.

18. STSADM scripts have options are not available via UI. E.g. assigning Specific DB to Site collection.

20. Consistent Look and feel in different sites.

21. UI assets location

22. Document Management

23. Content Organization

24. Content Presentation & Customization

25. Content Publishing – OOTB publishing including Quick Deploy

26. Search : Sources, Scope, Keywords, Crawl, Best bets

27. Versioning and Workflow:

28. List versioned

30. Data pull from anywhere in site collection. Provide RSS capability

31. Custom Look and feel : XSLT conversion

32. Site ColumnsReusable and central managed entity. Its like a data type.

33. Content TypeType definition/Functional unit – collection of setting & metadata.Usually references to site columns - Supports Inheritance - Identify Hierarchy

34. ListsDatabase table whose schema is defined by Content Type OR adding column individually.

36. Small/Medium/Large Farm

37. Different environments connectivity

38. Automated build needs

39. Securing SharePoint-

40. Intranet, Internet, Extranet

41. Zones requirements

42. Roles and Permission

43. Data Protection, Recovery and Availability

44. Monitoring needs

46. Project Structure/Processes setup to minimize need of SharePoint knowledge

47. Use OOB controls/infrastructure of SharePoint

48. XCopy (WSP) based deployment

49. Run in Minimal Trust level

53. Form Authentication cookie can Shared between multiple Web apps

56. Own Domain environment (AD, TFS, DB, Middle tier Servers all in one domain)

57. All developers (10 to 12) machines/servers in same domain

58. Each developer has its own MOSS setup

60. Use Scripts to setup/configure in medium to large Teams/Farms

61. Unattended MOSS installation scripts

62. Setup PDF ifilter to search pdfs

63. Create SSP via scripts

64. Create Web Application

66. Typical SharePoint solution will have

67. Branding Project: Contains master page, page layouts and their corresponding content types

68. Types Project: Contains CAML definition of site columns, List content types etc

69. UserControl Project: Contains ascx controls . V2010 supports visual web parts

70. WebParts Project: Contains web parts definitions and code

72. Requirements not fully flushed => Page Template/Layout keeps changing

73. PLD (Presentation developer) need isolated environment within SharePoint (Branding VS. Net Project)

74. Process

75. Person ‘X’ to be owner of SharePoint content database. i.e. responsible for types/building blocks

76. Change to Lists, Content Type, Site columns to be performed by Person ‘X’ and distribute the content database backup to team.

77. Page Layout

78. Person ‘X’ to create page layout with required elements (coming from content type)

79. PLD to use SharePoint designer to design Page Layout.

80. Use DisplayMode (Edit /Display) if SharePoint control default rendering is not sufficient <PublishingWebControls:editmodepanelrunat="server" id="editmodepanelEditModeQuickLinks" PageDisplayMode="Edit" > <PublishingWebControls:RichLinkFieldFieldName="QuickLink1" runat="server" id="RichLinkField0" /></li> </PublishingWebControls:editmodepanel> <PublishingWebControls:EditModePanelrunat="server" id="QuickLink1DisplayMode" PageDisplayMode="Display"> <pmxServerControls:LinkFieldRendererrunat="server" LinkFieldName="QuickLink1" /> </PublishingWebControls:EditModePanel>

82. Requirements close to finalization => Page Template/Layout doesn’t change often

83. PLD need isolated environment within SharePoint

84. Process

85. Move SharePoint assets as Features

86. Anyone is team is owner of SharePoint content database.

87. Page Layout

88. PLD to use Visual Studio to design Page.

91. Break permission inheritance & disable Anonymous

92. Set NoCrawl property to True

93. Exclude Library in SSP Search Index crawling

95. Package of related file set deployable to SharePoint from VS.NET

96. Copy to 12 Hive -> Use once a features is deployed

97. You can controls where the assemblies will go (Bin vs. GAC). Bin is preferred because GAC assemblies runs in full control by default.

98. Highly configurable

99. Andrew Connell stsadm extensions

100. Usage: Create Site columns, content types from SharePoint GUI and use following to generate XML to create them as a Feature