demo maker component

[serapath]

@todo

• implement first iteration of component
  • create repository
  • set up local dev environment with pnpm
    • pnpm link the modules locally
      • pnpm link --global (to make them available)
      • pnpm link --global <./package.json#name>
  • @output ❓ repository
• refactor component latest commit with new comm protocol and tag with v0.0.1.-alpha
  • @input ❓ repository
  • refactor latest commit with latest terminal/log to use versions
  • refactor communication protocol to use latest message standard
  • move terminal/logs to dev dependencies
  • rebase main branch on top of taged version
  • update package.json (new path for the dependencies)
  • update github page links
  • build new bundle.js to include changes in demo page
• implement next component version v0.0.2-alpha
  • @input ❓ repository#v0.0.1.-alpha
  • fix bugs & add features for v0.0.2- [ ] support single select (Support a filter for search swarm key and terminal messages using)
    • make new demo-maker component
      • text box with title, description and execute button
      • container element with the ui component you are demoing
    • Refactor codes(protocol, receive, recipients)
    • refactor all messages and status and update documentation
  • set up github page using demo maker component dev dependency
  • document component api in readme or whatever needs to show in the readme
    • document apis for each screen and return available actions
      • @input ❓ wireframes action bars
  • document component api in readme
    • list all opts
    • list all roles
    • list all incoming message types
    • list all outgoing message types
    • list all possible status the component instance can be in
• install latest dev dependencies
  • budo
  • browserify
  • datdot-terminal
• install latest specific version of dependencies
  • ...
• update github page links
• build new bundle.js to include changes in demo page
• update package.json (new path for the dependencies)

---

@info

the idea is a helper component for demo pages so it shows a component instance and a text field with a code snippet which is used to generate the component instance. A user can now tweak the code snippet based on the component api documentation in the readme and see how it changes the component instance.

Additional features could be to allow the component to be themed and to display multiple instances of the component each with modified code snippet to pass for example different arguments.