Child pages
  • Apstrata CMS
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Folder structure

  • build: ant build scripts for obtaining libraries and running js/css packaging utilities
  • lib: Libraries used in the site
    • apstrataCMS
    • ApstrataSDK
    • dojo: use dojo 1.6, the folder should contain directly the 4 dojo packages; dojo, dijit, dojox and util 
  • manage: cms backend and configuration files
  • src: Javascript code and php templates
    • home: base folder for widgets used on the site
    • templates: php templates
      • [themeName]: a folder per php templates set (customize templates here)
  • themes: CSS themes
    • [themeName]: a folder per css theme (customize templates here)
  • index.php
  • page.php: main controller

Configuration files

  • manage/config.php: Main configuration php script for the site
  • src/home/ApConfig.js: Apstrata config for the widgets used on the site
  • src/home/CmsConfig.js: Apstrata config for the cms

CMS Configuration 

  • apstrataServiceURL: apstrata service base URL, i.e.: ""
  • apstrataKey: apstrata account key, i.e.: E83D557788
  • contentStore: apstrata store, i.e.: site
  • developmentMode: this should be true throughout the development process, set to false on production deployments
  • useStub: this should be true, if the CMS should not get the content from apstrata but from a local set of test data, this is convenient in development
  • apstrataConnectionTimeout: connection timeout for cross domain apstrata connections, typically 30000
  • urlPrefix: This should be set to the default php script that creates the pages i.e.: "page.php?pageId=", typically this would be "pages/" if url rewriting is enabled, as an example pages/myPage would substitute page.php?pageId=myPage  
  • template: name of the template/skin used, i.e.: apstrata




  • No labels