...
Item List Blocks are probably very useful elements to embed in body elements of general purpose pages. A "Topic Page" could then just be a General Purpose page with a set of List Blocks with the above Block Titles.
There is an example of a Topic Page in the new format here: http://mit.edu/meponine/dontindex/ist/beta/topics/software/index.html
There is an example of a Topic Page from the current active site here: http://web.mit.edu/ist/topics/software/index.html
Service Page
A Service page contain two layers:
- Service Overview, which contains the following elements:
- Overview text
- How to Obtain
- Price
- Contact Information
- Service Detail
- this varies sufficiently from service to service that it has no regular elements
There is an example of a Service Overview in the new layout here: http://mit.edu/meponine/dontindex/ist/beta/services/software/mcsa.html
and Service detail: http://mit.edu/meponine/dontindex/ist/beta/services/software/mcsa-details.html
The same overview page in the currently active website here: http://web.mit.edu/ist/services/software/msca.html
existing service detail here: http://web.mit.edu/ist/services/software/msca-detail.html
Team Page
A team page is a simple subclass of the General Template with the following body elements:
- Mission
- 0...n Service Offered links
- 1...n Team Members, each of which has the following elements:
- Team Leader link (links to profile)
- Role
- 0...n Resource links (links to sub-page or external departmental website)
Team page in the new layout here: http://mit.edu/meponine/dontindex/ist/beta/admin/templates/template08-team-page.html
and an existing team page: http://web.mit.edu/ist/org/admincomputing/
Table Page
A table page has a body with the following elements:
- Introduction
- 1...n Sub-tables, each of which has the following:
- Heading
- 1...n Fields, each of which has:
- Field Label
- 0...n Field Values Values
Sample table page in the new layout: http://mit.edu/meponine/dontindex/ist/beta/admin/templates/template03-simple-table.html
Procedure
A procedure page is the most elaborate of the general pages, as follows:
- Page Introduction
- 0...n Anchor links (ideally automatically generated from the anchored elements)
- 0...n Procedures, each of which contains:
- Procedure Title
- Procedure introduction
- 1...n Steps, each of which has the following elements:
- Directions
- Result
- 0...1 Image
- 0...1 Tip
- 0...1 Warning
- 0...1 Note
- Procedure conclusion
Steps may have sub-steps, but these are probably not worth codifying as separate elements.
An example from the new layout is here: http://mit.edu/meponine/dontindex/ist/beta/admin/templates/template11-advanced-proc.html
An existing procedure is here: http://web.mit.edu/ist/services/printing/setup.html
ITinfo (dynamic) templates
TBD
The new layout has the following sample pages for ITinfo:
List page: http://mit.edu/meponine/dontindex/ist/beta/itinfo/product-list.html
Product page: http://mit.edu/meponine/dontindex/ist/beta/itinfo/product.html
version page: http://mit.edu/meponine/dontindex/ist/beta/itinfo/version.html
article page: http://mit.edu/meponine/dontindex/ist/beta/itinfo/article.html
There are some ITInfo page types that do not have samples in the above location:
Answer
User Group
...