SiteDeveloper

Site Developer

A site developer

• assembles a site from existing components.
• They configure how components should work together.
• They are developers. They may create high-level content types, ViewComponents, or ApplicationFunctionalityComponents.
• GLUI specialists

They are component consumers, not producers. But they may also be component "customizers".

Goals

• Provide applications to solve problems or automate processes (e.g. Content management).
  • Set up a site, including implementing the site structure.

    Use case: CreateASite

    Use case: Copy an existing site

    Use case: Create folders

    Use case: Define which content types can be created

  • Use existing building blocks (See IntegrateSoftwareFromMultipleSources and Packages)
    • FileSystemPackages

      Use case: Install a file-system package

      This should include analysing the impact of a package prior to installation

      It should also check dependencies.

      Use case: Update a file-system package

      This should include analysing the impact of a update prior to update

      It should also check dependencies.

      Use case: Uninstall a file-system package

      This should include analysing the impact prior to uninstall (e.g. with this break other dependencies.

      It should also check dependencies.

      • Change file-system package configuration

        Use case: replace a file-system configured component with a file-system configured component

        Use case: disable a file-system configured component

        Use case: Change permission useage for a file-system package

        Use case: replace a file-system permission definition

        Use case: disable a file-system permission definition

    • DatabasePackages

      Use case: Install a database package, HowToInstallAPackageInALocation.

      It should also check dependencies.

      Use case: Update a database package

      This should include analysing the impact of a update prior to update

      It should also check dependencies.

      Use case: Uninstall a database package

      This should include analysing the impact prior to uninstall (e.g. with this break other dependencies.

      It should also check dependencies.

      • Change file-system package configuration

        Use case: replace a configured component

        Use case: disable a database configured component

        Use case: Change permission useage in a database component

        Use case: Change permission useage in a database package

        Use case: replace a database-package permission definition

        Use case: disable a database-package permission definition

  • Discover existing components and how to use them

    Use case: Browse existing components, by component type, by package, by interface, by content-type, and so on.

    Use case: Browse components that are used with a partular object

    Use case: ViewComponentAPI

  • Customize existing components

    Use case: Create a new view from an existing view by specifying different templates.

  • Create DynamicContent

    Use case: Create a ZPT Page

    Use case: Create a DTML script

    Use case: Create a Python script

  • Find out what went wrong

    This is essentially debugging, but may include high-level debugging like auditing. This needs a lot more brainstorming.

• Assure site security (See SecurityResponsabilities?)

  Use case: Defines permissions and roles globally

  Use case: Define permissions and roles through the web

  Use case: Change required permissions for existing components

  Use case: Grant permissions (especially to roles and groups)

  Use case: Audit security