Ingeniux Content Management System v5.0. User s Guide for the Author Client

Transcription

1 Ingeniux Content Management System v5.0 User s Guide for the Author Client

2 Who Should Read this Guide...4 System Requirements Installation Pre-Installation Checklist Installing the Author Client Starting the Author Client Troubleshooting Application Startup Client Prompts for Microsoft Office CD General Troubleshooting Steps Overview of Author Client Getting Started Author Client Interface Information Pane (Left Column) Assignments List Search Site Map Toolbar Page Content Tab Overview Tab Edit Tab Preview Tab Keyboard Short Cuts Formatting Toolbar Creating a New Page Adding Content: the Edit Form Data Types Access Levels Required Fields Tracking Changes Revision Marks: Changing the Version: Revert To : Finishing Check Spelling Preview Assign or Advance Assign Advance Pages in Workflow vs. Pages not in Workflow Pages in Workflow Pages Not in Workflow Finding Existing Content Author Client in Detail Edit Form Data Types Plain text Formatted text (WYSIWYG) Dates Enumerated Lists Boolean Values

3 3.2.6 Component Element Narrowing Down the List Image file Elements Image file Element Attributes Media File Elements Document Elements Link Element Insert Element Navigation Element dbquery Com Execute Element Read-Only and Hidden Fields Required Fields Layout Field DHTML Control Format Editor Toolbar Form Editor Toolbar Text Formatting DHTML Context Menu Dragging and Dropping from other Applications Working with Images and other Assets Uploading Images and other Assets Inserting Image Components onto Pages Inserting Images into the WYSIWYG control Assignment List Site Map Moving and Copying Pages in the Tree Cross Site Copy - Copying Files from Other Sites The Context Menu Search Constructing a Query Searching Archived Files Using the Search Results Copying Archive Files Cross Site Copy - Copying Search Results From Other Sites Advanced Search Concepts Spelling Checker Check Spelling Dialog Options Dialog Dictionaries Dialog

4 Who Should Read this Guide This user s guide should be read by all content contributors required to use Ingeniux CMS Author client and by administrators supporting these content contributors. System Requirements The author client requires the following: Microsoft Internet Explorer v6.0 or higher Windows 2000, or Windows XP Microsoft.Net Framework 1.x or higher A connection to the Design Time Server Sufficient local permissions to install Active X controls 1. Installation This section can be skipped if the Author client has already been installed on the client computer. 1.2 Pre-Installation Checklist The following checklist provides a list of steps to perform prior to the installation of the Ingeniux Author Client: Verify Client meets hardware/software requirements Verify.Net Framework 1.1 is installed (Check Add/Remove Programs). Note.Net Framework 2 can be installed as well but the Ingeniux Client requires.net Framework 1.1. Verify all pop up blockers such as the Google or Yahoo Tool bars or the Internet Explorer pop-up blocker are turned off. The Internet Explorer pop-up blocker can be turned off by going to Tools Pop-Up Blocker Turn off pop-up blocker from the IE menu. Verify any personal firewalls are turned off. For Windows XP, go to Start Control Panel Windows Firewall Off. Verify any software configured to block the installation of Active X controls, prevent connecting to new sites, or block TCP/UDP port 80 in both directions is turned off. Verify that the IE security settings are set to Medium. This setting is located in the Tools Internet Options Security Tab Internet Icon Custom Setting button Reset to Dropdown. If a change is 44

5 required, make sure the user records their settings and then change the dropdown to Medium and select reset. (Note different versions of Internet Explorer may vary slightly.) 1.2 Installing the Author Client To install the author Client, access an Ingeniux CMS site from an Internet Explorer browser and the appropriate ActiveX controls will be downloaded to the hard drive. The browser must be configured to accept downloaded ActiveX controls in order for the client components to be installed. On the main menu bar, choose Tools Internet Options Security tab Internet Custom Levels, then select Prompt under Download signed ActiveX controls. Click OK. Figure 1: Internet Explorer Active X Settings In addition, an appropriate level of local permissions to the local machine is required to install programs (the author client in this case) on the local machine. If the Active X Control download fails, verify these permissions are in place or see the system administrator. Please note an MSI package may be provided by your system administrator- which can run and install the necessary Active X controls locally. Please see your administrator if you have difficulties installing the necessary active controls. 1.3 Starting the Author Client To start the Author Client, type the uniform resource locator (URL or World Wide Web address) for the Ingeniux site in the address bar of an Internet Explorer browser. The format is usually: [ServerName]/[SiteName] Or Once the client starts, a login dialog prompts for the user s credentials. This login dialog box prompts for the following information: User Name: Enter network login user name. Password: Enter password. 55

6 Domain: Enter the domain where the login is authenticated under. See the system administrator if for this information. Figure 2: Windows NT Domain Login Note the domain and user name may need to be entered in the following format if no domain option is present by the login dialog: [Domain]\[user name] In some networks using LDAP Authentication, a username and password is all that is required. Please see you administrator for the specific login format required for your site. If accessing an Ingeniux site for the first time, the browser prompts the user to download two signed controls. Click Yes to download these controls. Once downloaded, the browser will not prompt the user to download the controls unless the Ingeniux Design Time Server has been updated. The Author client remembers the window size and location of the last browser instance that was closed under normal circumstances. Listed below is the progression of client install screens: Figure 3: Ingeniux 5 Client Controls 66

7 Figure 4: Install Directory Figure 5: Confirm Client Installation Figure 6: Installing Ingeniux 5 Controls 77

8 Figure 7: Installation Complete Please note that the following error message may occur if the Ingeniux V5 Client is already in use when attempting to install another version: Figure 8: Ingeniux V5 Client Loaded Error Message To remedy this situation please try the following: A. Close all instances of the Internet Explorer Browser and then re-connect to the Ingeniux Design Time Site. B. Remove the Ingeniux CMS 5 Controls from Add/Remove Programs and then re-connect to the Ingeniux Design Time Site. Figure 9: Add/Remove Programs 88

9 1.3 Troubleshooting Application Startup Issue 1: Attempting to log in with credentials which do not match any user credentials in the Ingeniux CMS Users file generate the most common error. In the case below, the user logged in as sonyvaio\private but does not match a user in the Users file. Solution1: Either log in as a user that is already in the Users file, or have an administrator add a user to the approved users in the Users file. Figure 10: Invalid User Error Message Solution2: Enter credentials username (and domain if needed) in lower case, i.e. campus\jwaters. Issue 2: Another warning encountered occurs if the site is an earlier Ingeniux version than the ActiveX controls on currently installed on the machine: Figure 11: Newer Active X Controls Message Solution1: This is an information dialog and does not indicate a problem with the software. Simply click OK. This dialog appears if a customer connects to one site with a newer build of the same release, downloads the ActiveX control, and then connects to a different site using a previous build. NOTE: If the user accesses a site based on a version of the software that is newer than the controls currently on the user s computer, CMS will automatically try to download the newer controls. If the user downloads the newer controls and then tries to access an older site, the dialog shown above appears. NOTE: Internet Explorer configurations, Pop-Up Blockers, or Anti-Virus programs preventing the use of scripts, the use of Active X Controls, or the 99

10 spawning of additional browser windows interfere with the client s functionality and may prevent the client from performing as designed. 1.4 Client Prompts for Microsoft Office CD Launching the Ingeniux Client prompts for a Microsoft Office cd. Solution: 1. Open Notepad 2. Copy and Paste the following lines to Notepad: msiexec /i { E1-11D2-B60F C998E7} /qb- REMOVE=HTMLSourceEditing msiexec /i { E1-11D2-B60F C998E7} /qb- REMOVE=HTMLSourceEditing msiexec /i { E1-11D2-B60F C998E7} /qb- REMOVE=HTMLSourceEditing msiexec /i { E1-11D2-B60F C998E7} /qb- REMOVE=HTMLSourceEditing 3. Go to File Save and type in the following: triedit_fix.bat. 4. Execute the file. If this fails, please provide the Microsoft Office CD to install the necessary files. 1.5 General Troubleshooting Steps 1. Encountering trouble downloading the controls, Solution: Download the Active X installer (IGXUI_5*.msi) to the local computer and run the installation package locally. 2. Trouble installing the controls. Solution: Ensure the current user has administrative privileges on the box (or have sufficient privileges to install active x controls). 3. Encounter trouble launching the site after logging in. Solution: Go to Start Control Panel Add/Remove Programs and uninstall the Ingeniux client. Then, reinstall (preferably from the manual installer) the controls and try again. 10

11 2. Overview of Author Client This section provides a quick overview of the Author Client interface and provides a generic set of instructions towards using the Author Client to create site content. A detailed description of the Author Client functionality is documented in Section Getting Started To start the Author Client, type the uniform resource locator (URL or World Wide Web address) for the Ingeniux site in the address bar of an Internet Explorer browser. The format is usually: [ServerName]/[SiteName] Or Once the client starts, a login dialog prompts for the user s credentials. This login dialog box prompts for the following information: User Name: Enter network login user name. Password: Enter password. Domain: Enter the domain where the login is authenticated under. See the system administrator if for this information. Figure 12: Windows NT Domain Login Note the domain and user name may need to be entered in the following format if no domain option is present by the login dialog: [Domain]\[user name] In some networks using LDAP Authentication, a username and password is all that is required. Please see you administrator for the specific login format required for your site. 11

12 2.2 Author Client Interface The Author Client user interface (UI) consists of three main elements: Left-hand information pane Right-hand Edit/Preview area Toolbar Deleted: <sp><sp><sp> Toolbar Edit/Preview Pane Left Info Pane Figure 13: Author Client Interface Information Pane (Left Column) This area of the screen contains a list of pages currently assigned to the current user when the Assignments tab is selected, a search pane if the Search tab is selected, or a tree view if the Site Map tab is selected. 12

13 2.2.2 Assignments List The Assignments pane shows a list of all pages assigned to the current user. When a new page is created by a user, that page appears in that user s Assignments list until the page is assigned to another user (Send To) or transition the page to the next workstate. Other workers may assign pages that they have created or someone else in the group may send a page using the Send To feature. These pages will also show up in your Assignments tab. (See Assignments Task Graphic below.) Figure 14: Assignments Tab Search Selecting this tab launches Search, which is used for finding stories, images and other items in the design-time Content Repository. Search results display within this pane. More information can be found in the Search Section (4.18) of this document. Figure 15: Search Tab 13

