- Inserting Text, ScreenTips, Hyperlinks, and Images
- Working with Web Parts
- Changing the Home Page for a Web Site
- Modifying a List View Page
- Creating List View Pages
- Creating and Modifying a List Form Page
- Creating an ASP.NET Page
- Inserting a Web Part Zone
- Attaching a Master Page
- Managing Web Pages
- Key Points
On Wiki pages, only the content within the EmbeddedFormField SharePoint control can be modified using a browser, and on Web Part pages, only content within Web Part zones. In SharePoint Designer in advanced mode, you can modify content outside these areas.
In the Page Editor Options dialog box, you can configure picture conversion formats, auto thumbnail creation, and settings for Design and Code views.
Web Parts can be inserted outside Web Part zones and the EmbeddedFormField SharePoint control on content pages and on master pages by using SharePoint Designer. These are known as static Web Parts. Web Parts inserted into Web Part zones or the EmbeddedFormField SharePoint control are known as dynamic Web Parts. Details of dynamic Web Parts are stored in the SQL Server database separate from content pages and master pages.
View pages and form pages both consist of one Web Part zone (named Main) and one Web Part. In the case of a view page, the Web Part is an XLV. In the case of a form page, it is an LFWP.
You can create a custom data entry form by using a DFWP.
A nonpublishing page is the combination of two ASP.NET pages: a master page and a content page.
A SharePoint Server publishing page is a combination of three ASP.NET pages: the master page, a page layout, and a content page. You cannot modify a publishing content page by using SharePoint Designer; you must use the browser. However, you can modify the master page and page layout by using SharePoint Designer.
Design view for a content page shows the merged view of the master page and the content page, whereas Code view shows only the code of the content page.
In SharePoint Designer, you can create an ASP.NET page and then attach a master page to give it the look and feel of the SharePoint site.
Any pages or files you delete in SharePoint Designer are sent to the Recycle Bin, from which you can restore them.
SharePoint Designer saves all pages to the SQL Server content databases. You can reset pages to site definition pages if they originally pointed to them.