SharePoint Terminology

Here are some important terms pertinent to SharePoint Technology:

• Application page: Allows the use of inline custom code. Application pages or "_layout" pages are stored on the SharePoint Web server and made available via a Microsoft Internet Information Services (IIS) virtual directory. Though application pages behave much like other ASPX pages and allow the use of inline custom code, they differ from content pages in that they cannot be used to host SharePoint features such as dynamic Web Parts and Web Part zones.
• Content type: A reusable collection of settings to apply to a certain category of content such as documents and folders. Content types are designed to help users organize their SharePoint content in a more meaningful way.
• Custom action: Represents a link, toolbar button, menu item, or any control that can be added to a toolbar or menu that appears in the UI. We define custom actions by using a custom action element within a feature definition file. We can bind custom actions to a list type, content type, file type, or programmatic identifier (ProgID).
• Event receiver: Evaluator of an event and definer of the behavior of an application. Windows SharePoint Services 3.0 allows us to define event handlers within libraries, lists, and sites. Event receivers can be defined by using a receiver element within a feature definition file.
• Feature: A package of Windows SharePoint Services elements that can be activated for a specific scope and that helps users accomplish a particular goal or task. Windows SharePoint Services 3.0 introduces this inherently portable and modular functionality, which simplifies modification of sites through site definitions.
• Master page: Pages that provide a consistent layout and appearance (look and feel) for SharePoint sites. They allow us to factor out layout, structure, and interface elements such as headers, footers, navigation bars, and content placeholders. Master pages in ASP.NET 2.0 and master pages in Windows SharePoint Services work in the same way.
• Module: A file or collection of file instances that define the location where the files are installed during site creation. Modules are frequently used to implement a Web Part Page in the site. We can define modules by using a module element within a feature definition file.
• SharePoint site: A Web site hosted in a virtual URL. A SharePoint site is a place for collaboration, communication, or content storage. Depending on your business needs, we can create sites such as team sites, blog sites, wiki sites, and others. We can customize a site's appearance, users, user permissions, galleries, and site administration by using the Site Settings administration pages.
• SharePoint site collection: A collection of SharePoint sites that share common administration pages and site settings. Site collections allow you to share content types, site columns, templates, and Web Parts within a group of SharePoint sites.
• SharePoint Web farm: A group of Office SharePoint 2007 servers that share the same configuration database. All site content and all configuration data is shared for all front-end Web servers in a server farm.
• Site definition: A set of files that includes a master XML configuration file that is stored on all front-end Web servers. A site definition provides the basic blueprint for how sites look, what lists they include, their default navigational structures, and so on.
• Site template: A package containing a set of differences and changes from a base site definition that is created through the UI or through implementation of the object model. The site template package is stored as a .cab-based file that can be downloaded or uploaded to site collections by users with the appropriate rights. Site templates offer a measure of portability to SharePoint applications.
• Solution: A file that is a bundling of all the components for extending Windows SharePoint Services in a particular way. A solution file has a .cab-based format with a .wsp extension. A solution is a deployable, reusable package that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. We can use the solution file to deploy the contents of a Web Part package, including assemblies, class resources, and other package components.
• Theme: A group of files (CSS, images) that allow you to define the appearance (look and feel) of Web pages. Themes in ASP.NET 2.0 and themes in SharePoint Products and Technologies work in the same way. Themes are used to help organizations to brand their portals and team sites. Office SharePoint Server 2007 includes a set of predefined themes. However, as a developer, we can create custom themes for our company.