Conceptual Model

Date: July 13, 2016

Location: Engineering Library, Room 329

Attendees:
Jon Gunderson, Nick Hoyt, Robert Slater, Mike Scott

Meeting Goals

Come up with feature documentation for three components – heading, list, and images.

CKEditor is oriented towards people who have some knowledge of HTML markup and how the editor wants something to look. OneNet takes the focus away from how things are going to look/markup, and focuses on semantics.

Conceptual Model defined: The main objects and actions, and their relationships in a system.

Main problem with the horizontal toolbar is limited real estate tends to lean towards graphical buttons without text/descriptions to lead people to the correct/best semantic choice.

Front load/emphasize all semantic-based choices in the editor.

Keep a format/formatting section (not sure what it should be called), but limit it to simple formatting (strong, emphasis, line break, etc). Also have a section (templates or special objects maybe) for advanced/custom objects.

Is it possible for us to present a vertical editing menu for the WYSIWYG, and if so, is it desirable (with regards to integration of the editor into CMSes like WP)?

Conceptual Model

Main Objects

  • Document (implicit)
  • Parent blocks of text
    • Heading
    • Paragraph
  • Children of parent blocks of text
    • Strong
    • Emphasis
    • Links
      • External
      • Internal
      • In page fragment identifiers
    • Templated objects (custom)
  • Compound blocks of text
    • Tables
    • Lists
    • Templated objects (custom)
  • Images/applets/objects

Main Actions

  • Typing text (primary action): inserts characters into some element
  • Hitting enter/return: inside a block, splits it; at the end of an element, closes block and opens new one
  • Selecting text/content
  • Insert (the structure for) a block of text of some type: paragraph, list, etc.
  • Change the type of an element (change of the block level element type, e.g. paragraph to heading)
  • Changing the format of selected content (inline change, within a block level)
  • Change the “table template” for presentation of a table/types of data tables
  • Change the heading formatting (at the overall page level, not the individual headings)

Functional Requirements

Date: July 19, 2016

Agenda: Lists, Links, Tables

Lists
  1. Provide an obvious means of formatting current blocks of text as lists/list items. Functionality: Provide a ‘list’ menu that is prominent/obvious that includes CSS standard style types (bullet styles, numbering, etc.)
    1. Also need to support list-style: none (could provide template for something like citations)