General problem statements
Some content connectCenter presents can be overwhelming to non-technical people.
Some content connectCenter presents can be overwhelming to technical people new to connectCenter leading to a first impression of "overly complicated".
Some content connectCenter presents can be more than is necessary in various use cases.
Users and observers
connectCenter users sharing their screen
connectCenter users not sharing their screen
Non-technical people watching someone else sharing their connectCenter screen
Technical people new to connectCenter watching someone else sharing their connectCenter screen
Technical people familiar with connectCenter watching someone else sharing their connectCenter screen
High-level use cases
connectCenter / connectSpec demo
Various conversations with domain experts while screen sharing
connectCenter / connectSpec training
Developing promotional and education content
Browsing connectSpec or ADAPT Standard
CC model development
BIE development
Enhancement 1: Component browser
Effectively it would be the view and behavior you experience when doing BIE development but without the checkboxes or context-specific fields.
Dev mode
Option to turn on/off
Off by default
When on, CC editing is not possible
EU mode
Always on
Enhancement 2: Sibling sort order
Specific problem statement
connectSpec users can be overwhelmed by the number of child components a component may have. As connectSpec has grown over the years, components are seemingly in random order (e.g., XParty CC, followed by a bunch of non-party related components, followed by YParty).
Enhancement request
The current order is preserved for XML Schema production.
New components are always added as the last among siblings with respect to XML Schema production.
Devs can reorder siblings.
Note: The current component order only matters in the context of XML Schema production (as far as Jim knows).
Enhancement 3: Use "message profile"
Add "message profile" after "BIE" in the menu.
Enhancement 4: Show/hide rarely used components
Add a way to indicate that a component is rarely used in the context of a parent component.
Add a way to show/hide rarely-used components.
Enhancement 5: Reorganize search
Change search as follows:
Filter by ASCCP by default
Enhancement 6: Add simplified search-results view
Keep the existing view as an option
Add a simplified view that looks something like this:
