Getting started with AkashaCMS

Getting started with AkashaCMS

Initializing an AkashaCMS project

Project configuration

AkashaRender Projects, and using package.json to describe the build process

AkashaCMS project directories

Structure of the Rendered Output Directory

Content files

Templates, Partials, Page Layout, and server-side DOM Manipulation

Theming and CSS/JavaScript frameworks

Using plugins in AkashaCMS projects

Using GitHub submodules to collect static website content from multiple Git repositories

AkashaCMS is a family of tools for converting ideas into websites or EPUB3 eBooks while maintaining separation between content, layout and design. At the core is AkashaRender, the rendering engine, and Mahabhuta, a semi-independent module for server-side DOM processing using a jQuery-like API.

An AkashaCMS Project is comprises an AkashaCMS Configuration object, any required AkashaCMS plugins, and files related to the project. The configuration object is usually initialized in a JavaScript file named config.js. The types of files include assets, the static files that are simply copied into the project output, layouts and partials, two kinds of templates, and documents, or the content files. The purpose is to convert these files into an HTML or XHTML rendered output which may be a website, or an EPUB e-Book.

Since AkashaCMS is a Node.js based tool, the most natural way to manage an AkashaCMS project is using Node.js tools. This means using a package.json file to list dependencies on other Node.js modules, and to record a set of scripts with which to build and deploy the project.

( comments powered by Disqus


( Follow Node.js Web Development on Facebook