The following terms are frequently used in the Site Studio suite of applications. They are listed here in alphabetical order.
An HTML page that includes one or more scripts, or small embedded executable code, that are processed on a Microsoft web server before being sent to a web browser. ASP pages have the .asp file extension. In Site Studio, you can create Web sites with Idoc Script, JSP (JavaServer Pages), or ASP.
It is important to note that sites created in ASP is limited to the functionality available in Site Studio 10gR3.
See also: legacy site.
An individual who uses the performs the administrative Site Studio tasks on the content server. This would include tasks such as assigning web addresses to the site, backing up the site, replicating the site, and so on.
See also: designer, contributor, manager.
The process of creating an extra copy of your Web site and all files associated with it for archiving or safeguarding. Site Studio's backup feature is accessed from Oracle Content Server's web interface (the Site Studio Administration page).
See also: administrator, restore.
A file that provides control over how page content is displayed. More specifically, how different HTML elements, such as headers and links, appear on the page. A means of separating structure from presentation to control the formatting and layout of content in one place. Style sheets can be included in an HTML document by linking to an outside style sheet, embedding a document-wide style in the <HEAD> tag of the document, or embedding inline styles where needed.
A unique identifier for each content item on the content server. Content IDs are assigned when content items are checked in to the content server. Depending on the server configuration, they may be assigned automatically, or the person checking in the item may have to assign the ID. Content IDs are stored in a metadata field called dDocName.
The central repository of all files associated with a Site Studio Web site. The server provides advanced content management features such as library services (check-in, check-out, and the like), versioning, workflow, content conversion, and more.
A specially formatted web form that can be used by a site visitor to submit information to a Site Studio Web site.
A detailed report that shows how many times a piece of content was viewed. The report is made available through the integration between Site Studio and Content Tracker (an add-on to Oracle Content Server).
See also: site report.
The graphic that displays beside each contribution region on the web page, when the page is viewed in contribution mode. Clicking the edit icon opens Contributor (or a third-party application for a native document), enabling contributors to edit the region content assigned to the region. Clicking the menu icon provides more options, such as switching the file assigned to the region and approving or rejecting a document for workflow.
A way of viewing a web page in a web browser whereby you can see and edit the contribution regions (and perhaps instances of Manager) on the page.
When the page is viewed in contribution mode, you see a contribution graphic beside each editable region. Click the graphic to edit the contents of the region (a data file or native document), approve it or reject the contents (when workflow is used), update its metadata, and so on. You enter contribution mode using a combination of keystrokes (the default is Ctrl+Shift+F5).
An area where contributors can add and edit content on a web page, as defined by the site designer. When the web page is viewed in contribution mode, contributors can edit the content in the region using either Contributor (for contributor data files) or the application associated with the content (for native documents).
See also: placeholder, replaceable region.
One of three applications in Site Studio. Contributor is used to edit contributor data files associated with a contribution region. The way you set up a contribution region and contribution elements in Designer affects the appearance and behavior of the Contributor application. Typically, you have many different contributors using the Contributor application.
See also: Designer, Manager.
An individual who edits the content on a Site Studio Web site, using either Contributor or a third-party application. The contributor can be anyone familiar with the content on the Web site (a manager, a member of the sales or marketing team, a member of human resources, and so on). Using Site Studio, you often have multiple contributors working with a handful of managers and one designer.
See also: designer, administrator, manager.
An XML file created by Site Studio and designed to be opened and edited using the Contributor application. A contributor data file stores site content, and can be assigned to a contribution region, where it appears on the Web site. The file itself, however, is stored as a managed content item in the content server, separate from the page templates, region templates, subtemplates, and other managed site assets. This enables content (created by contributors) to be separate from presentation (created by site designers).
See also: native document.
A section in the site hierarchy that only appears on the site when it is viewed in contribution mode. Contributor-only sections can be useful to convey information, like instructions for contributing to the site, from designers to managers, managers to contributors, and so on.
A file that specifies the conversion rules for native documents on a Web site. Each conversion definition is a rule, template, or combination that defines how a native document is converted to HTML and displayed in the page.
A statement that specifies what criteria a native document on the content server must meet to be converted using a specific conversion template.
A part of Dynamic Converter used in Site Studio to define how native documents are converted to HTML for viewing in a web browser. Native documents on the content server are converted based on their metadata and file type.
A type of element that uses a custom element form. A custom element is quite different from the other elements (WYSIWYG, plain text, dynamic list, static list, and image) in that it is used to create a custom interface (web-based form) in the Contributor application. Contributors use the interface to add various types of content and perform actions that cannot be performed in the other elements.
See also: WYSIWYG element, plain text element, image element, static list element, custom element form.
An HTML file that defines custom forms for use in elements (for example, selection forms for specific file types). Custom element forms are used to create a custom interface that contributors use to add and control various types of content to a Web site.
One of three views for displaying the site assets that are templates (page templates, subtemplates, and region templates). In design view, you see what your template looks like as you design it. You can use the formatting toolbar, properties pane, drag and drop, right-click mouse options, and many familiar word processing commands to edit the content in this view. Site Studio uses markers for fragments, placeholders, and similar items that do not display properly in a dynamic WYSIWYG environment.
See also: preview, source view, form view.
One of three applications in Site Studio. Designer provides the development environment where designers can create the site and site assets, add fragments and construct contribution regions, and more. The Designer application is used with Manager and Contributor to build and maintain a site.
See also: Manager, Contributor.
An individual who uses the Designer application to build Web sites. This individual might be a web master, web developer, or member of the web team. The designer focuses on how the Web site looks: the structure of the pages, the way the pages are laid out, the imagery, and the corporate identity. The actual site content is typically created and maintained by contributors.
See also: contributor, manager, administrator.
Content that is displayed in an area defined by a placeholder based on where the page template is used. In some cases, a fragment can also display content that is dynamically generated. When viewing a template in Designer that has dynamic content, a small box with the name of the fragment or the placeholder appears.
See also: static content.
A list of files (contributor data files or native documents) that is based on a query performed in the content server. You can have, for example, a dynamic list that queries the content server for files with the document type "Press Releases" and displays those items on the page. The list can be simple, such as a list of links, or it can be complex, such as a list showing the title, an excerpt, and a link for each file. The dynamic list can be implemented as an element, and can also be implemented as a fragment. In the Toolbox in Designer, you have a category called "Dynamic List Fragments," which includes sample dynamic lists.
In Site Studio releases prior to 10gR4, dynamic lists were created using a fragment. Starting with the 10gR4 release, dynamic lists can be created either by using a fragment or by creating a dynamic list element definition. The dynamic lists function similarly, but implementing dynamic lists as elements maximizes the reusability of the site assets.
See also: list fragment, static list.
Part of the Contributor editor workspace where contributors make changes to contributor data files associated with a contribution region on a Web page. Each editing area has its own toolbar and its own field for entering the data. In some cases, such as with an image or custom element, the editing area does not have any place to enter text. In many cases, there are more editing areas for data than appears on the screen. This could be because the contributor data file contains data not displayed on the web page, or that the designer has included areas meant to display only when Contributor is open.
See also: element toolbar, contributor-only section.
The smallest chunks of reusable information in a Site Studio Web site. When using contributor data files on your site, you must create one or more elements in each contribution region. Each defined element is of a particular type: WYSIWYG, text only, image only, static list, dynamic list, or custom. These types characterize what the element content consists of, and, through element definitions, what editing options are available to contributors. If you add just one element, the contributor sees one field in Contributor; if you add several elements, the contributor sees several fields in Contributor. Elements are not used with native documents, only contributor data files.
See also: WYSIWYG element, plain text element, image element, static list element, dynamic list element, custom element.
A file that defines the editing experience for element types. Specifically, they specify what a contributor can do when editing an element. Element definitions are also used to specify validation scripts.
Each editing area in the Contributor editor has a toolbar specific to the type of area. Some toolbars have WYSIWYG items, or text-only, or image-only. Static lists and dynamic lists also have their own toolbars.
See also: editing area.
A way for designers to enforce specific rules on the content that is added in Contributor. You can regulate how much content is added, whether it is formatted in a certain way, and much more. Element validation is set up in an element definition. You can use the default validation script that comes with Site Studio or create your own.
A widely used programming language (and standard by the W3C) that facilitates the interchange of data between computer applications. XML is similar to HTML (the language used for web pages) in that both use markup tags. However, as opposed to HTML, XML tags say nothing about the presentation of the data contained in the tags, only their structure. Computer programs automatically extract data from an XML document using its associated DTD as a guide.
One of the views of site assets available while in Designer. This view is the graphical interface to the different definitions (placeholder definition, region definition, element definition) and configuration settings (such as the manager configuration setting). The other view available to definitions and settings is source view.
See also: source view.
A container for code, files referenced by that code, along with parameters that govern how that code is added to a template. Using fragments, you can create and edit features for your site, while keeping them separate from the site. Site Studio includes numerous sample fragments that are provided in the Toolbox in Designer. You can open and edit fragments using the Fragment Editor. Fragments are written in eXtensible Markup Language (XML), and they are stored in fragment libraries in the content server.
See also: snippet, toolbox.
Part of the Designer application that is used to open and edit fragments. You can use the Fragment Editor to add and edit fragment properties, snippets, assets, parameters, and so on. You open the Fragment Editor each time you create a new fragment or edit an existing one from the Toolbox in Designer.
A collection of one or more fragments and their assets for use with a Site Studio Web site. It is stored as a managed content item in the content server. A fragment library comprises an XML (eXtensible Markup Language) file that describes all of its contents, and a zip file that stores its contents. The sample fragment libraries that ship with Site Studio are automatically checked into the content server when you install the component.
The identifying characteristics of a fragment, such as its name, type, and choice of scripting language. The first thing you do when you create or edit a fragment is specify its properties.
A dynamic web page containing HTML and the Idoc Script code (a proprietary scripting language). HCSP pages can request services from the content server. They have the .hcsp file extension. In Site Studio, you can build page templates and fragments with Idoc Script.
A page that serves as an entry point to the Web site. It generally contains links to the main sections of the site. In Designer and Manager, a home page is the same as a primary page: the only difference is that you add it to the root of the site hierarchy rather than to one of the sections of the site hierarchy. Many navigation fragments in the Toolbox contain a link to your home page.
A formatting language used for documents on the World Wide Web (WWW). HTML files are plain-text files with formatting code that tells a web browser (or web-capable device) how to display text, position graphics and objects, and display links to other web pages.
A way of presenting content in a tabular format. On a Web site, HTML tables can be used to position content and therefore, design web pages. In Site Studio, you can use HTML tables to design your page templates (such as placing fragments and contribution regions in each table cell).
A proprietary scripting language used to create dynamic Web pages in Oracle Content Server. Idoc Script provides the ability to reference variables, conditionally include content in HTML pages, loop over results returned from queries, and more. In Site Studio, you can build templates and fragments with Idoc Script. The file extension for assets in Idoc Script is .hcsp.
A type of element that allows only one or more images. An image element offers options specific to adding images for a contributor (such as browsing the content server for an image, replacing an existing image, and applying a CSS class to an image). This element can be useful when you want to specify an area where only an image (and no text) should appear on a web page.
See also: WYSIWYG element, plain text element, static list element, custom element.
A cross-platform scripting language that can be added to existing HTML code on a web page to create basic online functions and interactivity.
A scripting language for the serving-side use of servlets, or small programs, that run on the web server. JSP is similar to Microsoft's Active Server Pages (ASP); they both request programs from the web server before displaying the results in a client web browser. JSP pages have the .jsp file extension. In Site Studio, you can create a Web site with Idoc Script, JSP, or ASP.
It is important to note that sites created in JSP only has the functionality available in Site Studio 10gR3.
See also: legacy site, Active Server Pages (ASP).
"Layout page" is a term from pre-10gR4 Site Studio releases. The current term is page template.
See also: legacy site, page template.
Sites which are made with the functionality of the pre-10gR4 architecture. You can continue to use legacy sites in Site Studio 10gR4 and higher, but they do not take advantage of the new architecture and features introduced in Site Studio 10gR4 and higher.
An item on a web page that takes the user from one web page to another, or to a different position within a web page. Links enable visitors to navigate your Web site. In Designer, links are automatically created when you add a navigation fragment to a template. You can add more links yourself, usually to cross-reference another part of your site or perhaps another site. You can also enable contributors to create links on the Web site using the Contributor application.
A feature in Site Studio (Designer and Contributor) that enables you to quickly and easily creates links to other sections, to other files, and to other sites in the content server. The multi-step wizard walks you through the necessary steps to create the link, choose a target section or file for the link, and choose a format for the link.
A type of fragment that displays either a static list or a dynamic list. Static list fragments display a fixed number of rows and columns, each containing an element (WYSIWYG, plain text, or image). Contributors can modify the list, for example, by adding, editing, and deleting rows and columns of information. Dynamic list fragments display a list of files (contributor data files or native documents) based on a query performed in the content server. Contributors can add and remove the files that appear in this list.
See also: static list, dynamic list.
One of three applications in Site Studio. Manager is a web-based site management console that can be used by one or more site managers to maintain the structure of the site. Site designers can add the Manager application to a site in Designer. The look and feel and behavior can be changed for each instance of Manager.
See also: Designer, Contributor.
An individual who uses the Manager application to reorganize the site navigation and hierarchy. Site managers can add or remove sections to the site without using Site Studio Designer by using a web-based tool that the site designer makes available to them. A manager typically works with one designer and multiple contributors.
Files that define the functionality that is available in Site Studio Manager. The manager configuration settings are used to control what access levels the manager has when accessing the Manager application. These settings include if the manager can control the hierarchy and rearrange it, and if they can reassign a page template to a section.
"Data about data." In other words, information that describes the characteristics and properties of an item (such as title, author, content ID, and so on). As you build your site, you can use this metadata to handle the content in different ways, such as creating a dynamic list that queries content items matching a particular document type or security.
A content file created using familiar third-party applications such as Microsoft Word. Native documents are converted to HTML format using Dynamic Converter, and they are edited using their associated application.
See also: contributor data file.
The way visitors make their way around a Web site. The navigation on your Web site is usually a collection of links that point to each main category, or section, on the site. In Site Studio, you can add a navigation fragment from the Toolbox, and it instantly creates a navigation menu, pointing to each section in your site hierarchy.
A fully-formed HTML file that defines the layout and high-level look-and-feel of web pages, including the placement of contribution regions (that is, editable areas on the page), navigation aids (in the form of fragments) and site-wide images (banners and the like). Page templates are the highest-level site design object.
An attribute that governs the appearance and behavior of a fragment or other managed content. You can specify a set of parameters when you create a new fragment, and you can enter values for the defined parameters when you add the fragment to a page template, subtemplate, or region template.
An insertion point (a tag) on a page template to identify where there is a contribution region (that is, editable area) on the Web page. They are simply conceptual spaces where other content is displayed when the page template or subtemplate is viewed in the context of the Web site.
See also: replaceable region, contribution region.
A file that defines what region definitions, region templates, and subtemplates are allowed for the associated placeholders. They also specify what contributor actions are allowed for the placeholders.
A type of element that allows only text, without modifying the font or other formatting modification. A plain-text element typically offers only the minimum editing options for a contributor (such as cut, copy, paste, and spell checker). This element can be useful when you want to prevent contributors from manually formatting the text on a web page (such as a title or heading).
See also: WYSIWYG element, image element, static list element, custom element.
One of three views in Designer for viewing a template (page template, subtemplate, and region template). The Preview tab provides an actual view of the page template, subtemplate, or region template as it appears in a web browser. Preview is useful for previewing dynamic (server-side) content, fragments, and contribution regions, since the content in these cases must be generated in order to be seen fully.
See also: source view, design view.
The landing page of a site section. This page is the page displayed when a visitor first enters that section. It represents the "index" file of the site section.
See also: secondary page.
An XML file that stores all information about a Site Studio Web site on the content server. Project files are created by Site Studio when a new site is created in Designer, and the file is stored in the content server as a managed content item.
A pane in Designer summarizing the properties of a section, page template, default placeholder definition, element, fragment, HTML tags, and more. The properties pane enables you to view and edit the HTML tags of your templates. You can make many of the same changes in the properties pane that you make to the template directly. The properties pane is especially useful for actions that cannot be performed directly in design view; for example, specifying background color, page margins, and table width.
The process of deploying a completed Web site to a location so that it can be viewed by visitors. Web sites can be deployed in Site Studio using Site Studio Publisher. This involves gathering all of the files associated with a Web site, building a static copy of the Web site, and then copying the completed site to a "live" location.
The data assigned to display in an editable area (contribution region) on a web page. This can be a contributor data file or a native document. Contributors are generally responsible for the region content (in the same way that designers are responsible for page templates and fragments). Once you assign region content to a contribution region, contributors can edit the content using Contributor (if using contributor data files) or a third-party application (if using native documents).
A file that defines the type of content that elements of a particular type consists of. It also specifies the content creation and switching options available to contributors for contribution regions, and sets default metadata for content files associated with these regions.
A partial HTML file (that is, without head and body sections) that defines the layout and look-and-feel of the data in contribution regions within web pages.
A region on a secondary page that allows other files (specifically, new contributor data files and native documents) to display. When contributors add new content to the site, the content displays in the replaceable region on a secondary page. The result is that contributors can add new web pages to the site without designers having to create new sections and new page templates each time.
See also: placeholder, contribution region.
The process of copying a Site Studio Web site from one content server to another. You might do this when distributing a site from a development environment to a production environment, backing up the contents of a site, and so on. You use the Site Studio Replicator or Content Server Archiver/Replicator to replicate sites in Site Studio.
A Site Studio feature accessible from the Site Studio Administration page on the content server. You can use the backup and restore feature to quickly and easily back up your entire site (or sites), store it in a compressed ZIP file, move it to another location, and restore your site from this file.
An individual who approves content on the site. A reviewer can use the workflow options on the contribution icon to approve and reject content. A reviewer might have the sole responsibility of reviewing content, or the reviewer might be a contributor acting in both roles.
Code that is added to a web page to make it more effective in displaying information or interacting with the user.
A page of a section typically used to display dynamic content. A secondary page can have static content, but what makes secondary pages useful is their ability to have dynamically placed and replaceable content. As such, they are used to create multiple versions of the pages within a site section; they provide a different content view for a site section. Secondary pages allow you to handle large sites without needing to physically create thousands of pages.
See also: primary page, page template.
A category or specific area in your site hierarchy. You generally create sections in your site hierarchy that represent common parts of a Web site, such as Products, Services, and About Us. The sections in your site hierarchy display in the navigation menus on your Web site. As such, you may use the sections to organize your site, while visitors use the sections to navigate the site. In Designer and Manager, you create sections in the Site Hierarchy pane and then add a primary and (optionally) a secondary page to each section.
A name associated with a Web site that allows visitors to locate the site with a web browser.
There are two kinds of addresses that you can use: a domain name address and a folder name address. A domain name address looks something like "http://www.mycompany.com" (where "www.mycompany.com" is the domain name), and a folder name address looks something like "http://UserPC/mysite" (where "UserPC" is the name of the computer hosting the site and "mysite" is the ID of the site).
A file associated with a Site Studio Web site and used to build a web page in some way (including a fragment or region definition in the page template as well). Graphics, cascading style sheets, and custom scripts are all frequently used site assets. You use the Site Assets pane in Designer to add and edit these files.
A pane in Designer summarizing the files used on the Web site. The files are grouped based on their use (page template, image, contributor data file, native document, and so on). You can use the Site Assets pane to preview, edit, and identify the location of an asset. You can also add new and existing files to the Site Assets pane, thus making those files part of your site.
What Designer uses to connect to and update a Web site stored on the content server. A site connection works much like a typical shortcut that you might add to your desktop for quick access to remote files. You can add, modify, and delete site connections without actually affecting the Web site in the content server. You can add as many site connections as you like, each going to a different Web site on the same content server or to different content servers.
A collection of individual sections and page templates that make up the structure of the site. The site hierarchy can be flat, where all sections are located at the top of the hierarchy, or it can be deep, where sections are placed within other sections. Similar to a folder in a folder hierarchy, each section in a site hierarchy is necessary to store related content. While you may think of a site hierarchy as a place to categorize and manage content on your site, Site Studio uses the site hierarchy to manage page templates and generate navigation links on your Web site, both of which are essential to the organization of your Web site.
See also: section.
The pane in Designer and Manager where you can create and maintain the site hierarchy for the Web site. The default location for this pane is in the upper left corner of the workspace.
A listing that displays the total number of files used by a Web site (or Web sites) and to see where those files are being used. There are three kinds of site reports that you can view: Web site objects report, Web site usage report, and Content Tracker report.
See also: Content Tracker report, Web site usage report, Web site objects report.
A powerful, flexible web development application suite that offers a comprehensive approach to designing, building, and maintaining enterprise-scale Web sites. It goes beyond conventional Web site development solutions by offering Web site creation and content management all in one. Everything associated with the Web site, including all site assets (such as templates, graphics, CSS files, and the like) and all site content, is stored and managed in the content server.
A section in the Oracle Content Server web interface where you can perform many administrative tasks for Site Studio, such as assigning web addresses to a site, backing up sites, and so on.
The text or code that you store in a fragment, defined by its insertion point in the page template. When you create a fragment, you must add one or more snippets to it. In each snippet, you must specify how it is inserted within the fragment: drop-point, head, top of body, or bottom-of-body. If you are using the fragment to insert text or code in one place in the template, you can create just one snippet. But if you know that parts of your fragment must be inserted in more than one place in the page template, then you must create a snippet for each. If a snippet is defined as placed in the head, then it should not be used on subtemplates or region templates, as these templates do not have headers. You add, edit, and remove snippets in the Fragment Editor.
See also: fragment.
One of three views in Designer for displaying templates (page templates, subtemplates, and region templates). Source view displays the code that makes up the template. You have complete control over the template while working in source view. If you do not like the way something looks in design view, you can always switch to source view to change it. You may, in fact, find yourself starting off in design view to initially create the template and then switching to source view to fine-tune the appearance and behavior of the template.
See also: preview, design view, form view.
All content placed directly on a template, making it not editable by the contributor.
See also: dynamic content.
A fixed number of rows and columns, each containing a contribution element (WYSIWYG, plain text, or image). Static lists can be used to bundle several elements in a table-like layout. Contributors can, therefore, add, edit, and delete the rows and columns of information, even rearrange them. Within each element, contributors have the same editing capabilities that they have in a standalone element. A static list can be implemented as an element, or as a fragment. In the Toolbox in Designer, you have a category called "Static List Fragments" that includes sample static lists.
See also: dynamic list.
In Site Studio releases prior to 10gR4, static lists were created using a fragment. Starting with the 10gR4 release, static lists can be created either by using a fragment or by creating a static list element definition. The static lists function similarly, but implementing static lists as elements maximizes the reusability that all site assets have.
See also: list fragment, plain text element, image element, static list element, dynamic list element, custom element.
A partial HTML file (that is, without head and body sections) that can be inserted into a placeholder on a page template to divide the placeholder into further smaller, reusable areas with their own placeholders and contribution regions. Subtemplates may contain very simple HTML code, but they may also be quite complex, with their own scripts and the like.
A feature in Site Studio (Designer and Contributor) that enables you to quickly and easily change the content of a contribution region. The multi-step wizard walks you through the necessary steps to change the contributor data file, native document, or even subtemplate (if the site designer has enabled changing the subtemplate).
The section on your site where a contributor data file or native document displays when you click a link that goes to that file. You can specify a target section for these files on your site or let Site Studio go through a linking evaluation to determine where the content should display. With target sections, you can make a file display on your Web site without moving it or changing its metadata attributes in the content server. As a result, you can share and reuse content on one or multiple Web sites using target sections.
A reusable piece of HTML code (with scripting code and the like). Site Studio 10gR4 uses three template types: page template, subtemplates, and region templates.
See also: page template, region template, subtemplate.
A window in Designer that shows all of the fragments on the content server. They are divided into four categories: navigation fragments, dynamic list fragments, static list fragments, and other fragments. You use the toolbox to add a fragment to a template or edit the fragment directly using the Fragment Editor. You may, on occasion, have to refresh Designer to see the latest fragments available on the content server (if your organization has multiple designers).
See also: fragment, Fragment Editor.
The address that defines the route to a file on an internet server (web server, FTP server, mail server, and so on).
A file containing HTML and possibly scripts, intended for viewing in a web browser. In Site Studio, a page template is combined with contribution regions, contributor data files, native documents, images, and other site assets to form a web page that the user sees in a web browser.
A collection of HTML or script-based web pages that are linked and stored on a server. In Site Studio, a Web site is defined by its site hierarchy, navigation scheme, and page templates. It is stored, managed, and served up by Oracle Content Server (which means you can take advantage of the many built-in content management features on the server).
A report that shows all of the explicitly referenced files on the content server used by a site. This report displays files by category (page templates, contributor data files, fragment libraries, and so forth).
See also: site report.
A report that shows a detailed summary of information for a single file, specifically where it is being used. The report breaks this down by Web sites where it is used, sections where it is used, and so on.
See also: site report.
A feature in Oracle Content Server that can be used in Site Studio to review the content of a Web site before it is released for publication. A single workflow can address a portion of a single web page or all of the content on the site. Typically, multiple workflows might be used to review different portions of a Web site. Designated reviewers have the authority to approve or reject content during the workflow process.
A type of element that allows full formatting and editing of the content. A WYSIWYG element typically offers all possible formatting and editing options, such as changing the font, centering text, and creating links to new and existing files. Site designers can enable and disable each option to customize the contributor's experience.
See also: plain text element, image element, static list element, dynamic list element, custom element.