structure the repo

[pietroppeter]

• how do we handle requirements and stuff
• improve on readme
• add gitignore
• add a CI with deploy preview

[pietroppeter]

from discussion in nimib speaking hours:

• minimal dependencies in main nimble file
• inside source we have folder and each one of them is a separate package with its own nimble file
  • advantage is that locally you can treat it as a single package
  • also we manage to have a single netlify preview
  • you cannot install it from nimble
• later when a package grows it can be pinned out of nimibex
• we provide a binary nimiblex that allows you to install the single package (with its own dependencies)

structure:

• first extensions to try: nbPython, Karax_widgets
• we could try to do srcDir = "."
• we provide binary to install single package: nimiblex install nbpython

[HugoGranstrom]

An alternative to rolling our own nimiblex could be to put our hopes on the new package-thingy Atlas to support monorepos. I remember araq and mratsim discussing it in the internals chat a while ago but it isn't currently implemented.

[pietroppeter]

as additional food for thought, a possible setup would be allow an easy way to copy and paste in a project selected modules, instead of adding this as a dependency. This is inspired by https://bvisness.me/microlibraries/ (I would expect most of the content here to be rather shallow in code complexity).