3 . DIMS Modules

A description of the item.

Text

Module description.

List

Cedit

Cedit consist of two parts

  • Cedit elements toolbar

  • Cedit styles toolbar

Cedit is the main website editing environment for website editor (webmaster, copywriter, etc.) In Cedit, content of a single item is edited(article, blogpost, product, event…)

In its substance, it could be said that Cedit is an HTML editor. However, there are some specifics that distinguish it from other solutions.

In Cedit, user has no control over the visual aspects of content edited. All visuals are already defined by Designer, while building a website/app in the Creator. Main reason for such a limitation is ensuring that a website/app is visually consistent, and that designed look and feel of a website/app is protected from possible visual mishap or misuse.

Set of available elements and/or styles for editor of the website/app is defined also by designer, so that users can work with elements that website/app requires. This ensures simplicity of UI that editor needs in order to easily complete tasks that are needed, and at the same time it ensures flexibility to satisfy complex needs of the various business models.

What else?

Elements and Styles

Theoretically any element from Creator Panel can be inserted into Cedit Toolbar or Cedit Styles. Components can be only inserted into Cedit Toolbar.

It should be clear, that same element would behave differently in these cases.

When element is used as Cedit Toolbar element, it is used as a block level element.

Purpose of the Cedit Elements is creating main content of the page.

That same element may be used from Cedit Styles Toolbar, but in this case, element, or set of characters needs to be selected before Style can be applied, and the chosen style will be applied only to that selection. In other words, it is used as inline level element, meaning that it is inline child of already existing Cedit Element.

Purpose of the Cedit Styles is adding additional styling (bold, italic, …) and adding additional interactivity to the content of the page (creating links inside of paragraphs, etc.).

Image & Assets

Module description. O boy! Files, different types (audio, video, images, fonts, documents, CSS ... ), managing, adding, deleting, structuring, Type specific stuff (image sizes, ... ) Imported assets (fonts, css, js, ... )

  1. Core Concepts
    1. Structured Data, MicroData, Schema.org
    2. GraphDB & Dynamic Content
    3. Html Renders (VPTL Model)
    4. Semantic HTML  (Document Semantics)
    5. CSS & Preprocessors
    6. External CSS & JS Libraries
    7. Integrated CMS
    8. Momentum Network and Market
  2. Environment
    1. Viewport
    2. Project Settings
    3. Tools Panel
    4. Code Editor & External Libraries
    5. Visual Helpers
    6. Web Parser
    7. Structure Panel
    8. Render Panel
    9. Stylebook
    10. Assets
  3. HTML
    1. Layout Structure (Master Template)
    2. Basic HTML Building
    3. Parsing Pre-made HTML
    4. Working With Snippets
    5. HTML In Dynamic Collection
    6. Hidden HTML Elements
    7. Forms
    8. Container Lock
  4. Website Structure
    1. Blank Pages
    2. Schema.org Classes
    3. Collections
    4. Collection Properties
    5. DIMS Module Settings
    6. Stylebook (vptli)
    7. Using Render Panel
    8. Index Operations
    9. Relations Between Collections
    10. Taxonomies
  5. Schema.org, Advanced
    1. Independent vs Context
    2. Testing Schema
    3. Knowing When To Stop
  6. Classes & Attributes, Advanced
    1. Auto Generated Classes
    2. Dynamic Attributes
  7. DIMS (CMS)
    1. Overview
    2. DIMS Interfaces
    3. DIMS Modules
    4. Publishing Content
  8. Building Editing Flow
    1. Inbound & Outbound Relations
    2. Using Dims Attributes
  9. Going Live
    1. Connect An External Domain Name