How it works

Many of the packages have been built with a “source” included mindset, it is rare that one of these packages are published to a package manager and requires installation. Many times this leads to obscurity and that annoying feeling of “I wish it would just do X”. Since you’ll be pulling the source directly into your projects you can do whatever you want to it. Customise it to fit your project UI, modify some of the functionality, extend it, break it, fix it, you do what is best.

There is only 1 real architectual decision that has been made. Artisan Stack has been built with Module Driven Development in mind. Meaning for the most part you can easily drop one of these packages into the specified modules directory and everything will just work. If you work in a different project structure, place it where you see fit and update any import paths as needed.

By default packages will go at the root of the modules directory or in a utility directory. In the documentation for each package it will specify the destination.

• Directorymodules

  • cartographer
  • sifter
  • toolbelt
  • Directoryutility

    • result
    • tracer