14 2.2.4 Site Map Selecting the Site Map tab gives the user a hierarchical view of how content is structured in the Content Repository and provides a way to change the order of items on the site. This tab may not be visible if the current user does not have permissions to see site tree. Figure 16: Site Map Tab 14

15 2.2.5 Toolbar This area of the screen contains the command buttons that users will use in the process of creating pages and publishing them to the Web. These are described below: Figure 17: Toolbar New Save clicking on the New icon will invoke the New Page dialog. Clicking on the dropdown arrow to the right will specifically allow the user to choose a new Folder, Page, or Component. New items are created by default as children of the currently selected item in the Site Map. saves changes made to the current page. / Check In/Out checks in or checks in page, saving page edits depending upon the status of the current page.. Refresh refreshes assignment list. Rename renames selected page. Upload Show Differences Spelling imports images and other media into the Content Repository to be used as components in pages or add directly to the WYSIWYG control. opens a comparison pane that highlights differences between a document and the saved, checked-in, or previous version of the document. runs the Spell Checker on the current page. Assign To Advance in Workflow Help assigns the current item (i.e., the item currently active in the Edit form) to any other person who belongs to the current group. transitions current page to the next workstate. The caption of this button is taken from name of the next allowed transition (e.g., Send for Approval ) and depends on the workflow that is attached to the page and the current page s workstate. If more than one transition is available from the current workstate, the button will display as a combo drop-down button with all available transitions listed in the dropdown menu. launches help file. Table 1: Toolbar Options 15

16 2.2.6 Page Content Tab This area of the screen, called the Edit Form, provides the main editing area for creating new pages or reviewing or editing existing pages. The top of this page displays information such as page name, page ID, who the page is assigned to, what workstate the page is in if it is in workflow, and any comments from the person assigning the page. Selecting an item in the Search results pane will open the item in the lower half of the Edit form in order to view the content of the item. Figure 18: Status Bar Figure 19: Status Bar Expanded There is some helpful information in the Status Bar at the top of the edit form (just below the toolbar in the right edit pane) that the following information appears from left to right: Page Name: Name of the page. Page ID: This is the ID automatically assigned by the system, and is sometimes helpful for identifying pages. Assigned To: lists the user to which the current page is assigned. Last Modified: lists the date and time the page was last modified. Last Modified By: lists the user whom modified the page last. Start Date: (if set in page properties) lists the Start Date for a page. End Date: (if set in page properties) lists the End Date for a page. Publish As: (if set in page properties) lists the Publish As Name for a page. 16

17 2.2.7 Overview Tab The Overview Tab provides a brief snapshot of system and content based management information. The information displayed on this tab depends upon the user s permissions. Typically, the Overview tab will display all logged in users and recent pages that the user has edited. Figure 20: Overview Tab Edit Tab The Edit Tab provides the main interface to view a particular page s elements and properties. In addition, the Edit view provides the main interface for editing and creating content. If the page is checkout to the logged in user, these elements can be edited; content can be added. Please note an element marked as read-only can not be edited; an element marked as hidden will not be displayed in this view. 17

18 Figure 21: Edit Tab Preview Tab Clicking the Preview tab provides a rendering of the current page, as it will look when published. This preview is completely functional, with all navigation, links, etc., appearing and functioning as they will on the published site. This provides a useful alternative to the Assignment list, Search, or the Site Map as a means of finding content. 18

19 Figure 22: Preview Tab Keyboard Short Cuts These functions are available based on the User Group permissions set for the logged in user. Keyboard Shortcut Action Keyboard Shortcut Action CTRL + ALT + N New Folder F2 Help CTRL + SHIFT + N New Check in a CTRL + SHIFT + I Component page CTRL + S Save CTRL + SHIFT + O Check out a page CTRL + SHIFT + P Preview Page CTRL + D Show Differences CTRL + SHIFT + R Rename Page CTRL + N New Page CTRL + M Upload CTRL + T Advance through Workflow ALT + ENTER Properties CTRL + K Assign to Table 2: Short Cut Keys Formatting Toolbar CTRL + X Cut CTRL + F7 Spelling Checker CTRL + C Copy CTRL + F5 Refresh Tree CTRL + V Paste DEL Delete The Formatting toolbar appears across the top of the WYSIWYG (or What You See Is What You Get) control when a page is in an editable state. From left to right across the top of the toolbar, the following controls are available: Figure 23: Format Editor Toolbar Search and replace function Cut Copy Paste Text Paste from Word (Remove Word specific formatting) Undo Redo Remove Style/Class Remove Formatting Remove Empty Tags Remove Word Specific Formatting Remove Span provides mechanism to search and replace text strings in editor. cuts selected text. copies selected text. pastes text from previous Cut or Copy action. pastes text from Word document without word specific formatting. undoes previous action. re-applies previous action. Removes Style/Class applied to selected text. Removes Text formatting applied to selected text. Removes empty tags in editor. Removes Word specific formatting from specific text. Removes span tag in selected area. Table 3: Format Toolbar Options 19

20 Figure 24: Form Editor Toolbar Options Create link from selection Insert anchor Insert image from Web Insert table Insert rule Insert div Insert Form Insert Paragraph Bold Italic Underline Text Color Background Color Left Justify Center Justify Right Justify Full Justify Ordered List Bulleted List Indent Outdent creates a link. inserts anchor tag to be modified in the HTML tab. inserts image from another Web page. creates table. inserts horizontal line. inserts an opening and closing Div tag in the selected space. inserts an Iframe in the selected space. creates new paragraph. bolds selected text. italicizes selected text. underlines selected text. changes color of selected text. changes the background color for selected text. justifies selected text to the left margin. justifies selected text to the center. justifies selected text to the right margin. justifies selected text to the left and right margins. creates ordered list. creates bulleted list. indents selected text. outdents selected text. Table 4: Form Editor Toolbar Options Figure 25: Text Format Editor Toolbar Stylesheet Select Format Select Font Select Font Size Table 5: Text Format Editor Toolbar Options selects stylesheet to apply to text in editor. select format (heading 1, etc) to apply to selected text. select font to apply to selected text. select Font size to apply to selected text. 20

21 2.3 Creating a New Page To create a new page, select the New command button on the Toolbar. One of the following dialogs appears: Figure 26: New Page Dialog (Page Creation Rules or Page Type) Figure 27: New Page Dialog (Page Creation) Note: This dialog may differ depending on the user s group permissions. If the user has the permission to create pages from page types as well as from rules, the user will see a different dialog. See the Ingeniux Administrator for more details. Enter a Name for your page- The name is used to identify the page in the Assignments list and the Site Map. In this example, the page is called Visiting the Campus. 21

22 Choose a Page Creation Rule- These Rules are the names of the Page Creation Rules (PCRs) that have been configured for the group(s) to which the active user is a member. PCRs determine what page types the user s group is allowed to create, under what node of the Site Map they will be created, and what workflow the page will be bound to. In this example, Admissions Page was chosen from among the three choices. Click OK- The user will see a screen like the following, showing an empty Edit Form awaiting content. Note that the new page was created automatically under the Admissions section which is where the Page Creation Rule specifies that it should go. 2.4 Adding Content: the Edit Form The fields of the edit form depend on what page type is being created and on what types of information have been included by the site designers for that type of page. For example, the first field on the new page created above is a simple text box for the article title. To fill this out, simply type the desired title and move to the next field. Note that this field is denoted as Required in the title of the field. This means that the page cannot be published until a value is filled in. 2.5 Data Types There are a number of different data types that may be found on the edit form. How the user enters a value depends on the data type. The most commonly encountered data types for most content authors are listed below: Plain text: Text entered in a Plain Text accepts no formatting. Text is entered by typing directly into the field, by dragging and dropping, or by cutting and pasting from another document or Web page. Text boxes will expand to accommodate the length of the entry. Formatted text (WYSIWYG): Text entered into the WYSIWYG control accepts formatting (colors, fonts, backgrounds, bold, italic, underline, etc.), as well as hyperlinks, images, tables, etc. Text can be typed directly in this control or dragged and dropped from another source. The WYSIWYG control will be described in detail later. Components: Components are items in the content repository that are used on other pages, such as an image component, a link, or a navigation component. Components can be associated to a page by dragging and dropping the desired item from the Site Map or Search Results page directly into the data field. Components will have an icon next to them that can be clicked in order to edit the attributes of the component. 22

23 2.6 Access Levels Fields on the edit form have designations, as designed by the site designers, which control how a field is viewed and accessed. If a particular field is grayed out on the edit form, the field has been marked read only by the site designers and cannot be edited. Fields may also be designated as hidden, in which case they will not show up at all. 2.7 Required Fields Items on the Edit form may be marked Required which means the page cannot be published until a value is entered. The site administrator sets required status for fields. 2.8 Tracking Changes Show Differences is a feature that visually tracks and displays comparative document changes. With Show Differences, the user can compare two version of a document, Element by Element, and see what changes that have been made. Start Show Differences by using the keyboard shortcut Ctrl. + D. View the differences in an element by positioning the cursor in an element (field on the Edit Form). The highlighted version of the document will appear in the non-editable field at the bottom of the page. Figure 28: Differences Window Pane 23

24 2.7.1 Revision Marks: When the active document is edited changes will automatically be highlighted in the comparison document located in the bottom right pane. The following revision marks indicate the status of a change: When an element is selected the current text will show up in black text. When new text is added to an element, the new text will show up in green. When text is replaced or deleted, it will appear as red text with a strike through it. When Text is moved, the new location will be blue and underlined. The original location of moved text will be blue, underlined, and struck through Changing the Version: To change which version the current document is compared to, select the Compare current to list (located at the top of the comparison pane). Select which version of the document to compare. The three options are: Saved (default) compares the current contents of the Element selected to the version that has been saved. Note: When a page is saved and the selection is Compare Saved, the changes that were made prior to saving will lose the color-coded revision marks and the text will appear in Black. Checked In compares the current contents of the Element selected to the version that has been checked in. Previous compares the current contents of the Element selected to the previous contents, saved or not. Note: If a document has never been checked in, the current page can not be compared to a previous version. In this case, Previous will not appear as a selection in the menu options Revert To : The Revert To button will roll the document back to whatever version is being compared. If reverting to the saved version, all unsaved changes will be lost. If comparing a document to a previous version, it will revert to Previous. Likewise, comparing against Checked In will revert to Checked-In. Close the Show Differences window: Click the Close Window icon on the top right of the bottom pane Use the Ctrl + D keyboard shortcut Check-In the document 24

