iAPPS is a product of Bridgeline Digital
Below are some terms that explain key concepts for iAPPS and for the internet more broadly.
| Term | Definition |
|---|---|
| Archive | To store items, such as page templates, which are not in current use. These are stored in an archived folder, but are not deleted. Archived items can be restored (unarchived) if needed. |
| Activate | Activate See deactivate. |
| CSS | Cascading Style Sheets. Style definitions (for example, font size and color) for elements in a page (such as headings) that are included in a separate file, which may be shared by multiple pages. |
| CMS | Content Management System. iAPPS Content Manager is a web CMS. A CMS is used to track your internal and external content and to align your content with your company goals. |
| CMS group | A group of users who create and manage content for a site in iAPPS Content Manager. |
| CMS object | A CMS object is a component of a web page that can be managed by a CMS user. A CMS object may be one of the following: • menu item • page • file • image • content item • content item definition template • page template • style sheet (CSS) • list |
| CMS user | A user who creates and manages content for a site in iAPPS Content Manager. |
| Container | A Container in iAPPS Content Manager is a section in the Control Center or other iAPPS screen that provides access to commonly used features and functions. A Container in Site Editor is a pre-defined box on a page template where CMS users can insert pre-defined types of content such as text, images, multimedia, etc. |
| Content | Refers to the things a CMS user may insert in a page, including text, images, multimedia, links to documents such as PDF and MS Word files, etc. |
| Content area | Refers in general to the area on a page where CMS users can insert text, images, etc. |
| Content Definition Template | A pre-defined layout that specifies the exact placement of text, images, and other content. The content item definition template uses an XML form to store types of content and a stylesheet (.xslt) to create the output. |
| Content item | A single piece of content in a page. A content item can include text, images, etc. in a pre-defined layout (refer to content item definition template); or, a content item can include text, images, etc. in whatever layout (free form) a CMS user creates. For example, a CMS user might type in a press release with text and images in either a pre-defined layout or a free form layout. |
| Data Libraries | Collectively refers to the three libraries in iAPPS Content Manager that contain data that CMS users can insert into pages. These are the Content Items Library, Images Library, and Files Library. |
| Deactivate | To make a user inactive; that is, deny him or her access to iAPPS Content Manager. A user can be activated; that is, granted access again if needed. |
| Directory | A folder that contains images, files, or content items for a site in iAPPS Content Manager. Images and files go into a physical folder (like in MS Windows Explorer). Content items have only virtual folders; they do not have a corresponding physical structure. Note that pages are stored under Menus and Pages and not under “directories”. |
| Display Libraries | Collectively refers to the three libraries in iAPPS Content Manager that contain items that are used to define and format pages and content. These are the Styles (CSS) Library, Page Templates Library, and Content Definitions Library. |
| File | A document such as a PDF or MS Word file. Files are stored in the Files Library. Files generally do not open directly inside a page; CMS users can insert links to files in their pages. •Multimedia files, such as Flash movies, are also stored in the Files Library. Unlike the other file types, multimedia files open directly inside a page. |
| Image | A graphic such as a logo, photo or line drawing. Images are stored in the Images Library and CMS users can insert images into pages. |
|
Index Terms (Tags) |
Terms that reference specific CMS objects for indexing, including content items, pages, files, images, and users. Tags can be used throughout your site and the product suite for varying types of material. Even users can be assigned tags, either automatically or manually. Their exact uses will vary depending on your specific site setup, but tags allow website creators to group, filter or collect information. So for example, a retail site could have an tag assigned to buyers of certain products. They might then run a Marketier email campaign with information on similar products. |
| List | A group of CMS objects, (such as files) that are displayed on a single webpage. Content Manager displays these objects in a numbered or bulleted list. |
| Menu item | An option on a site menu. A website user clicks a menu item to move to another page. |
| Page | A single page on a site that contains a collection of text, images, multimedia, etc. A page is created from a page template, and represents the full-screen view in the browser (everything the site visitor sees in the browser window is part of the page). Pages are stored under “Menu Items” and not under “directories”. |
| Page template | A page with a pre-designed format and pre-defined containers that CMS users can use to create a page, then fill in that page with text, images, multimedia, etc. |
| Properties | The attributes of a CMS object, such as the title and description of a page or file. |
| RSS feed | A Really Simple Syndication (RSS) feed contains content in the form of pages from an associated web site. A feed allows website visitors to receive automatic notifications when the content is updated. |
| RSS channel | A RSS channel is the stream in an RSS feed. A CMS user can define channels that contain one or more website pages. The channels make up the feed that website visitors can receive. |
| Security levels | Settings that determine access level permissions for website users. |
| Site | A connected group of pages. Also referred to as website. |
| Style sheet | Refer to CSS. |
| User roles | User roles define the tasks that CMS users can perform. These roles include author, approver, and publisher, among others. Refer to Section 1.4 for a complete list of user roles. |
| Website User | Visitors to the live front-end of the website. They may or may not be logged in. Users can be anonymous or placed into security levels or audience segments. |
| Workflow | The specified order in which a page is sent from one CMS user to another for tasks such as editing, approval, and publishing. |
| XML | Extensible Markup Language. A computer markup language that manages custom tagging for your information storage needs. |
|
iAPPS is a product of Bridgeline Digital
|
