v0.9

New structure:

• hive-server
  • extensible collab server
  • extensions: auth + document types (including importexport plugins)
    • -- would you ever want to have a doc type and not the accompanying importexport options? They should be merged. Node dependencies, if not too esctensive, should be auto-installed, external deps should be opt in.
    • on the other hand maybe importexport plugins should be entirely client-side?
• hive
  • extensible client-side js library
  • extensions: editors + extensions
  • contains:
    • not auth -> app specific
    • not editor selection and setup
  • notes:
    • where do Editors' meat js files and config go / come from?
    • where do translations go / come from? (Possible solution: https://github.com/jshcrowthe/wc-i18n/pull/6)
    • where do preferences go / come from?
      • custom adapter that host app has to inject?
      • needed at all? what is a preference and doesn't lie in honey land?
        • user/chat.windowSize: honey (hive extension gets an attribute, if at all)
        • {user,document}/editor.editor: honey
        • author color: is not a setting (preferences are private!)
        • document/myDocuments.publicAccess: honey
    • expose the architect hub, components must expose the DOM elements that they render into -> better yet: WebComponents!
• hive-honey
  • hive module that implements a standard client website
  • contains
    • the http routes
    • the build mechanism for creating index.html, build.js and build.css
    • client-side router and route listeners
    • client-side auth system and mechanisms
    • client-side preferences renderer
  • notes:
    • perhaps this should be a totally separate node.js process?