25 2.8 Finishing Check Spelling Click the Spelling icon on the main toolbar. If there are any misspellings, you will see a dialog like the following: Figure 29: Spell Check Dialog The word highlighted in the Not in Dictionary field is the word not recognized in the main dictionary. The highlighted word in the Suggestions box is what the spelling checker suggests as a replacement. Most common actions are Ignore (let the spelling stand) or Change (replace the word with the highlighted word under Suggestions). For more information, see the section 3.15 on the Spelling Checker Preview Click the Preview tab at the top of the Edit Form. The page will now appear in the Main Content Area as it will appear on the web site: all content is rendered as it will be on the site, and all navigation is as functional as it would be on the published site Assign or Advance The last step in the process is to assign the page to another user or to advance it in workflow. Assigning the page to another user leaves the page in its current workstate but assigns it to another user in the active user s group. Think of it as an informal peer review this option allows for peer review without advancing the page to the next phase of publishing. Advancing the page sends it to the next workstate and to a member of the group associated with that workstate Assign To assign a page, click the Send To icon on the main toolbar. A dialog box similar to the one below will appear: 25

26 Figure 30: Select User Dialog The top window will show all other users in the active user s group. Users currently logged into the system will be shown in blue. Highlight a name and type a comment in the Comments field if desired. This comment will appear on the right side of the status bar on the edit form and in the Notes field on the Assignments list. Note: If the page in question is not in workflow, the users in the Select User dialog will be all users in the system Advance To advance the page in workflow, click the workflow advance button on the Main toolbar. The advance button will carry the caption(s) associated with the allowed transitions from that point- such as Send for Approval or Send Back to Author. If there is more than one transition available from any given state, the button will appear as a dropdown combo button, with the other choices available under the down arrow. Choosing a transition from the dropdown, prompts the user to choose a particular user from the group associated with the workstate the page is being transitioned to. The dialog box is identical to the dialog for Send To. 2.9 Pages in Workflow vs. Pages not in Workflow The exact manner in which the user interacts with content in Ingeniux CMS depends on many factors that are specific to the implementation of the site, such as group permissions and roles, content security settings, etc. Not every permutation of these factors will be covered in the documentation. There are, however, two distinct strategies for working with content, depending on whether the pages you are working on are bound to workflows or not Pages in Workflow When pages are bound to workflow, the primary approach to interacting with content consists of choosing items from the assignment list, adding or editing content, then advancing the page through workflow to other users. Workflow generally implies that different users will be responsible for the page at various points in its lifecycle (e.g., authoring, editing, approval) and that this flow through the editing process benefits the organization. 26

27 Depending on how workflow has been configured, the workflow transitions may perform many of the actions that the user would normally have to do manually (e.g., check in, mark for publish, publish). Because these actions are performed automatically in workflow, the permissions for these functions may be revoked at the group level. In general, when workflow is heavily employed on a site, group permissions are much more restrictive than otherwise. This gives site administrators the ability to lock down content, making it impossible for users to inadvertently compromise the content of the site. So, when pages are in workflow, users do one of the following: Create a new page, add content, and advance it in workflow or assign it to another member of the user s group. Page creation rules (if used) will automatically ensure that the page is created in the correct section of the site, attached to the correct workflow, and assigned to the correct user. Choose an existing item, modify it as required, and advance it in workflow to the next workstate or assign it to another member of your group Pages Not in Workflow When pages are not in workflow, interacting with content is typically less structured with no enforced trajectory through the organization and no enforced division of labor between different users. When workflow is not used extensively, permissions are typically more expansive and users have more freedom as to what they can do with content, but also have more responsibility to perform the correct actions on a page to ensure it is in the proper state. Such actions as check in, check out, mark for publish, and publish are handled manually Finding Existing Content Whether pages are in workflow or not, if the user wishes to modify an existing item in the Author Client, there are several ways to locate the item to edit: Assignments list: From the Assignments list, select the desired item and edit it in the Edit Form. The user s assignments list, in most cases, gives the user the most exhaustive list of what the user should be working on. Site Map: Browse for the item in the Site Map (assuming the user s group has permission to see it), select the page, and edit. Note that the user will not be able to edit the item if it is not assigned to the user. Search: Search for an item using the Search feature. An item can be selected in the search results to open it for editing (again assuming it is assigned to the current user). 27

28 In-Context Editing: Browse for a page to edit in the Preview mode. Then click on the Page Content Tab to edit the page. Again, note that the user will not be able to edit the item if it is not assigned to the user. If looking for existing information or components to use on the current page in the Edit Form, either browse for the item in the Site Map and then drag it to the appropriate field on the Edit Form or use the Search feature to locate the item that you wish to include on the current page, and then drag the item from the search results pane onto the appropriate field in the Edit Form. This is the most typical way to find, for example, an image component if the user does not have permission to access the Site Map. 3. Author Client in Detail 3.1 Edit Form The edit form is the workhorse of the Ingeniux CMS Author client. It is where nearly all page-level data and metadata is entered. The key to understanding the edit form is to know what kind of data can be entered there. 3.2 Data Types There are a number of different data types that may be found on the edit form. How users enter a value depends on the data type. The allowed data types are described in the sections below Plain text Plain text requires text without formatting. Plain text is usually entered by typing directly into the field, dragging and dropping, or cutting and pasting from another document or Web page. Text boxes will expand to accommodate the length of the entry. However, the plain text element is limited to 295 characters. Figure 31: Text Field Formatted text (WYSIWYG) Text entered into the WYSIWYG control accepts formatting (colors, fonts, backgrounds, bold, italic, underline, etc.), as well as hyperlinks, images, tables, etc. Text can be typed directly in this control, dragged and dropped, or copied/cut and pasted from another source. The WYSIWYG control will be described in detail in Section 3.5 below. 28

29 Figure 32: Formatted Text Dates Dates can be filled in on the edit form by selecting a date from the date selector. Select the checkbox and select the date from the Date Picker Control. Figure 33: Date Picker Enumerated Lists Displays as a dropdown list; user selects from the list. The list of items is set by the Administrator and/or Site creator. Figure 34: Enumerated List 29

30 3.2.5 Boolean Values Displays as a checkbox; user checks/unchecks box. The Boolean options and check box options are set by the Site Administrator and/or Site creator. Figure 35: Boolean Field Component Element Component elements create a relationship between two nodes in the Document Tree. This element is just a 'slot' into which another page or component can be dragged in. Whatever is dragged into this Component element will be pulled in its entirety- meaning that all the XML in the dragged item will be brought into the page or component into which it was dragged. This is different than, say, a Link element which only pulls in a portion of the page or component that was dragged into it (attributes such as Name, ID, URL, and Schema type). Component elements will have an icon next to them that can be selected in order to edit the attributes of the element. Figure 36: Empty Component Element Figure 37: Component Element 30

31 Narrowing Down the List Figure 38: Selecting Component Page A component element can be populated by dragging a component from the site tree or by selecting the Pick button on the Component Element. The pick option provides three options for selecting a component: Search by Component Type: This dropdown provides a listing of components by type. Selecting a particular type such as Binary Document in the Show Only these components types dropdown narrows down the list of components available for selection. To select a component, highlight a specific component in the listing and then choose the Select button. Search by Name: This option narrows down the list of components by name. As text is entered into the Show only components with name containing field, the list of components begins to narrow corresponding with the text as entered. Again, to select a particular component, highlight a specific component in the listing and then choose the Select button. 31

32 Figure 39: Selecting Component Page (cont.) Queries: By selecting the Advanced button, a query can be entered that will choose the appropriate component via query that runs at the time the page is rendered. To enter a query, select the Advanced button, enter a query string for the Component to be selected when content is rendered, select OK, and then select the Select button. Figure 40: Dynamic Component Picker Figure 41: Dynamic Component Picker (cont) Please note that the Query function is an advanced option and should not be used unless a value has been specified by the System Administrator and/or Site creator. 32

33 3.2.7 Image file Elements When an Image file element is used, it displays as a blank text box with a button beside the text box that opens the Images folder on the server. The user picks an image from the Image Browser which then populates the field with the name of the image. Figure 42: Image File Element Figure 43: Image File Browse Dialog Image file Element Attributes File Name: indicates the actual image file selected. This option is grayed out if the URL radio button has been selected. URL: pulls image file from a different URL outside of the xml\documents directory. Preview: provides the option to preview the image selected via the URL option. Alternate Text: allows for the entry of text to appear when mousing over the image on a rendered page. 33

34 Alignment: dropdown defining the position of the image file on the rendered page. Figure 44: Alignment Dropdown Border: provides the option to place a border of the entered size (in pixels) around the image on the rendered page. Horizontal: sets the horizontal spacing (in pixels) around the image determining how close text wraps around the image on the rendered page. Vertical: sets the horizontal spacing (in pixels) around the image determining how close text wraps around the image on the rendered page. Height: sets the native height (in pixels). Please note that the proportions are not kept when modifying this value. In other words, this value is not tied to the Width value and which will need to be modified by a proportional amount to maintain the correct proportions of the picture. Width: sets the native Width (in pixels). Please note that the proportions are not kept when modifying this value. In other words, this value is not tied to the Height value and which will need to be modified by a proportional amount to maintain the correct proportions of the picture Media File Elements When a Media file element is used on the edit form, Media file element displays as a blank text box with a button beside it that opens the Media folder on the server. The user picks a media file from this folder which then populates the field with the name of the file and displays it on the edit form. Figure 45: Media Element 34

35 Figure 46: Media File Browse Figure 47: Media Type Dropdown Document Elements When a Document element is used on the edit form, the Document Element displays as a blank text box with a button beside it that opens the Documents folder on the server. The user picks a document from this folder which then populates the field with the name of the file and displays it on the edit form. Figure 48: Document Element 35

36 Figure 49: Documents Browse Link Element Link elements are used to create a relationship between two nodes in the Document Tree. This element is just a 'slot' into which another page or component can be dragged in. Whatever is dragged into this Link element will bring with it only a portion of its contents: its Name, ID, URL, and Schema type. Additional elements from the dragged in page must be specifically 'exported' by being added to the Exported Elements list (Admin System Options Navigations Exported Elements) or added exported in the properties of the link itself. Link elements are meant to link internally to other nodes in the Document Tree, not to external web sites. Link elements will have an icon next to them that can be selected in order to edit the attributes of the element. Figure 50: Link Element 36

