Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about how to design and create your own Sharepoint Site. Many people may not know much about it. In order to make you understand better, the editor has summarized the following for you. I hope you can get something according to this article.

However, I have been doing Sharepoint development for a period of time, but Sharepoint is still new to me. I recall that when I first came into contact with Sharepoint, I looked everywhere for information, and I found a lot of information, but I still didn't know how to do Sharepoint development. I also searched a lot of articles on Cnblog, but it was still in the clouds for a novice like me. So I wanted to write a series of introduction to Sharepoint. This series will start with the basics, so that even a person who has never known Sharepoint knows how to do Sharepoint development through reading this series.

It mainly introduces how to design and create your own Sharepoint Site.

Through Microsoft's materials, we know that there are many ways to create a custom Sharepoint site. But which way do we choose? On what basis do we make our choices?

Purpose is the purpose. Purpose is the most critical factor. Depending on your intention, you can choose whether it is a simple custom site or a premium custom site. For example, if your site is for a group or to manage a small Project, you can choose a simple custom site, but if a site is used by an enterprise of thousands of people and has a large number of visitors every day, you can choose an advanced customized site, perhaps in this case, the functions provided by Sharepoint Server 2007 itself cannot be implemented. At this point you need additional development capabilities, we can use other development tools, such as Visual Studio 2005 and so on.

Resources resources. The resources include software (Microsoft Office SharePoint Designer 2007 and Microsoft Visual Studio 2005) and hardware. Simple sites don't need a lot of extra resources. Sharepoint itself provides adding web parts, customizing view lists, and changing images on the home page. And with the help of Sharepoint Designer you can also complete more complex customizations, such as changing Master Page and LayOut. But advanced sites need a lot of resources, such as more Farm to complete development, testing and other work, but also with the help of other development tools such as VS2005 to complete more functions.

Personnel is, in popular terms, people. The larger the site, the more complex the function, the more people are needed. It's easy to understand.

Let's take a look at the development approaches, advantages and disadvantages of various levels of sites.

A simple customized site

For simple Sharepoint Site. You can customize it directly in the browser. For example, a team site includes: Team Logo, Calendar, Shared Documents, announcements, shared contacts and some simple web part. All these functions can be accomplished through the functions provided by the site itself.

Intermediate customized site

For some simple functions, you can operate like customizing simple Site. In addition, you can also handle more advanced customization through Sharepoint Designer 2007 (a tool for handling Sharepoint site). For example, an enterprise site uses the home page to display company messages, and sub-sites to display human resources information and some business data. This requires you to do more extra work:

. Custom Master Page

. Custom layouts to display different Page

. Custom CSS style

. Custom data display web part to display personal data

. There are also some such as workflow, document management, business intelligence and so on.

Advanced customized site

Our series is aimed at those who want to develop workflow, web part, document management, CSS, Master Page, layouts pages, etc. Advanced Sharepoint site is those Internet sites with a wide range of uses, large visits and more business. These sites generally require user authentication, custom site elements and characteristic sites. So to develop such a site, we may need a complex development, testing, and deployment environment. For example, develop and deploy in this place to another place, and so on. This requires a huge team that includes requirements analysts, designers, developers, and testers.

This guide describes two methods of customization:

An author-centric approach, in which authored site elements (including projects such as master pages and layout pages) are maintained and deployed in a different way than site elements developed by maintenance and deployment. This method speeds up the distribution of created content.

A developer-centric approach in which developed site elements (such as Web parts and workflows) and site projects (such as master pages, layouts, and cascading style sheets) are maintained and deployed using similar methods. This provides a more rigorous maintenance approach to typical website projects that are usually associated with software development.

In the author-centric approach, there are different ways to create, maintain, and deploy authored and developed Web site elements.

Authored site elements create authoring site projects (master pages, layouts, Web, and cascading style sheets) and their content pages, graphics, and other files for the site by using client applications running in Web browsers, such as Office SharePoint Designer 2007, Office Word 2007, or Office SharePoint Server 2007. The management of content, such as version control, check-in / check-out, and content approval, is based on the document management features provided by default in Office SharePoint Server 2007. Use the Web publishing features included in Office SharePoint Server 2007, such as content deployment and site variants, to deploy all authored site elements, including projects and content pages.

Developed site elements typically use Microsoft Visual Studio 2005 and Microsoft .NET Framework 3.0 to create custom developed site elements for a Web site. Source control and configuration management are handled by programs such as Visual Studio 2005 Team System. Package custom development elements as features and deploy them using the packaging and deployment capabilities of the Office SharePoint Server 2007 solution.

The author-centered approach has the following advantages:

Use the content deployment features in Office SharePoint Server 2007 to deploy custom projects, such as master pages and layouts.

Accelerate the distribution of content because all content is managed directly in Office SharePoint Server 2010 rather than in a separate configuration management system. You can take advantage of the built-in content versioning, check-in / check-out, and approval features of Office SharePoint Server 2007.

It is generally easier to configure and deploy because this approach requires a less customized development environment.

For an introduction to scenarios that use an author-centric approach, including examples of the various environments used, see Custom scenarios.

A developer-centric approach

In a developer-centric approach, you use different approaches to create authored and developed Web site elements, but maintain authored and developed projects in the same configuration management system and deploy in a similar way.

Authored site elements are divided into two categories: projects that create frames in which to display site content (such as master pages and layouts) and site content (pages and images of the site). In the developer-centric approach, the project is developed in a development environment and maintained in the same configuration management system as maintaining coded Web site elements. The project is packaged with the coding elements into the solution package, and then the solution package is deployed to the production site, creation site, and test site. Site content is maintained in the creation field using the document management features provided by default in Office SharePoint Server 2010. Both project and website content use content deployment capabilities to deploy from the creation site to the production site and the test site.

Developed site elements, as in the author-centric approach, typically use Microsoft Visual Studio 2005 and Microsoft .NET Framework 3.0to create custom development elements for a Web site. You can use Visual Studio 2005 Team System or the equivalent configuration management system to manage source code, binaries, and solution files. Package custom development elements as features and deploy them using the packaging and deployment capabilities of the Office SharePoint Server 2010 solution.

The developer-centric approach has the following advantages:

The project and code are managed in the same configuration management system.

All custom elements of the site can be rebuilt and deployed from the configuration management system. This is useful in geographically distributed Web sites and disaster recovery.

You can maintain a baseline environment for disaster recovery or rollback from program errors.

Test / integration and pilot environments can be deployed using production-level projects.

Developed and authored elements are maintained using similar tools and processes.

After reading the above, do you have any further understanding of how to design and create your own Sharepoint Site? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.