The following are some guidelines for writing content for the TPTP website.

1. The web content for TPTP is maintained in a CVS repository. You will need to obtain access to the following:

   Host: dev.eclipse.org
   Repository Path: /cvsroot/org.eclipse
   Connection Type: extssh

   (Information coming soon on how to obtain access.)
2. Use the following style sheets: http://www.eclipse.org/default_style.css and http://www.eclipse.org/tptp/eclipse_style.css
3. The content must be either HTML format or PDF format.
4. HTML formatted document guidelines:
   • Use the following template for the document HTML document template. You can import this template into your HTML authoring tool.
   • If you are using Microsoft Word to author your documents, ensure that you save the document as a web page, with the filtered option.
   • If you are using Microsoft Front page to author your documents, ensure that the filtered option is on as well.
5. Use the directory map below to place your content in the appropriate directory.
6. In each directory, there is an index.html or index.php that you can update with a link to your document.

The following listing outlines the directory structure for the TPTP web content.

• tptp: Root directory for all TPTP Web Content. main.html is the page to be edited for the main project page.
  • groups: Directories to be used by the different TPTP groups.
    • Architecture: Architecture Group documents, information, meeting minutes, etc.
      • documents:
      • meetings:
    • Marketing: Marketing Group documents, information, meeting minutes, etc.
      • pressroom: Press related information
        • pressreleases: Press releases for TPTP
    • PMC:
    • Planning:
    • Requirements:
  • home: Content that is common across projects.
    • architecture: Overall project architecture documentation.
      • images:
    • archive: Pre 3.3 information (migrated from Hyades)
    • doc_resources: Documentation guidelines
    • documents: Documents common across projects
      • process: Documentation related to TPTP processes
      • resources: Documentation for developer resources, e.g. development guidelines
      • tutorials:
      • webcontent: Directory map information
    • downloads:
      • drops:
      • installguides:
      • releasenotes:
    • images:
    • project_info: Cross project information.
      • faq:
      • featureplans: All current and future feature plan information.
        • features: Feature documentation mappingn to bugzilla enhancements.
        • themes: Cross project information.
        • utils: Utilities used for comparing feature plans with bugzilla entries.
      • devplan: Release plans, action plans.
      • general: General project info such as what is TPTP, contributing to TPTP, etc.
      • schedules: Cross project schedules.
      • structure: Cross project structures, component matrix.
  • reports: Reports for enhancements, defects, test results.
    • bugs: Bugzilla reports (generated queries)
    • test: Test pass reports
  • monitor: Monitoring tools project.
    • archive:
    • documents:
  • performance: Tracing and Profiling tools project.
    • archive:
    • documents:
  • platform: Platform project.
    • archive:
    • documents:
  • test: Testing tools project.
    • archive:
    • documents: