Manual and Documentation

NOTE: This manual describes HammerKit version 3.5. To view documentation for the current release of HammerKit Studio, please go to http://manual.hammerkit.com/
search
Index / C. Using HammerKit tools / Creating and editing content

A. Introduction
B. Installation and Configuration
C. Using HammerKit tools
Home
Creating and modifying site design
Creating and editing content
Managing site structure
Constructing and editing a component
Using directories
D. Object API
E. HammerScript
F. Access Rights
Creating and editing content

Managing site structure
Constructing and editing a component

You can create and manage dynamic content with HammerKit�s content editor. You can create pages containing text elements, images, links, file attachments, tables, web forms and actions in free defined order. And you can define the page design using pre-defined styles. In the content editor you can:
  • create, edit, organize and publish content
  • create and edit page layout templates (See Templates)
  • create and edit element templates for element groups
  • create and edit restricted access page components (See Page components)
  • create and edit HTML-formatted e-mail campaign messages (see xMedia Campaign Manager)
  • define various page properties
  • create and edit text elements and their properties
  • upload images and edit image elements� properties
  • create and edit links to pages of the site and to outside URL:s and e-mail addresses and their properties
  • import files to the file directory and create and edit file attachment links and their properties
  • import text from HTML and RTF formatted files
  • create and edit tables and their properties
  • create and edit input forms and their properties.
  • include action modules to pages and specify their settings.

Standard HTML supported

The web pages created and published with HammerKit comply to the HTML 4.01 specifications.

Basic concepts

The interface of the content editor is based on the technologies developed by Basewell Oy, Finland. All operations are carried out using interface elements available in a standard web browser. The content editor�s tools are used to upload, access and manipulate the data in the database. This is the introduction to the Content editor�s interface

Element

The content of a web page or component is composed of elements. The elements contain settings that define it�s behaviour in the web page. When the page is accessed by the visitor the HammerKit composes the source code of the page from the database elements. The elements are created and edited with content editor�s tools.

Elements are inserted in the page or component with element tools.

The elements
  • text
  • image
  • link
  • file
  • table
  • form element
  • action module
  • script
  • tag
The HammerKit�s element model brings many advantages:
  • dynamic linking
  • easier re-arranging of content and actions
  • easier editing of existing content elements

Dynamic elements

You can transform an element into a dynamic element by assigning it an element name. The element name is a database label that the system uses to save different values to one element. This makes possible the dynamic printing of the content and data from the elements in other pages (see Print element module, Logic scripting tool and Page2Form module) and the use of the element templates to define the design and structure of recurring components (for example product information, news box, event announcement, advertisements etc.) (See Using element templates)

Components

Component is a composition of one or more elements. Actually a page is one type of a component consisting of text elements, images, links, files, form elements, tables, scripts and action modules. Each component is recognized by its unique identification number: article id.

A component with sub-pages acts as a folder or sub-directory. To put the other way, the folder acts as a component.

A component (or page) can also contain other components via dynamic linking.

Creating a web page with Hammerkit is a process of composing elements into a component.

Action Modules

HammerKit contains a wide selection of action modules. All the actions in the HammerKit-generated web page are composed from action modules. Action modules are pre-programmed actions with a easy-to-use visual interface for setting the module�s properties and behavior. (See Modules)

Click to edit operations

In most operations of the content editor the first click selects the target and the second click chooses the operation.

Use VIEW menu to
  • switch the viewing mode to tagged or not tagged (visual)
  • show or hide the Element toolbox
  • show or hide the Component menu editor
  • show or hide the HammerKit toolbox
  • modify the background color of the content container

UPDATED: 11.09.2005 17:20


� HammerKit Oy 2008 UPDATED: 11.09.2005 17:20