37 Figure 51: Link Element Properties Link: specifies the xid (without the.xml extension) of the page to which to link. Exports: allows for the entry of an associated attribute to be pulled along with the image into the current page. (also known as local export) Insert Element Insert elements pull in content from either an outside source, such as a web page, or from an internal HTML document, such as an HTML or ASP page. If from an outside source, the content can be either well-formed XML or poorlyformed HTML. If well-formed XML, the attribute 'WellFormed' should be set to 'true'. If from an internal source, the source document must reside in the PreBuilt directory on the server, as this is where the Insert element will expect it. Figure 52: Insert Element 37

38 Figure 53: Insert Element Browse Figure 54: Insert Element Properties Properties: Insert: specifies the URL of the content to be inserted. If the content resides in the PreBuilt directory, simply specify the file name as the client will automatically look for the file in the \xml\prebuilt directory. Wellformed: (True/False) specifies whether the content to be inserted conforms to XML standards. If the document does not conform to XML standards, selecting true will generate an error. ExtractHTMLBody: allows the client to pull only the content contained in a <body> tag. Note, a value of true will generate an error if the document does not contain a <body> tag. 38

39 Navigation Element Navigation elements are the workhorse of the Ingeniux CMS implementation. Anytime content needs to pull content from one part of the site to use in another, chances are that a Navigation element is the tool to use. The obvious uses of a Navigation element are for navigations header navigations across the top of the site, left-hand navigations down the side of the site, etc. Other less obvious uses, however, include "Top 5 Press Releases" on the home page, "breadcrumb" navigation across a story page, and event child pages on Section front templates. Each of these scenarios utilizes one of the five different Navigation element navigation types: Ancestor, Children, Sibling, Sequential and Subtree. Depending on the demands of the site, Navigation elements can also be enhanced to provide additional information using the Exports feature, and through global System Options. Each Navigation element's output results in a similar XML fragment, regardless of navigation type. Figure 55: Navigation Element Figure 56: Navigation Element (Expanded) Figure 57: Navigation Type Dropdown Figure 58: Navigation Order Dropdown 39

40 Type: specifies the type of navigation. Ancestors- pull in pages residing one or more node levels above the current page. ** Children- pull in pages residing one or more node levels below the current page. ** Sibling- pulls in pages residing on the same node level as the current page. The number of pages pulled in depends upon the Max Nodes setting. Sequential- (non-standard) pulls in sibling navigation preceding and following the current page. Subtree- (non-standard) pulls in pages residing one or more node levels below the current page but excludes all pages in not marked for publish. (This navigation performs the same as a Child Navigation in Preview with the Show All Pages option unchecked.) ** The number of nodes and number of node levels are determined by the Max Nodes and the Max Depth properties. Site tree: Generated XML for the Westlake Center page with the Ancestor Navigation with NO StartPage set: <Page ID="x1" URL="x1.xml?Preview=true&Site=&UserAgent=&In cludeallpages=true&tfrm=4" Schema="Folder" Name="Seattle Sample Site for Training" /> <Page ID="x224" URL="x224.xml?Preview=true&Site=&UserAgent=& IncludeAllPages=true&tfrm=4" Schema="Folder" Name="Seattle City Site" /> <Page ID="x237" URL="x237.xml?Preview=true&Site=&UserAgent=& IncludeAllPages=true&tfrm=4" Schema="Folder" Name="Pages" /> <Page ID="x239" URL="x239.xml?Preview=true&Site=&UserAgent=& IncludeAllPages=true&tfrm=4" Title="Welcome To Seattle! It's not sunny here very often... if I make changes they show here..." Schema="Section" Name="Home Page" /> <Page ID="x244" URL="x244.xml?Preview=true&Site=&UserAgent=& IncludeAllPages=true&tfrm=4" Title="Welcome to Westlake Center" Schema="Story" Name="Westlake Center" /> Figure 59: Ancestor Navigation 40

41 Site tree : Generated Child Navigation XML: <Page ID="x244" URL="x244.xml?Preview=true&Site=&Us eragent=&includeallpages=true&tfrm= 4" Title="Welcome to Westlake Center" Schema="Story" Name="Westlake Center" /> <Page ID="x245" URL="x245.xml?Preview=true&Site=&Us eragent=&includeallpages=true&tfrm= 4" Title="Welcome To Pike Place Market" Schema="Story" Name="Pike Place Market" /> <Page ID="x243" URL="x243.xml?Preview=true&Site=&Us eragent=&includeallpages=true&tfrm= 4" Title="Welcome To Washington State Ferries" Schema="Story" Name="Washington State Ferries" /> Figure 60: Child Navigation Site tree: Generated XML for the Westlake Center page with the Sibling Navigation: Figure 61: Sibling Navigation <Page ID="x244" URL="x244.xml?Preview=true&Site=&UserAgent=&I ncludeallpages=true&tfrm=4" Title="Welcome to Westlake Center" Schema="Story" Name="Westlake Center" /> <Page ID="x245" URL="x245.xml?Preview=true&Site=&UserAgent=&I ncludeallpages=true&tfrm=4" Title="Welcome To Pike Place Market" Schema="Story" Name="Pike Place Market" /> <Page ID="x243" URL="x243.xml?Preview=true&Site=&UserAgent=&I ncludeallpages=true&tfrm=4" Title="Welcome To Washington State Ferries" Schema="Story" Name="Washington State Ferries" /> 41

42 Site tree: User s Guide to the Author Client Generated XML for the Home Page with the Subtree Navigation: <Page ID="x244" URL="x244.xml?Preview=true&Site=&UserAgent= &IncludeAllPages=true&tfrm=4" Title="Welcome to Westlake Center" Schema="Story" Name="Westlake Center" /> <Page ID="x245" URL="x245.xml?Preview=true&Site=&UserAgent= &IncludeAllPages=true&tfrm=4" Title="Welcome To Pike Place Market" Schema="Story" Name="Pike Place Market" /> <Page ID="x243" URL="x243.xml?Preview=true&Site=&UserAgent= &IncludeAllPages=true&tfrm=4" Title="Welcome To Washington State Ferries" Schema="Story" Name="Washington State Ferries" /> Figure 62: Subtree Navigation Site tree: Generated XML for the Home Page with the Sequential Navigation: <Page Name="Prev" Schema="Story" URL="x244.xml?Preview=true&Site=&UserAgent=&I ncludeallpages=true&tfrm=4" Title="Welcome to Westlake Center" ID="x244" /> <Page ID="x243" Name="Next" URL="x243.xml?Preview=true&Site=&UserAgent=&I ncludeallpages=true&tfrm=4" Title="Welcome To Washington State Ferries" Schema="Story" /> Figure 63: Sequential Navigation 42

43 Navigation Order: specifies the direction in which navigations are built. Up- starts with the last page found via navigations and then adds each additional page to the resulting XML moving up towards the first page found in the navigation. Down- starts with the first page found via navigation and then adds each additional page to the resulting XML moving down towards the last page found in the navigation. Start Page: limits the extent of a navigation to a particular page xid. For example, an ancestor navigation with a start page of x12 will include all pages up to and including x12. Max Nodes: specifies the total number of pages pulled into a particular navigation. Max Depth: specifies the number of node levels pulled into a particular navigation. Query: provides an option to filter the results of a navigation via an xpath query. Exports: allows for the entry of an associated attribute to be pulled along with the navigations pages pulled into the current page. Priority among Navigational Properties: A particular navigation will stop at the first limiting property that the navigation encounters. For example, a Max Node of 5 will limit the navigation to only 5 pages regardless of the Max Depth or Start Page properties settings dbquery Com Execute Element The dbquery Com Execute element allows the page to execute a query to a database with a specified DSN. It is an example of a built-in Server Extension component included within Ingeniux CMS. When the dbquery component executes the specified query, a dbquery element is created with a subelement for each record in the returned result set. The field values are contained within CDATA sections to protect special characters. If a field has a NULL value, then the string value NULL will be returned. Figure 64: DBQuery Com Execute Element 43

44 Figure 65: DBQuery Element Properties ProgID: identifies the COM interface ID used by the COMEXECUTE. Do Not Modify. Method: identifies the method invoked by the Class specified by the ProgID. Do Not Modify. DSN: supports a Data Source Name configured to connect to a database. This attribute will also support connection strings. Label: provides the means to assign a friendly label to identify the query. ID: provides the means to assign an ID number to identify the query. Add Attribute: provides the option to define additional attributes and their values for the specific query. Figure 66: Add Attribute Dialog Add Elements Option: provides the option to define additional elements and their values for the specific query. 44

45 Figure 67: Add Element Dialog Read-Only and Hidden Fields Fields on the edit form may be read-only- meaning that they cannot be edited. These fields will show up as grayed out on the edit form. Hidden fields will not show up at all. The site administrator or site designer sets these attributes at the schema level. Figure 68: Read-Only Field Required Fields Items on the edit form may be marked Required- which means the page cannot be published until a value is entered. The site administrator or site designer sets this attribute at the schema level. Figure 69: Required Field Layout Field The layout field defines what stylesheet should be applied to the page. This field is pulled from the page schema for the particular page defined by the Site Designer. Typically, this field is not editable from the Author client and should not be modified unless the stylesheet for this particular page needs to be changed. Figure 70: Layout Element 45

46 3.5 DHTML Control The DHTML control allows users to produce formatted text that is saved as hypertext markup language (HTML) that can be read by browsers. Because the DHTML control does the work of translating formatting into HTML behind the scenes, the user does not have to know HTML to use this tool. Simply choose the fonts, sizes, colors, styles, etc., from the toolbar, and the DHTML control handles the rest. A user can type text into the DHTML control, drag and drop, or cut and paste information from other documents or Web pages. Once the text is in the control, it can be formatted. The Editor provides three modes: 1. Edit tab (see image below): provides a form for users to enter text and a whole host of additional objects and formatting via easy to use formatting buttons. Formatting buttons will be described in detail in the section below. Please see section for a brief legend of Editor Buttons. Figure 71: DHTML Editor Edit Tab 2. HTML tab (see image below): displays the HTML markup associated with the text, formatting, and objects on the Edit page. This markup can be edited directly within this tab. Please note that the changes made on this tab are saved immediately. 46

47 Figure 72: DHTML Editor HTML Tab 3. Preview Tab (see image below): displays text, formatting, and objects as rendered HTML. Figure 73: DHTML Editor Preview Tab Note formatting may be displayed differently by the various DHTML editor screens. The preview tab displays how the HTML will be displayed to browsers. All worked should be previewed before publishing to confirm the content appears as intended. One additional note, a site wide stylesheet may provide additional formatting to this content. Please check with the Site Administrator regarding the use of site wide styling. 47

