Introduction
Structured Content Editing module for DNN (Dotnetnuke)
Goals of Open Content
- HTML module replacement for responsive websites
- Easy content editing of complex layouts by end users
- Content editing for websites using frameworks like bootstrap
- Not for large amount of data (like articles or catalogs)
Features of Open Content
- Structured content editing of complex data (from single item to multiple lists)
- Template based rendering
- Multi language Static localization of content editing UI
- Template exchange with data definition and templates
- Module title editing from the Content editing UI
- Online template editing
Open Content Architecture
- Content & Template settings Schema definition in standard json schema format
- Content & Template settings UI definition in json format
- Alpaca Form Engine for Content & Settings Form generation http://www.alpacajs.org
- Client side form generation connected thru webapi
- Razor or Handlebars as Template engine for server side rendering
- File based schema, UI & templates
- Data stored in db in json format (as a single complex data element)
Supported field types
- Text
- Drop-down & Radio buttons
- Check-boxes
- Url (with auto complete search in dnn pages)
- Image (with instant upload and auto complete image search in specified folder)
- Textarea
- Rich text (Simple CKEditor http://ckeditor.com/ or wyzightml http://wysihtml.com)
- List of items
- Table of items
- Mix of multiple single fields and list of items (stored as a single item, not for large amout of data)
- Dependency between fields
Updated less than a minute ago