The document discusses various topics related to the SharePoint user experience and custom development. It explains that custom development in SharePoint can be done without writing code by leveraging the existing user interface framework. It also overview standard features of Windows SharePoint Services v3 like lists and libraries, and how SharePoint Server 2007 simplifies user interface tasks using Master Pages and navigation controls from ASP.NET 2.0. Finally, it covers steps for creating and extending web applications and site collections in SharePoint.

2. The SharePoint User Experience What do you mean by Custom Development; is it always about writing code. Now since Windows SharePoint Services is a framework, and Microsoft has already written a user interface layer, you can make many development changes without writing any code. Keep in mind that you will always have this functionality in Office SharePoint Server 2007 because MOSS simply builds more functionality on top of the core functionality by WSS v3.

3. SharePoint Server 2007 & ASP.NET 2.0 SharePoint server 2007 greatly simplifies the UI tasks by using Master Pages and site Navigation controls borrowed from ASP.NET 2.0, which is the foundation of SharePoint 2007.

4. Session Topics Standard features of WSS v3, including lists and document libraries. Columns of lists, including Site Column and Content Types. Enhancements to the user Interface and how to modify the site look and feel. Addition of Mobile Development to Windows SharePoint Services v3.

5. Create or Extend Web Application Web Application is the new name for what is known as a “Virtual Server” in Windows SharePoint Server v2. Do not get confused with Microsoft Virtual Server.

6. Steps NeededCreate or Extend Web Application Navigate to Central Administration page, click to Application Management tab. Under SharePoint Web Application management, click the Create or Extend Web Application. To create a new web application click on Create New Web Application.

7. Create or Extend Web Application

8. Site Collection Content Is always stored in a Site Collection Even though you have created a Web Application, a site collection needs to be added to have a place to store the content of the web site. Site collection is a top level site that will contain all of the other pages in the site. When a new SP Web Application is created, a site collection is not automatically created by SharePoint. To create a Site Collection navigate to the Application Created page, click on the Create Site Collection link.

9. Create or Extend Site Collection

10. Using SharePoint Lists & Libraries SharePoint is made up of content and data. The lists and libraries of SharePoint are the core to store data in SharePoint. The lists can be set up and customized by a site designer or authorized user to contain any number of fields required for list data. A library is where a collection of files, as well as associated data, can be stored and managed. Every list is defined in a file called “Onet.xml” that is stored in the site definition.

11. Using Pages to Display Lists Basic Page: Use this page to create a new basic page on your site. You can add any content you want to the new page after you create it. Web Part Page: A Web Part Page is a collection of Web Parts that combines list data, timely information, or useful graphics into a dynamic Web page. The layout and content of a Web Part Page can be set for all users and optionally personalized by each user. Sites & Workspaces: Use this page to create a new site or workspace under this SharePoint site. You can specify a title, Web site address, and access permissions.

12. Create SharePoint Lists & Libraries

13. Storing data with Lists & Libraries Data that is stored in SharePoint is stored in one of the two ways: Lists: These contain data elements that define what is contained in SharePoint. Some common examples are a list of links, a list of announcements, or a list of custom data elements. Libraries: Libraries are a special type of list that has built-in capabilities to handle storing files. This includes version and new file template features.

15. Project Tasks

16. Issue Tracking

17. Survey

18. Sites and Workspaces

19. Announcements

20. Contacts

21. Discussion Board

22. Links