48 3.5.1 Format Editor Toolbar Figure 74: Format Editor Toolbar 1. Search and Replace- provides the ability to locate and/or replace a text string within the edit pane of the Editor. To search, follow these steps: a. Enter text string to locate in the Search Box. b. Select the Search button. To replace a text string, follow these steps: a. Enter text string to be replaced in the Search Box. b. Enter new text string in the Replace Box. c. Select the Replace button. To delete a text string, follow these steps: a. Enter text string to be replaced in the Search Box. b. Leave the Replace Box empty. c. Select the Replace button. Figure 75: Search/Replace Dialog 2. Cut- provides the ability to cut text. To cut a piece of text (or object) inside the Editor, highlight the text (or object) and select the Cut button. Cutting a piece of text removes the text from the editor to be pasted into a different location in the editor. 3. Copy- provides the ability to copy text. To copy a piece of text (or object) inside the Editor, highlight the text (or object) and select the Copy button. Copying a piece of text does not remove the text from the editor to be pasted into a different location in the editor. 4. Paste- provides the ability to paste text that was previously cut or copied. To paste the text, select an area of the editor and then select the Paste button. 5. Paste Word- pastes text copied or cut from Microsoft Word and removes the Microsoft Word specific formatting. To paste from Microsoft Word, cut or copy a piece of text from a Word document, switch to the Ingeniux client, and then select the Paste Word button. 6. Paste Text- pastes text copied or cut from another source other than the DHTML editor. To paste from another application, cut or copy a piece of text from another application, switch to the Ingeniux client, and then select the Paste Text button. 7. Undo- undoes last action performed in editor. 8. Redo- repeats last action performed in editor. 48

49 9. Remove Formatting- removes the formatting for the selected text based on the option selected. To remove the current Format type, highlight text and select the Remove Format button. To remove a different Format type than the one currently selected, highlight text, select the down arrow, and the select the Format type. There are five options: - Remove Style/Class - Remove Formatting - Remove Empty Tags - Remove Word Formatting - Remove Span Tags Form Editor Toolbar Figure 76: Form Edit Toolbar 1. Link- allows for the creation of links with DHTML content. To create a link, highlight text within the editor and select the Link button. Figure 77: Link Properties Link Properties: Text: defines the text used for the link. 49

50 Type: defines the type of link. File: links to a file. Note that users system must support the file type. Ftp: links to a FTP site. Http: links to a HTTP site. Https: links to a secure HTTP site. Mailto: links to the user s default program to send . News: links to a News server. Telnet: links to a Telnet server. Wais: links to a Wais server. Anchor: provides a dropdown of previously created anchor tags with in the existing content inside the DHTML editor. Anchors can be used to provide links to other section of text within the same content. URL: lists the action address associated with the linked word. The Ellipses button launches a minimal browser window to confirm a particular address. To load a particular address, enter the address into the Address option and select Go. To save the Address, select the Save Address button. Figure 78: Link Browser Window 50

51 Target: defines how the link should load when launched. Figure 79: Target Dropdown _blank- launches link into a new blank browser window. _new- launches link into a new blank browser window. This attribute has been depreciated for most current browsers. _parent- launches link into the Frameset parent, used primarily with frames. _search- launches link into a Search Window if supported by browser. _self- launches link in the current window browser. _top- launches link in the top most window browser, used primarily with frames. The remove link removes the link and all its properties from the highlighted text. Image Class Tab: Class: applies a CSS class to the link. The dropdown is populated by the system administrator or the site designer. Figure 80: Link Class Properties 2. Anchor tag- provides the option to create an anchor tag. Anchor tags can be used to provide links to section of the content within the same body of content. 51

52 Figure 81: Anchor Properties Dialog 3. Image- provides the option to pull in an image from the \xml\images directory. Figure 82: Image Attributes Dialog Attributes Tab: Width: sets the native Width (in pixels). Please note that the proportions are not kept when modifying this value. In other words, this value is not tied to the Height value and which will need to be modified by a proportional amount to maintain the correct proportions of the picture. Height: sets the native height (in pixels). Please note that the proportions are not kept when modifying this value. In other words, this value is not tied to the Width value and which will need to be modified by a proportional amount to maintain the correct proportions of the picture. Border: provides the option to place a border of the entered size (in pixels) around the image on the rendered page. Horizontal: sets the horizontal spacing (in pixels) around the image determining how close text wraps around the image on the rendered page. Vertical: sets the horizontal spacing (in pixels) around the image determining how close text wraps around the image on the rendered page Alignment: dropdown defining the position of the image file on the rendered page. 52

53 Figure 83: Alignment Dropdown Left- aligns image to the left margin. Right- aligns image to the right margin. Top- aligns image with the tallest character in the current line. Bottom- aligns image to bottom of the current line. Middle- aligns the middle of the image with bottom of the current line. Center- aligns the middle of the image with the middle of the current line. Adsbottom- aligns image to the character farthest below the current line. Absmiddle- aligns the middle of the image with the middle of the current line. Texttop- aligns image to the tallest item in the current line. Source: allows user to select image file the xml\images directory. Alternate Text: allows for the entry of text to appear when mousing over the image on a rendered page. Preview: provides the option to preview the image selected via the URL option. Image Class Tab: Class: applies a CSS class to the image. The dropdown is populated by the system administrator or the site designer. 53

54 Figure 84: Image Class Dialog 4. Table- creates an html table containing the number of rows and columns selected. To create a table, follow these steps: a. Select the Table button- which expands as visible in the first graphic below. b. Using the mouse cursor, highlight the number of squares corresponding to the number of columns and rows for the table. c. Once the correct number of squares have been selected, simply click to create the table inside the editor. Figure 85: Creating a Table 5. Line- inserts a line inside the editor. 6. DIV- inserts div tag. 7. IFRAME- inserts the current client system time. Note, requires modifying the IFRAME tag to add a src= attribute in the HTML view. 8. Paragraph- inserts a <P> tag to create a separate paragraph. 9. Bold- bolds highlighted text. To bold, highlight the text to format and then select the Bold button. Example: Bold. 10. Italic- italicizes highlighted text. To italicize, highlight the text to format and then select the Italic button. Example: Italic 54

55 11. Underline- underlines highlighted text. To underline, highlight the text to format and then select the Underline button. Example: Underline 12. Font Color- provides the option to select a font color. To change the font color to the currently selected color, highlight the text to format and then select the Color button. To change the font color to a new color, highlight the text to format, select the down arrow, and select a color. See the More Color description on the following page. Figure 86: Font Color 13. Font Background Color- provides the option to select a font background color. To change the font background color to the currently selected color, highlight the text to format and then select the Background color button. To change the font color to a new color, highlight the text to format, select the down arrow, and select a color. The More Colors button allows for additional colors to be selected. Figure 87: Font Background Color More Colors Options: The More Colors button allows for additional colors to be selected. Either select a color by click inside the color palette or by entering a web based color number inside the color option and then click OK to apply the color to the selected text. 55

56 Figure 88: More Colors Dialog 14. Left Justify- justifies selected text to the left margin 15. Center Justify- justifies selected text to the center between left and right margins. 16. Right Justify- justifies selected text to the right margin. 17. Full Justify- justifies selected text to both the left and right margins. Note about Text justifications: The Edit tab will not show text justifications. For example, the figure below displays shows the highlighted text Center Justified as left justified. However, this text is center justified as indicated by the highlighted center justification button in the top right corner. Figure 89: Edit View of Font Justification 56

57 Selecting the HTML tab displays the underlying HTML formatting. Please note that the text Center Justify is within a <P> tag with the align attribute sent to center. Figure 90: HTML View of Font Justification Finally, selecting the Preview tab displays the render HTML. Please note that the text Center Justify is in fact justified to the center. Figure 91: Preview of Font Justification 18. Ordered List- creates an ordered list. To create an ordered list, select the Ordered list button and enter text. The next sequential number is created after each carriage return. The ordered list is escaped by two consecutive carriage returns, i.e. hitting the enter key twice. Example: 1. Item1 2. Item2 3. Item3 19. Bulleted List- creates an unordered list. To create an unordered list, select the Bulleted list button and enter text. A new bullet point is created after each carriage return. The ordered list is escaped by two consecutive carriage returns, i.e. hitting the enter key twice. Example: HTML 57

58 XML XSLT 20. Indent- indents to the left the current line one tab for each time the Indent button is selected. 21. Outdent- outdents to the right the current line one tab for each time the Outdent button is selected Text Formatting Figure 92: Text Formatting Toolbar 1. Stylesheet- provides a dropdown listing of CSS stylesheets to format the contents of the editor. To select a particular style, highlight the text to format, select the down arrow, and then select the style to apply. The options within the dropdown list are configured by the system administrator. 2. HTML Format- provides a listing of standard HTML formats to apply to text within the DHTML editor. To select a particular format, highlight the text to format, select the down arrow, and then select the format to apply. Figure 93: HTML Formats 3. Font type- provides a listing of standard fonts. To select a particular font, highlight the text to format, select the down arrow, and then select the font to apply. Note that the selected font must be available on the client s system to be available within the dropdown. 58

59 Figure 94: Font Type Dropdown 4. Font Size- provides a listing of standard font sizes. To select a particular font size, highlight the text to format, select the down arrow, and then select the font size to apply. Figure 95: Font Size Dropdown DHTML Context Menu Right-clicking within the DHTML Edit window provides one or more the following options depending upon what item is selected prior to the rightclick: Inset Image- performs the same action as the Insert Image button. Insert Link- performs the same action as the Insert Image button. Cut- performs a standard cut of the selected content. Copy- performs a standard copy of the selected content. Paste- performs a standard paste of previously cut or copied content. Set to Foreground- adds the Z-index style attribute to the select content to force this content forward. Set to Background- removes the Z-index style attribute from the select content to force this content into the background. 59

60 3.6 Dragging and Dropping from other Applications Text can be dragged/dropped or copied/paste from Microsoft Office applications and many other applications as well. Native formatting is preserved in most cases. The degree to which formatting is preserved is dependent on how well the source application s formatting is preserved on the Windows clipboard since the clipboard is the intermediary between the source application and the Ingeniux CMS WYSIWYG control. For example, to copy an Excel spreadsheet into the WYSIWYG control, select the cells to copy, copy to the clipboard, and then paste into the desired location in the WYSIWYG control. In the example below, the selected cells are in blue: Figure 96: Spreadsheet Example The data is then pasted into the control. Note that all formatting has been preserved. This is because the HTML formatting instructions for each cell lie nested within the formatting for the entire WYSIWYG control, and thus override the top-level formatting instructions: 60

