1.

contentManagement

automated systems...

A Content Management System (CMS) is a software system used for content management. Content management systems are deployed primarily for interactive use by a potentially large number of contributors. For example, the software for the website Wikipedia is based on a content management system.

Taken from wikipedia.com

 


2.

availableModules

click each module for more information...

Required by default, the core system runs it's own custom API system outputting various formats; xml, rss, array, flashFormat (used for dynamic flash) to name a few. The core system comes pre-built with a full WYSIWYG (what you see is what you get) editor; tinyMCE. Using tinyMCE and a dynamic page management module you can manage your entire web sites' content with the core system.*

Some of the modules pre-built into the core system include:

  • dashboard
  • account Management
  • account Groups (default groups shown below)
    • administrators
    • moderators
    • staff
    • members
    • web users
    • cron users
  • account permissions
  • php mail() settings
  • database management
  • database archive management
  • system restore points
  • menu management
  • micro management
  • private message system
  • dynamic pages (wysiwyg)*
  • module management
  • license management
  • dynFields™ basic
    • add;
    • edit;
    • or remove custom database fields
  • bbclone (site statistics on steriods)
  • plus much much more...

* the number of pages are based on the package purchased...


The corporate blog is fully customisable from field displays to required fields in member registration (if enabled). Attach files, links, images (from the image gallery if module is purchased) or upload images direct from your computer.

Posts can be viewed per month and year using a calendar system that appears on the right hand side menu. The menu item can be moved up and down to your preference using the menu management (included with core module).

Other features include; auto adding rss feed entries into categories, manage categories, multiple system admins, moderators, staff and members can post on the blog (dependant on group permissions), add blogger and wordpress blogs, auto pruning, manage comments, auto pruning comments, registration, plus much more...


Upload photo's directly to your web site, categorise them, share them with co-workers, friends, business associates, pretty much anyone you want. Password protect categories, restrict access from certain administrative groups and or certain members. Import images straight from flickr, create rss feeds or a slideshow with a click of a button.

Using a javascript framework, images from your gallery can be loaded into the same browser window you are in without opening another window or annoying popups! You can customise the look and feel using cascading style sheets (css) to suit your web site or use one of the pre-built templates.

The Image Gallery supports *.jpg, *.gif, *.png and *.bmp images, you can set the default image size, thumbnail size, even add custom thumbnail sizes for render upon image upload. Enable the comment feature to allow comments to be posted on your images, also enable comment filtering and all new comments will be approved first before publishing... These and many great features are included with the Image Gallery...


The Shopping Cart module is currently in development.

Some of the base features include:

  • Custom fields per category
  • Invoice System
  • Full quote system
  • Purchase Orders
  • Cost Price Per Supplier
  • Bulk Price Options
  • Upload Photos to Products
  • Postage Costs Per Company e.g. Australia Post, StarTrack, DHL...
  • S.O.H. (stock on hand) management
  • Product Variation Management
  • PayPal intergration
  • Google Checkout intergration
  • Regions & Taxes system
  • Suppliers & Vendors system
  • Email & Notification system
  • Discount Coupon System
  • Discount % per qty amount
  • Softgoods, such as "online registration" or "file downloads"
  • + much much more...

The Newsletter module is currently in development.

More information coming very soon, we promise...


The Address Book module is currently in development.

More information coming very soon, we promise...


The SEO or Search Engine Optimisation module is currently in development.

More information coming very soon, we promise...


More information on all modules are available on request.


3.

apiOutput

how is it structured?

base dynFields™ api input example:

<api>
  <dynFields>
    <tableName>databaseTableName</tableName>
    <fieldName>databaseFieldName</fieldName>
    <parse>fieldValueToLookUp</parse>
    <debug>false</debug>
    <fields>
      <fieldName value="fieldName" return="fieldNameReturn" />
    </fields>
  </dynFields>
</api>

base dynFields™ xml output example:

<?xml version="1.0" encoding="utf-8"?>
<api>
  <output>
    <tableName>
      <fieldNameReturn> {database variable} </fieldNameReturn>
    </tableName>
  </output>
</api>

The above examples are based off using the dynFields™ 'xml' output function ($api->getXML). Other output formats include:

  • xml
  • rss
  • atom
  • array
  • flash formatted
  • + many more...

More indepth examples and instructions per module you must have access to our online developer kit, restricted to licensed clients only. To login to the developer kit click here.

 


4.

systemRequirements

what you need to run it...

Platforms:

  • linux
  • debian
  • ubuntu
  • unix
  • os x 10.4+

Software:

  • apache 1.3.x
  • php 4.3.x -> 4.4.x **
  • mySQL 4.x

PHP Modules:

  • cURL
  • domxml ( required for dynFields™ )
  • exif
  • ftp
  • gd
  • imap
  • mbstring
  • mcrypt
  • xmlrpc ***
  • zlib

Apache Modules:

  • mod_rewrite
  • mod_gzip

* note: all content management systems require a valid license key supplied upon registration and purchase of product via mavrick web design or one of it's resellers.

** fooBarCMS v2.x.x does NOT currently run on php5 servers, we anticipate v3.x.x will support php5. Apache 2 and php4 are compatible with fooBar CMS.

*** xmlrpc is used for such modules as the corporate blog and core systems when multiple domains run from one content management system to allow sychronisation and remote commands / pings to the fooBar CMS.

 


5.

sourceDeveloperKit

$sdk->customise($your['code']);

Why develop an API (Application Program Interface) you say?

We offer a full SDK (Source Developer Kit) so you can out source your own programmer to develop your own modules to use with our content management system.

Why allow this kind of freedom?

This kind of freedom does come at a price, a SDK License must be purchased in conjunction with your CMS License to recieve the SDK files. We have a full online help system from installation to configuration to the core system and per module configuration and how to "talk" across the core API then to each module.

I'm still lost, why an API again?

90% of our content management files come encrypted, a parser; ionCube is included with each build of the CMS. So we offer other means to talk to our API as the core code cannot be viewed...

Can mavrick web design develop custom modules?

We sure can, 70% of all CMS purchased from mavrick web design have had some form of customisation at the request of the client. Each custom module or modification to pre-built modules are billed ontop of the set price of the module.

 


6.

branding

make it look as if it where your own...

We know what's like to buy something and use it, only to let our clients know we didn't make it. Branding is the best way to get around this!

With our branding module available during purchase, you can fully customise the software name, add your own logos and change tool tips as you see fit to give it your own look and feel, css files will become editable and the ability to upload your own custom icons to replace the default ones will become available.

That's awesome you say? We know, however you must register as a reseller to be able to purchase this module.

 


design | content management | services | portfolio