AboutContactGetReadHelp

Software components

Book page submitted by admin on Tue, 2006-04-18 09:29. [nid:1013]
in
  • folkd
  • LinkedIn
This page is part of a set of pages: "corepractice.org technical manual"
Turn the page:
‹ How the Application Architecture is/will be implemented in DrupalupUser requirements ›
       CMS
The website is currently based on Drupal Content Management System (CMS).
We looked at Plone and Xaraya as two other close contenders, but Drupal www.drupal.org won out due to its maturity, its extensive user contributions, its superior community capabilities and e-commerce capabilities (memberships, fees etc). See appendix for rankings at the time the comparison was made.
The main perceived weaknesses of Drupal are image handling, content type handling and workflow. Tests will be (March 2006) performed to confirm Drupal can meet user requirements. Significant new developments have happened and are ongoing in Drupal in these areas.
 
       Database
 
MySQL was chosen because it is
            Common among open source products, including Drupal
            Open source
            Well known
            High performance and scalable
 
 
       Web server
 
Apache was chosen because it is
            Common among open source products, including Drupal
            Open source
            Well known
            High performance and scalable
       Financial
Selection of a financial system will be left to the IoCP’s first Treasurer, but it is expected to be a free open source package[1]. Or the Institute might decide to invest in something like Quicken or MYOB.
Requirements include:
            Multiple currencies and currency conversion
            Ability to handle both US and NZ tax systems (and others?)
            Handle subscription-style products


This page is part of a set of pages: "corepractice.org technical manual"
Turn the page:
‹ How the Application Architecture is/will be implemented in DrupalupUser requirements ›