61 Figure 97: Pasted Data Often times it is desirable not to have formatting preserved in drag-and-drop operations, so that the styles defined in extensible stylesheet language transformations (XSLT) and Cascading Stylesheets (CSS) can be applied to enforce consistency of presentation. In such cases, it is recommended to first paste the data into a text-only editor such as Notepad and paste the data to the DHTML editor. This will strip all formatting from the copied information. 3.7 Working with Images and other Assets Adding an image or other asset to a page is a two-part process: First, the asset must be uploaded from the user s local machine to the server that runs Ingeniux CMS. Once it is there, it can be used repeatedly on other pages Uploading Images and other Assets To add an image from the hard disk or other network location, select the Upload icon from the main Toolbar. A File dialog prompts the user to choose the image(s) to import. 61

62 Figure 98: Image Selection Dialog Choose the file types to browse for in the Files of type dropdown. In this example, the user has chosen Image files. Select the image(s) and be sure the image name(s) appears in the File name box. Choose the location on the server to upload the image to in the Upload to dropdown. The user will be able to choose from Images, Documents, Prebuilt, Stylesheets, Schemas, or any subdirectories of these directories. To create a component out of the uploaded image, check the Create component checkbox. It is highly recommended that components are created out of the assets uploaded for several reasons. If the asset is made into a component, the users will have the opportunity to add metadata that describes the image (description, keywords, etc.). This will enable search for images using the search function. It also means that the image will appear in the content tree as an item that can be dragged and dropped onto the edit form or otherwise reused. It is important to note that there must be a valid page creation rule in order to create a component. These rules will need to be configured by the system administrator. Next, click Import. If the Create component box was checked, the following dialog appears. This gives the user an opportunity to add metadata about the image that assists later when searching for and organizing this information. 62

63 Figure 99: Image Attributes Dialog Under Additional description, description of the image can be entered. This is the text that will appear as the alternate text during a mouse rollover of the image. Under Keywords, the user may enter multiple keywords, separated by commas. These keywords will be stored in the metadata of the component. Under New image name, the user may change the name of the image being uploaded. By default, the name of the component will be the same as the name of the image. Select OK to upload the image and create the component. The user can find this component in the Site Map (though the user may need to refresh the map first by selecting the Refresh icon). It will also appear as assigned to the user in the Assignment list. After the few moments it takes to index the component, the image can be located by searching on any of the metadata associated with the component Inserting Image Components onto Pages Now that the image component is created, the user can access it in several ways to use it on a page: via the Site Map, the Assignment list, or the Search window (using the search function will be described in more detail below). Once an image component has been located by any of these means, it may be dragged and dropped into an image component field (if one exists) on the edit form. Simply select it in the left column, and drag it into the page. Dragging is accomplished by clicking and holding down the left mouse button on the Image and dragging it to the Image field of the page. Once the cursor is within the Image field, release the left mouse button. The user can also edit the attributes associated with this component. Clicking on the component will open it in the edit form where the user will be allowed to edit the metadata associated with the image Inserting Images into the WYSIWYG control Images may also be inserted directly into the WYSIWYG control whether or not they exist as components. Simply place the cursor in the WYSIWYG control where the image needs to appear. From the right click context menu, choose Picture A dialog similar to Figure 32 on the next page will appear. This is the same dialog used for the properties button ( ) next to the image name on the edit form. 63

64 Figure 100: Picture Dialog Browse for an image file on the server and highlight the image in the file list. Make sure the name of the file appears under File name. To reference an external image somewhere on the Internet, click the URL radio button and enter the complete URL to the image. Click Preview to see the image in the blue preview area. File Name: indicates the actual image file selected. This option is grayed out if the URL radio button has been selected. URL: pulls image file from a different URL outside the xml\documents directory. Preview: provides the option to preview the image selected via the URL option. Alternate Text: allows for the entry of text to appear when mousing over the image on a rendered page. Alignment: dropdown defining the position of the image file on the rendered page. Border: provides the option to place a border of the entered size (in pixels) around the image on the rendered page. Horizontal: sets the horizontal spacing (in pixels) around the image determining how close text wraps around the image on the rendered page. Vertical: sets the horizontal spacing (in pixels) around the image determining how close text wraps around the image on the rendered page. Height: sets the native height (in pixels). Please note that the proportions are not kept when modifying this value. In other words, this value is not tied to the Width value and which will need to be modified by a proportional amount to maintain the correct proportions of the picture. Width: sets the native Width (in pixels). Please note that the proportions are not kept when modifying this value. In other words, this value is not tied to the Height value and which will need to be modified by a proportional amount to maintain the correct proportions of the picture. 64

65 3.8 Assignment List The usual way to work with content using the Author client is through the Assignment list. The Assignment list shows every item that has been assigned to the user along with any items created by the user. Pages are listed in chronological order with the most recently assigned at the top of the list. Any comments entered by the user who assigned the page to you are in the second column of the Assignment list. Figure 101: Assignment List To work with an item in the list, simply click on the title of the page in the list and it will populate the edit form, ready to edit. When assigning the page to someone else or advance it to another state, the item will disappear from the list. 3.9 Site Map Content in Ingeniux CMS resides on a central server in the Content Repository (or Content Store), primarily in a single directory. Though the content resides in a single directory, logical hierarchical relationships between items in the repository can be established via the Site Map (also referred to as the Content Tree) in a manner very similar to browsing the file structure on a hard drive. Any particular item in the content repository is known as a node. Items that are one level above other node in the hierarchy are said to exhibit a parentchild relationship- with the superior node called the parent node and the subordinate node called the child. Nodes at the same level are said to exhibit a sibling relationship. Any nodes hierarchically above a given node are known as ancestors and any nodes below are referred to as descendents. The structure of the content in the site map is usually strongly reflected in the structure and navigation of the Web site. For example, in the Site Map in the next section, the page named Admissions has six child pages and on the Web site, that page has six links listing the articles that appear in that section. This is called Child Navigation and is one of the standard navigational types in Ingeniux CMS. A great deal about the state of various content items can be gleaned by looking at the Site Map. Bold: Items in Bold are marked for publish (i.e., approved for publishing). In the example above, the page named Visiting the Campus is not marked for publish, while Financial Aid is. 65

66 Figure 102: Site Tree Icons: If an icon is grayed out, like the About Faber icon, it is checked in. If it is in color, like the Research icon, it is checked out. Icons also indicate something about the type of item it is. If the folder icon depicts an open folder, like the node Faber Public Site, indicates the node of the tree has been expanded Moving and Copying Pages in the Tree It is easy to move or copy pages within the tree. To move a page, simply hold the left mouse button over the page and drag it to the place to move the page. To copy the page, hold down the control key while dragging the page. There are two different modes for dragging a page in the tree: insert mode and child mode. Insert mode places the page between two others; child mode makes the page a child of the page it is dropped on. The shape of the cursor indicates the mode. If the cursor is a line, the page will be inserted exactly at the location of the line. In the figure below, the page being dragged will be inserted after Directions to Campus and will be another child of Admissions. Figure 103: Copy/Move Image (Part 1) 66

67 If the page being moved had been dragged a little further, the left end of the cursor would outdent a bit more, showing that the page would be moved to the location after Directions to Campus and before About Faber, but would now be a peer of Admissions rather than a child. This is shown below. Figure 104: Copy/Move Image (Part 2) If the insertion mark highlights a page, the dropped page will be a child of the page that it was dropped on. In the figure below, with a cursor that makes a blue background behind the page Directions to Campus, the moved page will be created as a child of that page. Figure 105: Copy/Move Image (Part 3) Tip: Right clicking on a page and dragging it to a new location will open a menu that prompts the user to copy or to move the page to the current location. When attempting to move a page to a new location, the user will see the following dialog: Figure 106: Move or Copy Dialog 67

68 Choose Yes to continue the move operation, No to cancel. It is strongly recommended not disabling this dialog by checking the Don t show this to me again option Cross Site Copy - Copying Files from Other Sites Cross Site Copy allows the user to copy pages from other Ingeniux CMS sites. In order to use Cross-Site Copy the system needs to be properly configured by the Administrator. There are three ways that cross-site copy can be performed: With two instances of Ingeniux CMS running on the same computer, click and drag a page from one sites content store to the other sites content tree. With two instances of Ingeniux CMS running on the same computer, copy one page onto the clipboard and paste into the other content tree. Using Cross-Site Search (see Search section) locates a page residing in another content store. Click on the page in the search results list to open it in the lower right-hand pane. Drag the page s icon onto the content tree. Cross Site Copy always copies the Checked Out version of a page, regardless if changes have been saved or not. Any images, files and embedded in the page will go over with the copy. However, other dependencies will not follow the page. Copy does not prompt the user to save changes before performing a copy. If the user selects a folder or page that has children to be copied only the selected page is copied and child pages do not get copied. The copy action does not require that the destination site contain a schema for the page copied. However, because the copied page was created without a local schema it is marked with distinctive Turquoise icon. This provides users with an easy way to visually detect copied pages that have no local schema. If the pages local schema already exists in the destination site the page gets the icon specified in the schema. The copied page does not retain its original name, e.g., X540.XML. The page will automatically be assigned the next available pageid in the destination site. 68

69 3.11 The Context Menu Right-clicking on an item in the tree opens the context menu. The items that appear in the menu depend on user group s permissions. For instance, if the user doesn t have the permission to create a new page, the New menu item will not appear. Which menu items are active depends on the state of the page. For example, if a page is Marked for Publish, Unmark for Publish will be available and Mark for Publish will be grayed-out. The context menu shown displays all available functions. The functionality of the context menu in the Author client is identical to the functionality of the context menu in the Admin client which is in some cases slightly different than the equivalent functionality provided by the toolbar in the Author client. The various functions and any differences between the two clients are described below. New - Selecting the New options launches the New dialog box, allowing the user to create new pages, components, or folders. The example below shows a context menu for a user that has no permissions except for the ability to create or edit a page. Figure 107: New Page via Page Creation Rule If the user has the right to create pages from page types as well as page creation rules, the Create New Page dialog will look like the following: Figure 108: New Page via Page Types If the user chooses the Use Page Creation Rules radio button, the dialog behaves as described in the section on Working with Content. If the user chooses the Use Page Type button, the Page Types section of the dialog becomes active. A list of all available schema types appears in the Type 69

