You can add the following views to your pages:
Team list (in different styles)
default list view (may be configured)
grouped by team (with a jump-menu)
Single view (= detailed information of one person)
BOX (= contact person for this page / department)
You can create
persons
groups
location
Every person can be added to none, one ore multiple groups. The groups represent the teams or organizational units of (for example) a company. For each team, you may select none, exactly one or multiple team leaders (they may be team members, too – but the don't need to be).
You can enter the following information to a group record:
Group name (no HTML allowed)
Team leader(s) (Select none, one or multiple team leaders)
a page (pointing to a page that contains additional information about this team, will be linked in the singe view)
You can enter the following information to a person record:
Hidden (default: no)
Last name (no HTML)
First name (no HTML)
Image (You can upload a picture of this person or select an existing file from the fileadmin directory; up to 1M in size)
Groups (Select the teams in which this person is a member)
Function (The job title, like “CEO”, no HTML)
Email address (an Email address, no HTML)
Tasks (Enter some descriptive words on the job this person does, no HTML)
In company since (enter a date since when the person is in the company)
Birthdate (enter the date of birth)
Opinion (Enter some thoughts or a citation, no HTML)
Location (If you'r company is spread over the world, note the city where this person works, no HTML)
Room (Enter the room number of the office where this person works, no HTML)
Phone (The phone number, no HTML)
Office hours (Enter the times when this person is available, no HTML)
Files (You can upload up to 5 files, up to 1.5M each. This can be a CV for example. The files can be uploaded directly or chosen from the fileadmin directory.)
As from version 0.1.0, this extension supports localization of it's records. So it's possible to have multi language sites with a one-tree-fits-all concept. What you need to do for this to work:
Create a “Website language” record on page 0 (the root).
On each page that you like to translate, add a “alternative language” record. Configure this record to point to the new language you created in the root of the site. Also fill in the field “page title”, and write it in the translated language (that's the page title that will be shown on the translated frontend).
Important: Also create such an “alternative language” record in the sysfolder where your records are stored.
Now you can begin to localize your page content (including the plugin of this extension) by clicking on the flag shown next to the record title.
By default, non translated records will be shown in the default language. If you want to be more strict, you can change this behaviour in the TypoScript setup of your site. Just add the following line to your template:
plugin.tx_bzdstaffdirectory_pi1.sys_language_mode = strict
With this activated, non translated records will be invisible to the frontend. In the teamlist, they are hidden. In the contactperson and detailed view, an error message will be shown.
The template for the detail view that ships with the extension contains all markers that are available to show in the frontend. To use some or even all of these markers in the list view, you can copy paste them. All markers that are generated for the detailed view can also be shown in the list view.
Just one change is needed: You must rename the wrappers: In the detailed view, the wrappers are named like ###FIELD_WRAPPER_XYZ### - to use them in the list view just rename them to ###LISTITEM_WRAPPER_XYZ### (where XYZ is the effective name of the field).