Configurable and Extensible

Traction TeamPage provides built-in forms to install, configure and manage the initial setup including permissioned access rules and connection to external email, Active Directory, LDAP, and Jabber services.

TeamPage configuration wizards guide you through initial setup and configuration, as well as initial configuration of new collaboration Spaces you create. Named user accounts can be created automatically (by live connection to Active Directory or LDAP services), using TeamPage forms including self-registration. You can configure TeamPage to send temporary passwords to TeamPage account holders, and welcome message to new users.

TeamPage Server, Space, and Personal preference configuration

TeamPage configuration forms allow people with Setup permission to configure a wide variety of options and defaults - from CSS interface colors and layout, to default time zone, locale (and language), to Proteus skin configuration options to let you configure the number and order of top-level tabs shown in each TeamPage space. You can choose any of these tabs to shown in any space: dashboard, status, activity, wiki, tag, action tracking, calendar, documents. This allows you to trim options to match how you want to use each Space.

CSS Stylesheet Customization

TeamPage view layouts, colors, and content can be customized using CSS style sheet overrides that are easy to configure, test and install. TeamPage's plug-in architecture makes it simple to configure and maintain a coordinated set of style sheet (or style sheet and SDL) customizations as plug-ins that are easy to install and work across TeamPage software updates.

TeamPage SDL and SDK

The Traction Software Developers Kit (SDK) and Skin Definition Language (SDL) make it easy for developers to extend or customize Traction Teampage's appearance, behavior, and connections to other systems beyond what you can do with TeamPage forms and CSS customization. You can build a new skin that runs on the same TeamPage server as Traction Software's standard skins to implement specialized systems with your own programming team, or with the assistance of Traction Software and its partners.

Traction's Skin Definition Language (SDL) makes it simple to program look and feel extensions. Traction's Java Software Developer Kit (SDK) can be used to create new SDL tags, derive from Traction's Java SDK components, or create new authentication, notification and other components using the SDK's run-time extensible interfaces. Traction Customers have full access to the Java source code and JavaDoc of the SDK layer - including the full SDL implementation and Google Web Toolkit (GWT) components - at no additional cost. Traction Software builds and delivers all of its skins using the same SDK / GWT / SDL codebase we provide to our customers, partners, and developers.

With these tools it's possible to create custom interfaces, views and forms, Custom Interfaces, Views and Forms as well as special purpose Skins (User Interface). Traction's plug-In architecture makes it simple to share extensions as well as deploy and maintain them across software updates.

Traction's SDK can also be used to create new widgets.

Plug-in Architecture

Developers can use Traction's plug-in architecture to add new functions to TeamPage or override and extend the appearance and behavior of standard TeamPage features and interfaces. The architecture preserves plug-ins in their own directories so the installation of new plug-ins or software updates is non-destructive.

Plug-ins makes it simple to fine tune, re-arrange or simplify the appearance and behavior of standard skins as well as add unique features and widgets'.

Plug-in extensions are packaged as self-contained files that are easy to create, share, and install in an extensions directory. Plug-in extensions are preserved across software updates to simplify software maintenance as well as initial deployment.

The TeamPage plug-in architecture includes Server Setup web page that makes it easy for server administrators to install and configure options plug-in extensions. A personal setup page is also provided to make it simple for individual users to configure their own plug-in settings. For example, each user can specify a Jabber Username and edit notification options for when using Traction's Jabber notifier plug-in.

Here's a an image of the page where you upload, delete and manage plug-ins, the Jabber notifier is selected:

When you click Configure, a form pops up allowing the administrator to setup server level properties and default user level properties of the plug-in.

Plug-in's can extend or override Traction's Skin Definition Language for simple UI extensions, or use Traction's Java Software Developer Kit to create new SDL tags, derive from Traction's Java SDK components, or create new authentication, notification and other components using the SDK's run-time extensible interfaces. Traction Customers have full access to the Java source code and JavaDoc of the SDK layer - including the full SDL implementation - at no additional cost.