70 dropdown and all stylesheets appear in the Layout dropdown. The default layout is suggested automatically. Normally, this should not be changed. Rename - launches the Rename dialog. A page can also be renamed by left-clicking on the page that already has focus in the Site Map. Refresh - refreshes the Site Map and the edit form. This has the same function as the Refresh button. Cut - cuts the current selection from the tree and puts it on the clipboard. The icon of the page will change indicating that it is now cut from the Site Map but it will not disappear until the page is pasted to a new location or the tree is refreshed. Copy - copies the currently selected page to the clipboard. Paste - pastes the contents of the clipboard and creates a child page of the currently selected page. Delete - deletes the currently selected page and sends it to the Recycle Bin. Assign To - launches the Assign To dialog. This is identical to the Toolbar command called Assign. Advance - launches the Advance Page in Workflow dialog. This combines the functions of selecting a transition and selecting a user into one dialog. Figure 109: Workflow Dialog Under Allowed Transitions, choose a transition from the dropdown. Then pick a user from the Users dropdown. Enter any Comments if desired and then click Advance. 70

71 Show History - launches workflow History dialog. Send Mail - launches Send Mail Dialog. Check In/Check Out - checks in the current page if it is checked out. Checks out the current page if it is checked in. If the current page has children, the user will be given the option to check in/out the current page, or the current page and its children. Undo Checkout - reverses the checkout operation. Rollback - rolls back changes to the previously checked in version of the page. Mark/Unmark for Publish- marks the current page for publishing if it is currently unmarked. Unmarks the current page if page is marked. If the current page has children, the user will be given the option to mark/unmark the current page or current the page and its children. Preview - launches the Preview Window. Publish - launches the Publish dialog. Properties - launches the Page Properties dialog Search Ingeniux CMS provides robust full-text searching ability based on Microsoft Index Server technology. Searches are fast and accurate Constructing a Query To use search, click on the Search tab. The user has the choice to enter a simple text string or to hit the Search Options link for advanced functionality. With Search Options, the user will see a dialog like the following at the top of the Search page. Figure 110: Search Dialog Enter Keywords To Search For: Enter the term(s) on which to search. A logical OR is assumed between multiple terms. The search term environmental research would return all articles that contain the word environmental and all articles that contain the term research. Use quotation marks to specify an exact match; for example, environmental research returns articles that specifically mention environmental research, but will not return pages that merely contain the term research. The scope of the search includes the entire xml file; that is, all data entered by the user, all captions on the edit form, all xml tags, etc. Look In: This determines which sites are searched. By default, This Site is checked in the list. The user has the choice to search This Site (the 71

72 local site) or any number of external sites that have been configured by Administrator. Sort by: This determines the sort order of the results. The choices are Date (newest item first), Date (oldest item first), Rank (most relevant first), and Rank (least relevant first). Search for: Determines the type of files to search. The choices depend on how the system is configured. Now click Search. The search results set appear in the lower half of the search pane. In the upper left of the Search pane, the user will see the total number of results for the search. The results are presented 25 at a time. To see the next 25, click Next>>; to see the previous 25, click <<Previous. To start a new search, click New Searching Archived Files Archive files are pages that are copied from the Ingeniux Content Repository/Content Store to a Microsoft SQL database. Note: The Archive needs to be configured by the Administrator. Once a document is archived it may be searched along with local content stored in the content repository. Ingeniux CMS Search automatically searches both the Content Store and the Archive. When results are returned, archived pages that have been deleted from the Content Store are listed at the end of the list of returned files. Archived pages are highlighted in the list with Archive specified under the Remote Location column of the results page. If a page has been archived but not deleted from the Content Store, only the local page will be returned. If an archived page is returned within search results list, the user can select the page to view it. The archived page will display in the bottom right of your window. The returned archive page is read-only. Although you can select text and copy/paste it into another page, the user cannot drag it to the Content Tree to copy it as you would with a local file Using the Search Results The results are returned 25 at a time in a list at the bottom of the Search frame. Results that are returned from remote sites are highlighted. To view the next or previous set of 25, the Author clicks the buttons on the results header Copying Archive Files If an archived page is returned within search results list, the page can be selected to be viewed. The archived page will display in the bottom right of the window. The returned archive page is read-only. Although the user can select text and copy/paste it into another page, the user cannot drag it to the Content Tree to copy the page as a local file Cross Site Copy - Copying Search Results From Other Sites In order to use Cross Site copy, the system needs to be properly configured by the Administrator. When multiple sites are searched, files returned from remote sites will be highlighted in the search results. To copy a remote file, 72

73 simply click on the page in the search results list to open it in the lower pane on the right. Drag the page s icon onto the content tree. Cross Site Copy always copies the Checked Out version of a page, regardless if changes have been saved or not. Any images, files and embedded in the page will go over with the copy. However, other dependencies will not follow the page. Copy does not prompt the user to save changes before performing a copy Advanced Search Concepts The user can search for any word or phrase in the Content Store by typing the word or phrase into the query form and clicking the button to execute the query. Search results are for exact matches only. Partial matches are not returned, and there are no wildcards. Therefore, if there is a page with content homecoming, searching on homecom will not be successful. Searches produce a list of files that contain the word or phrase no matter where they appear in the text. This list specifies the rules for formulating queries: Consecutive words are treated as a phrase; they must appear in the same order within a matching document. Queries are case-insensitive, so you can type your query in UPPERCASE or lowercase. Search works for any word except for those in the exception list (for English, this includes a, an, and, as, and other common words) which are ignored during a search. Words in the exception list are treated as placeholders in phrase and proximity queries. For example, searching for Permit for Vehicle, the results could return Permit for Vehicle and Permit and Vehicle, because for is a noise word and appears in the exception list. Punctuation marks such as the period (.), colon (:), semicolon (;), and comma (,) are ignored during a search. To find all the forms of a compound word, use the hyphenated form of the compound in your search. A common example is the word database, which is a compound of data and base. Sometimes people are inconsistent in how they create compound words, so forms such as data base and data-base will appear in text. If you query for data-base, all instances of data-base, data base, and database will be returned. Boolean operators (AND, OR, and NOT) and the proximity operator (NEAR) can be inserted to specify additional search information. The search strings passed to Index Server follow standard Boolean logic. Parentheses can be used to group search terms. Here is a sample query, where all letters stand for words: 73

74 (A OR B OR C) AND (X OR Y) This query will return all items that contain either A, B, or C, and which also contain either X or Y. Logical AND's take precedence over logical OR s, so without parentheses the query would be processed like this: A OR B OR (C AND X) OR Y The pipe character can be used in place of OR s, so the query above could be written: (A B C) AND (X Y) 3.13 Spelling Checker CMS Author client provides a spelling checker. Click the Spelling icon on the toolbar to spell-check your content Check Spelling Dialog If the spelling checker finds words it does not recognize, a dialog box, like the following, appears: Figure 111: Spell Check Dialog The dialog specifies whether the word should be ignored or replaced. An explanation of the functions of this dialog follows. Not in dictionary, Consider changing, or Capitalization box: contains the misspelled word. The label of this box changes with the type of problem detected. Not in dictionary indicates that a misspelled word was detected; the word is considered misspelled because it could not be located in any open dictionaries. Consider changing indicates a word was encountered which was marked with a conditional-change action in a user dictionary. Capitalization indicates the word is spelled correctly but has a problem with its case. Suggestions list: contains a list of suggested replacements for the word reported as misspelled. Subsequent presses of the Suggest button may yield more suggestions. The word selected in the Suggestions list will be used as the replacement when the Change or 74

75 Change All buttons are pressed, unless the word in the problem box was edited. Change button: causes this occurrence of the reported word to be replaced. If the problem word was edited, the edited word is used as the replacement. Otherwise, the selected suggestion is used as the replacement. If the reported word is frequently misspelled, a user might consider adding it to a user dictionary via the User Dictionaries Dialog. The user can display the User Dictionaries dialog by selecting the Dictionaries button. Change All button: changes this instance of the word and all following occurrences of the reported word to be replaced with the word in the Change To box. If this occurrence of the word is to be replaced and no other occurrences to be changed, use the Change button. If the reported word is frequently misspelled, consider adding the misspelling and the correction to a user dictionary via the User Dictionaries Dialog. Ignore button: causes this occurrence of a misspelled word to be skipped. If the same misspelled word appears later, it will be reported. Ignore All button: Causes this and all further occurrences of a misspelled word to be skipped. Use this button if the word reported as a misspelling is actually spelled correctly. If the word is used frequently, ignore it permanently by selecting the Add button. Add button: causes the reported word to be added to the dictionary selected in the Add Words To list. Use the Add button if a correctly spelled word used often is reported as a misspelling (e.g., a family name). If the word is not used frequently, select the Ignore or Ignore All buttons instead. Add Words To list: indicates which words will be added to the user s dictionary when selecting the Add button. The Add Words To list shows all user dictionaries currently open. Add words to user dictionaries via the User Dictionaries Dialog which is accessible by selecting the Dictionaries button. Suggest button: searches for more suggested replacements for the current misspelled word. Each time the user presses the Suggest button, a "deeper" search is made. The Suggest button is disabled once all possible suggestions have been located. Undo button: removes the last change made. The Undo button can be pressed several times to remove the last several changes. Undo Edit button: removes any changes made to the text in the problem box. This button appears only if the text in the problem box has been changed. Cancel button: stops the current spelling checker operation. Dictionaries button: causes the User Dictionaries Dialog to be displayed. Use the User Dictionaries Dialog to edit the contents of user dictionaries. 75

76 Options button: causes the Options Dialog to be displayed. Use the Options Dialog to set spelling checker options Options Dialog Clicking the Options button causes the Options Dialog to be displayed. Use the Options Dialog to specify various spelling checker options. These options affect the way the spelling checker operates. Figure 112: Spell Checker Options Ignore Capitalized Words: when enabled, any words beginning with a capital letter are ignored (i.e., are skipped over without being checked). Enable this option if the text being checked contains many proper names. Ignore All-Caps Words: when enabled, any words containing all capital letters are ignored (i.e., are skipped without being checked). Enable this option if the text being checked contains many acronyms. Ignore Words with Numbers: when enabled, any words containing embedded digits are ignored (i.e., are skipped without being checked). Examples of such words include "Win95" and "Q4." Enable this option if the text being checked contains many code words or other symbols containing digits. Ignore Words with Mixed Case: when enabled, any words containing an unusual mixture of upper- and lower-case letters are ignored (i.e., are skipped without being checked). Examples of such words include "MicroHouse" and "CapsLock." Enable this option if the text being checked contains many variable names or other symbols which use case changes to distinguish words. Ignore Domain Names: when enabled, any words that appear to be Internet domain names (such as wintertree-software.com) are ignored (i.e., are skipped without being checked). Catch Doubled Words: when enabled, any word appearing twice in a row is reported via the spelling checker dialog. Case Sensitive: when enabled, a distinction is made between capitalized and non-capitalized words. For example, canada is 76

