• Admin Interface

    Symphony’s Admin Interface, or back end, enables authors to manage content and system settings.

    • Blueprints

      Blueprints refers collectively to a Symphony project’s pages, components, and sections.

    • Components

      Components refers collectively to a Symphony project’s events, data sources, and utilities.

    • Maintenance Mode

      Maintenance Mode, when enabled, disallows access to a Symphony project’s front end and replaces it with a placeholder page.

    • Navigation Groups

      Navigation Groups allow Sections to be grouped together in the Symphony admin interface.

  • Authors

    Authors can login to the admin interface and manage a project and its content.

  • Data Sources

    Data Sources fetch, filter, and sort data and expose it as XML to pages for templating.

    • Data Source Chaining

      Data Source Chaining enables a data source to be filtered using the results provided by another data source.

    • Data Source Filters

      Data Source Filters can use parameters, advanced operators, regular expressions, and normal values to filter results.

    • Data Source Output Parameters

      Data Source Output Parameters are set using the results from a data source and enable data source chaining.

  • Devkits

    Devkits provide useful developer tools on the front end which facilitate debugging, profiling, and other tasks.

  • Ensembles

    Ensembles bundle an entire Symphony project, including its database and workspace files, into an installable package.

  • Entries

    Entries represent individual content records in a section.

    • Handles

      Handles provide sanitized, URL-friendly equivalents for the values stored by many field types.

    • System Dates

      System Dates store creation timestamps for a Symphony project’s content entries.

    • System IDs

      System IDs provide unique identification numbers for a Symphony project’s content entries.

  • Events

    Events facilitate advanced front-end interactions such as data submission.

    • Event Filters

      Event Filters add additional conditions or actions to an event.

  • Extensions

    Extensions add specialized functionality to the lean, mean Symphony core.

    • Delegates

      Delegates allow developers to manipulate input and output and perform other tasks during the generation of back-end and front-end pages.

    • Extension File Structure

      The Extension File Structure enables Symphony to detect and load extension files automatically.

  • Fields

    Fields give shape to sections and their entries by defining the data they capture.

    • Field Types

      Field Types define the structure of fields and govern their behavior in capturing and outputting data.

    • Text Formatters

      Text formatters can be applied to fields to transform or format their content before saving.

  • Git

    Git version control is used to manage updates and contributions to the official Symphony codebase.

    • Github

      Github hosts the official Symphony repository and the repositories of most Symphony extensions.

  • JIT Image Manipulation

    JIT Image Manipulation provides a URL-based API for dynamically transforming images.

  • Pages

    Pages constitute a Symphony project’s front-end interface and determine its URL structure.

    • Page Templates

      Page Templates transform the XML provided to a page by its data sources.

    • Page Types

      Page Types enable special handling of pages, and are used to specify a project’s home page, error pages, etc.

    • URL Parameters

      URL Parameters enable pages to capture and utilize parameters set dynamically in their URLs.

  • Parameters

    Parameters channel dynamically set values through the system for use by data sources and in the templating layer.

    • Data Source Output Parameters

      Data Source Output Parameters are set using the results from a data source and enable data source chaining.

    • URL Parameters

      URL Parameters enable pages to capture and utilize parameters set dynamically in their URLs.

  • Sections

    Sections model and define the types of content to be managed in a Symphony project.

    • Field Types

      Field Types define the structure of fields and govern their behavior in capturing and outputting data.

    • Navigation Groups

      Navigation Groups allow Sections to be grouped together in the Symphony admin interface.

  • Utilities

    Utilities enable the abstraction and reuse of common template functions and markup.

  • Workspace

    The Workspace directory stores project-specific files like data sources, pages, utilities, and uploads.

  • XML

    XML powers Symphony’s data engine and is used to structure content for templating.

  • XSLT

    XSLT powers Symphony’s page templates and utilities, which together comprise the templating layer.

    • XPath

      XPath is used by XSLT to address nodes and perform basic computations while traversing an XML document.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details