The Page Module is where most site editing of pages and page content is done. Selecting the module shows the architecture of the website in the Navigation Pane (in the centre). The architecture is represented as a tree structure showing the relationship of pages to each other.

This is the module that website editors and contributers use most.

What you see here is what the site administrator would see. In a live installation, if you were not the Administrator what you would see would depend on what the Administrator had decided you should be able to interact with. You might see far fewer modules. The pages visible in the tree would be the ones that you have rights to access and edit.

This module shows the page-tree architecture and then a preview of the selected web page as it will appear in the Front End.

You can edit page content directly on the previewed page - by clicking on an edit icon which appears beside each editable element.

The List module shows all the content records stored for the page. This is useful for viewing the records for users, content items, addresses and templates related to a page.

Some extensions like the guestbook extension save records on a particular page or in a system folder; the List Module is useful for viewing and editing these records.

Access control in TYPO3 is done on multiple levels. Apart from access defined for modules, tables and tablefields, every page has an owner, group and settings for each of them. Page permissions can also be set here by Administrative users.

Enables management of versioning.

Using this module you can define versions, and return the curent workspace to a previous state if necessary.

TYPO3 normally does not delete anything - it merely makes changes invisible. Effectively this makes you site past proof.

Templating is managed at a number of levels within typo3. It is mediated through typoscript - a declarative programming language. A consequence of this is that each page can behave and/or appear more-or-less differently to others, if necessary. This module is mainly of interest to site engineers, and is kept well hidden from site users.

File management is an integral part of the system. You can configure TYPO3 to mount any path on the server and then allow certain backend users/groups to store files in those folders. Files can be uploaded, renamed, copied, moved, deleted - even edited online! Selecting an image folder enables a thumbnail view (a smaller view like those you can see on the left hand side) of the images in a folder. Other image information such as size, date of upload and file type is shown with the image.

Enables editing of Backend (BE) Users' personal setup details.

Editable features include name, username, email address, password, BE language (more then 40 langauges are available) and BE layout preferences.

From here you can control exactly what each user is able to see and interact with in the backend, by assigning them to backend groups, and giving the individual permissions.

The module manages Workspaces. Each page has at least two workspaces - the live workspace, where changes are implemented immediately, and the Draft Workspace, where changes can be made and viewed, though they do not appear on the website until published. Users of the Draft workspace may or may not have permission to publish, and the system enables them to view their work in a browser as it develops without impacting the main site.

Creating new pages is very easy. As you create pages, TYPO3 will organize them in the hierarchy of the page tree. If you want to change your site architecture, you can simply move the pages around within the system.

Page content types are selected when adding a new content element. Page content types can be changed at any time from the pull-down 'Type' menu at the top of the content element. The two most commonly used elements are text and image elements. In one page, you can use multiple content elements.

TYPO3 features a Rich Text Editor which allows WYSIWYG editing of the web pages. This resembles Word or any other word processor so closely that users will find it extremely intuitive to operate. As an administrator, you can configure it to display your stylesheet classes and filter unwanted HTML.

When backend users are logged in, the web pages may display small control panels and 'edit icons'. These provide an intuitive, context-oriented way of editing content on directly on the web pages. If you need to edit something while browsing the website, simply click the little pencil icon near the object.

An admin panel optionally appears at the lower left of pages when they are previewed. This lets you control many features of the editing and publishing process, and gives feedback on issues such as page loading times.

With the mailform wizard, you can easily add a web form with customizable fields such as text fields, radio buttons, selector boxes, file upload fields, etc.

Fields can be set to be voluntary or compulsory, and the completed form can be mailed to an arbitrary number of recipients.

While this is good for communications coming inwards one at a time to specific individuals, it does not help you if you need to take a survey, and store the results in the database on the server for analysis later.

Questionaire is an extension that does this. The results can be exported to a csv-file to analyze in Microsoft Excel or the statistical program SPSS or its open source concurrent PSPP.

Backend users are allowed to log into the TYPO3 backend and do permitted actions. Each user can also be a member of one or more groups and each group can include sub-groups. Groups contain the main permission settings you can set for each user. Many users can be a member of the same group and, thus, share permissions.

The Extension manager allows extentions to be downloaded from the typo3 repositary or one of its mirror sites. You can also install and uninstall loaded extensions, check for updates for your current extensions, and download manuals for most extensions. With the extension kickstarter wizard, the framework for new extensions can be built very easily. A basic frontend output can be created, though further coding in php is necessary to create a working extension.

Third party products can be integrated seamlessly into TYPO3. For example, the popular GPL-application, phpMyAdmin, is available by default for admin users. It is preconfigured with the current database of TYPO3 and access is managed automatically by TYPO3. phpMyAdmin allows administrators to do really low level operation of the database.

The Install Tool ensures that the installation and upgrade process of TYPO3 is easy. Each time TYPO3 releases a new version or preview, the main database structure may be altered. The Install Tool will automatically identify which changes are needed in order to upgrade the database and with a single click, those changes are performed. TYPO3 is a very comprehensive system which currently runs on nearly any PHP-enabled server. However, the more exotic features, like the powerful image generation engine requires special software. The Install Tool provides tools for analysis and bug-tracking of the installation.

The Log keeps track of changes as they are made, and allows them to be compared and reversed. It also records who has logged in to the system, and what they did while logged in, and can therefore be invaluable in both tracking down who has caused problems and undoing the damage. Generally typo3 does not remove information from the database - it simply marks it as deleted, and although it makes sense to perform a manual clean out from time to time, the log, together with the use of workspaces and versioning, ensures that it is quite difficult for anyone to do irreperable harm to the system.

Each typo3 site can be configured to support a default language, plus multiple parallel languages, which form another dimension to the pages - each page has a separately editable sub-page for each language. Communication between the main page and the subpages is available so that content elements can be copied to the sub-pages complete with their text, for translation. Pages with a translation in a given language are accessible by means of a language menu which can be interted anywhere on the page. If a translation exists (and is marked visible), the relevant language page will appear if the user has selected a non-default language. If no translation exists for a content element, it can either be omitted altogether from the translated page, or it can be diplayed using the default language. The backend also exists in many languages, and different users can be configured to see the backend in that language, instead of the default.