77 considered different from Canada, so canada would be reported as a misspelling. When the option is disabled, canada and Canada are considered identical. Note that the performance of the spelling checker will be reduced if this option is disabled. Auto Correct: when enabled, words marked with "Auto Change" actions will automatically be changed to their specified replacements. When disabled, a dialog prompts before the words are changed. Phonetic Suggestions: when enabled, suggestions are made on the basis of phonetic (sounds-like) similarity to the misspelled word. This option tends to improve suggestions for badly misspelled words. Enabling this option will increase the time required to locate suggestions. Note that either this option or the Typographical Suggestions option must be enabled or no suggestions will be offered. Typographical Suggestions: when enabled, suggestions are made on the basis of typographical (looks-like) similarity to the misspelled word. Note that either this option or the Phonetic Suggestions option must be enabled or no suggestions will be offered. Suggest Split Words: when enabled, two separate words will be suggested as a replacement for a misspelling containing two joined words. For example, "is the" would be suggested as a replacement for "isthe". OK button: closes the Options Dialog, and saves any changes made to the option settings. Cancel button: closes the Options Dialog, and discards any changes made to the option settings Dictionaries Dialog Clicking the Dictionaries button invokes the User Dictionaries Dialog. This dialog allows the user to edit the contents of a custom user dictionary. Different users on the same machine can have different custom dictionaries. Figure 113: User Dictionaries Action list: Used to select an action that is associated with words in the dictionary. The action tells the spelling checker what to do when it finds a word in the dictionary. The following actions can be selected: Auto change (use case of checked word): this action allows the user to automatically replace one word with another. For example, 77

78 if the user often type recieve instead of receive, the user might enter the word recieve with receive as the other word and Auto change (use case of checked word) as the action. The spelling checker will automatically correct recieve wherever it appears. If recieve were capitalized ( Recieve ) the spelling checker would automatically replace it with Receive. Note that the replacement is made automatically only if the Auto Change option is enabled (see the Options Dialog for information on the Auto Change option). Auto change (use case of other word): this action allows the user to automatically replace one word with another, always with the same case pattern as the other word. This action is useful for automatically expanding abbreviations. For example, you could enter the word TBD with to be determined as the other word and Auto change (use case of other word) as the action. The spelling checker will automatically replace TBD with to be determined wherever it appears. Note that the replacement is made automatically only if the Auto Change option is enabled (see the Options dialog for information on the Auto Change option). Conditionally change (use case of checked word): this action allows you to optionally replace one word with another. For example, if the user often types recieve instead of receive, the user might enter the word recieve with receive as the other word and Conditionally change (use case of checked word) as the action. The spelling checker will ask to replace recieve with receive. If recieve were capitalized ( Recieve ), the spelling checker would ask to replace it with Receive. Conditionally change (use case of other word): this action allows the user to optionally replace one word with another, always with the same case pattern as the other word. This action is useful for optionally expanding abbreviations. For example, the user could enter the word TBD with to be determined as the other word and Conditionally change (use case of other word) as the action. The spelling checker will ask to replace TBD with to be determined. Exclude (treat as misspelled): this action tells the spelling checker that the word is misspelled, even if it is listed in another dictionary. Words marked with this action will never be offered as suggestions for misspelled words, and they will be reported as misspellings when they are encountered by the spelling checker. Ignore (skip): this action tells the spelling checker that the word is spelled correctly, and so can be skipped over. This is the most common action. Add Word button: causes the word entered in the edit area of the Words list to be added to the currently selected dictionary. The 78

79 currently selected action and other word are associated with the word. The user can use the Add Word button to change the action or other word associated with a word. Note that the Add Word button is enabled only when a new word is typed in the edit area of the Words list. The words added may contain virtually any character but only words that contain embedded periods should have trailing periods (e.g., U.S.A. is OK, but USA. is not). In addition, the user should not enter possessive word forms (e.g., enter Mary, not Mary's). Close button: closes the Dictionaries dialog. Delete Word button: causes the word appearing in the edit area of the Words list to be removed from the currently selected dictionary. The associated action and other word are also removed. User Dictionaries list: contains the list of open dictionary files. When the user selects a file from the list, its contents are displayed in the Words list. Other Word box: contains an alternate word associated with the currently selected word. The other word is used in the "Auto change" and "Conditionally change" actions to supply a replacement word. You can enter more than one word in the Other Word box but the total length should be limited to 63 characters. Words list: contains the list of words in the currently selected user dictionary. 79

80 4 Glossary of Terms: Action Administrator Client Ancestor Ancestor Navigation Assign To Assignment List defines a specific action the system takes during a transition, i.e. send mail to specified users etc. PC Based client designed to create, edit content in addition to managing the Ingeniux Design-time server. refers to page(s) existing on levels higher than the currently selected page in the Site tree. navigation(s) referencing nodes one level and above the current page. administrative function that assigns the select page to another user. provides a list of pages currently assigned to the logged in user. Attributes meta data contained within element tags which describe the element it is associated with. Author Client PC Based client designed to create and edit content. Check In Check Out process of telling the system a page can be published if marked for publish. process of telling the system that a page is not able to be published. Child refers to page(s) existing one level below the currently selected page in the Site tree. Child Navigation navigation(s) referencing nodes below the current page. piece of XML created from a Page Template containing content with XID but does not contain layout attribute. Components perform some specific function like querying Components a database. Content Store set of xml pages that make up the site is collectively referred to as the content store. DB Query specific type of component used to pull data from an external Database. Dependencies are the connections between pages. Dependency graph Design-Time Server DHTML Editor database, specific to the publishing target, that contains the list of dependencies for each page. site used by Content Creators to build, manage, and publish content. provides editing environment to richly format content within a CDATA block. 80

81 Edit Pane Elements Full Access Full Publish Incremental Publish Ingeniux Client displays selected page in Site Tree and provides the interface for editing the currently selected page if a given page is checked out and it is assigned to the user or the user as administrative rights to the page. smallest logical division of an xml file represented by tags, i.e. <TAG>. allows specified group ability modify the node (and the nodes inheriting this permission). publishes all checked in pages marked for publish for a given page; deletes the contents of the Publishing Target before publishing all pages. publishes selected pages and its dependent pages to publishing target. Active X Controls or Mac Application used to build, manage, and publish content by connecting to the Designtime Server. Java Server Java based Runtime Server application supported on non- Windows based operating systems. MAC Client Mac Based client designed to create and edit content. Mark for Publish marks a selected page for publish; pages marked for publish are published on the next full publish. Navigation part of a page that provides a link to another resource. Page Creation Rules Page Template/Schema Page Types Pages Parent Peer Sync Permissions rule specifying a page template used to create new page and place within the site tree the new page is placed; used in conjunction with workflow to simplify the creation and management of content. XML page used as a template for creating new pages; specifies the structure including the element types and their attributes. specifies a particular page template to use when creating a new page. XML Page created from Page Template containing content with XID and Layout Attribute which points to specific Stylesheet. refers to page(s) existing one level above the currently selected page in the Site Tree. third party utility used to replicate published pages from the Design-time Server to the Run-time Server. refers to the functions a given User Group is able to perform, i.e. see site tree, delete pages, create pages, etc. 81

82 Preview Publish Publish As Publishing Target Read Only Access Recursive Recyle Bin applies specified stylesheet to the current selected page to provide a view of what the page will look like on the Run-time Server. initiates the processing of a page by Ingeniux CMS in order to ready the page for posting to the live, world-facing site. The process of creating XML pages to be replicated to the Run-time Server. publishes duplicate page of the selected page to the Publishing Target with specified friendly name. directory to which pages are published to specified during an incremental or full publish allows specified group the ability to view the node (and the nodes inheriting this permission). indicates that the operation should be applied to the page as well as its descendents If the operation in question is applied to all the children and their children and so on, it is said to be recursive. stores deleted pages. Pages can be restored if the Recycle Bin has not been emptied. Replication process of copying published pages from the Design-time to the Run-time Server. Republish repeated publish. refers to the ID associated with a particular RuleID PageCreationRule. Run-Time Server Sibling Sibling Navigation Site Map public facing, whether to a department, company, university, or the Internet, website that serves content that has been published by the Design-time site. refers to page(s) existing on the same level as the currently selected page in the Site Tree. navigation(s) referencing nodes on the save level as the current page. logical tree structure for the Ingeniux site or site(s); maintained by the reference.xml which exists over the flat file structure in the \XML directory. Site Tree Start Page logical representation of how pages are organized into ancestors, siblings, and children. attribute of an ancestor navigation element which indicates the highest level node to pull into the navigation; navigation stops one page below the page specified. Stylesheet file used to format an XML document. 82

83 Transition Trigger File Unmark for Publish Upload User Agent User Groups User Manager Users Workflow WorkflowAdministrator Workflowlog defines the movement of a page between two specific workstates; defines which actions occur during the transition. file, publishdone.txt, used to indicate when a publish has completed; used by Peer Sync to start the replication of newly published pages to the Run-time Server. unmarks a selected page for publish preventing this page from being published. function within all three clients that allows the user to load documents, images, media, or other binaries onto the Design-time Server. user agent is used to determine which stylesheet will be used to render the content for a particular client. For example if a client is using a Safari browser to access the site, then we need to use the stylesheet that is specific to this particular user agent. divide users into logical groups to which permissions are assigned. provides an interface to manage users and user groups on the site. account with access to the ingeniux system; must be a member of a user group to be able to perform any functions. provides an automated mechanism for moving content through the Ingeniux system. A workflow process is defined by a sequence of workstates that a page must move through as work is completed. interface that is used to perform administrative tasks related to Workflows. log returns the workflow data associated with the site. The log is stores as.db file (workflowlog.db) in the xml directory of the site. WorkflowlogEntry entry in the WorkFlowLog. Workstate The location of a given page within a workflow. document utilizing tags to logically structure content. This document does not contain any formatting XML information. code used to transform XML and stylesheets into complete documents- usually to be consumed by an Internet XML Processor Browser. XSLT stylesheet language used to format an XML document. 83