Published intranets in SharePoint Server 2010
A published intranet site is a site that is internal to an organization and uses the publishing features in Microsoft SharePoint Server 2010 to host content for the entire organization. This is usually the main communications site or portal for the organization. Typically, such a site is not available to external users. The site is usually branded and is not a collaboration mechanism, but rather a place to consolidate information that needs to be widely shared with the whole organization.
Send feedback about prototype
Follow these tasks in the order they are presented to create and operate a published intranet site for your organization.
The following downloads are available:
This section suggests some typical steps to take during the evaluation phase before a project is planned. An organization might use different steps or perform steps in a different order to meet its unique needs.
1.1 Evaluate organization needs
1.2 Evaluate software capabilities
1.3 Review requirements
1.4 Exit criteria
In this step, you determine your high-level needs for an intranet site. Include both technical decision makers and business decision makers in this process. Do not plan your specific implementation, but instead take time to identify requirements and constraints.
1.1.1 Identify business goals
1.1.2 Determine availability, capacity, and performance requirements
1.1.3 Identify functional requirements
1.1.4 Determine operations criteria
1.1.5 Identify staff and resource constraints
2.1 Train IT and development staff
2.2 Determine key vision or identity for the site
2.3 Plan information architecture
2.4 Define implementation-wide requirements
2.5 Define content requirements
2.6 Plan site structure
2.7 Define page structure
2.8 Plan style design
2.9 Plan custom development and extensibility
2.10 Plan for browsing and search
2.11 Plan solution architecture
2.12 Plan integration with related solutions
2.13 Create project plan for overall effort
2.14 Verify that site design complies with governance plan and meets organization needs
2.15 Create training plan and gather training materials and resources
2.16 Order hardware
2.17 Exit criteria
Before you begin your project, make sure your IT and development staff members are fully trained to use SharePoint Server 2010. Training videos and labs are available on TechNet and MSDN.
3.1 Review application lifecycle management (ALM) best practices
3.2 Create proof of concept
3.3 Create custom connectors
3.4 Develop customizations to global layout
3.5 Create publishing page layout
3.6 Test browser support
3.7 Create custom navigation
3.8 Develop custom Web Parts and forms
3.9 Create custom search experience
3.10 Create custom site templates
3.11 Optimize code performance, Validate Solution and fix bugs
3.12 Create strings for multiple locales
3.13 Create the solution package
3.14 Create operations plan and train operations staff
3.15 Exit criteria
Plan and implement an application lifecycle management (ALM) process that integrates the SharePoint Server 2010 development tools and capabilities with the specific requirements and needs of your project.
Follow the steps in this section to deploy your published intranet to both test and production environments.
4.1 Run and test a pilot solution
4.2 Prepare the servers
4.3 Deploy the published intranet solution
4.4 Create metadata
4.5 Train content authors and content approvers
4.6 Author and import content
4.7 Grant permissions to site visitors
4.8 Configure monitoring options
4.9 Perform operational maintenance tasks
4.10 Set up and configure regional farms
4.11 Roll out the site
4.12 Exit criteria
As a best practice, create a pilot project and test your published intranet solution with representative users to ensure that it works the way you want it to. Then, make any adjustments before deploying to your production environment.
5.1 Farm administrator operations
5.2 Content and site owner operations
5.3 Author and approver operations
5.4 Site visitor operations
In this section, you manage your farm to keep all services, servers, and sites running effectively.
5.1.1 Monitor and tune server farm performance
5.1.2 Manage business continuity
5.1.3 Install software updates
5.1.4 Update search terms
5.1.5 Maintain services