Integrate the "cards" with new content interface

[djplaner]

Using models and views.

• [x] document how contentWithCards is currently working (model and views)
• [ ] plan out integration with model/view
• [ ] implement

[djplaner]

how does contentWithCards work?

contentInterface method has a handleBlackboardCards method

• suggesting implementation could be all in the view
• or perhaps the model and view components should be separated at a higher level?

handleBlackboardCards

• has to organise collections of card elements into bunches

  i.e. there might be separate lists of cards through out a document, group them together

  • could be part of the contentInterface model. This is a very contentInterface thing to do
  • This could be a pre-cursor of the model identifying the various content elements and using that to figure out what views to call

• iterates through each bunch of cards calling createBunchesCards

  • hides the card elements and add the bbitems to a list
  • call extractCardsFromCotent on that bbItem list to get the models

    • this could be an in to the original card model
    • this approach could be used to allow the Card Interface to have separate elements where there's a bulleted list in content items for cards - matching the bulleted list in Word doc

  • call addCardInterface to generate HTML for those cards and place them

    • This is getting into view territory

  • add the event listeners for the cards

[djplaner]

How to implement

1. ciModel - looks for card lists/divs in the ContentInterface - does this create listOfCardBunches?? no
2. content.js - tests if there are any and creates a cardContentModel which accepts the card elemetns and geneats listOfCardBunches
3. content.js - creates a ciCardContentView responsible for replace card content
   1. content.js - creates a ciTweakView responsible for updating the tweak

There would (eventually) be some sort of inheritance relationship with the Card Interface views and models

Model

[djplaner]

Leaving this aside. Cards now in Content.js. Need to move to webpack or some related approach before going down this route.