For non-developers

The purpose of N2 is to make it easier to develop great web sites. N2 builds upon standard techniques in ASP.NET 2.0 and concepts such as object oriented programming which should make it a piece of cake for any skilled developer to work with.

Scope 

The scope is to  provide a developer friendly content management engine paired with an editor interface easy enough for non-technical people (some office skills are required).

CMS features 

Of course N2 comes with all the features you might expect from a web based CMS: 

  • Organize of pages in a hierarchical structure.
  • Web based edit interface (internet explorer or mozilla required)
  • Create, read, update and delete pages stored in a database.
  • Copy, move, sort and search pages.
  • Separation between text (content) from templates (HTML).
  • View and rewind to earlier versions of a page.
  • Organize, delete and link to uploaded documents and folders.
  • Word-like input of formatted text/content.
  • Role based access control to edit interface and to branches of the pages within the site. A very simple user manager is also included.

Development process 

However it's not a ready-to-use solution. What needs to be done in order to get a site up and running with N2 is probably something along these lines:

  • Figure out what kinds of information you'd like to manage with the CMS (text, news, products, banners, contact forms, etc)
  • Start programming a model that matches those kinds of information and define what input fields are required for each page or page part. An input field might bee a WYSIWYG text input, a drop down list with predefined values or a link to an uploaded document or page within the site.
  • Development of page templates and page parts. This involves creating the graphical interface for the people who come and visit the site and the development of any functionality that guests can interact with such as shopping baskets or functionality to add comments.
  • Installation on a web server that might be a web hosting provider or hardware you own yourself.
  • Input of content and organization of the page structure (site map).