Epic: Move Kit Framework to Portfolio
To put the full depth of my work on this lisp framework into view in this portfolio, I want to move the code I wrote in all of the kit framework into this portfolio. This way it is easier for future employers to see exactly how much work went into making this entire framework function the way it does. The work meant for Remove duplicate code included in headers. and Cull duplicate macros will be tracked in this issue. May as well call it an Epic, it could be a lot of work to move everything into here.
Cull duplicate macros, I have implemented many macros that share the same name, causing issues at runtime. For instance, the remember macro was implemented differently, which broke my code in some cases.
This issue is related to kanban/tasks/Move all outside work into the portfolio git and Remove duplicate code included in headers., and may be marked as #duplicate or possibly #rejected in favor of another task.
The dev code that watches, compiles, bundles, and serves the website would have a difficult time accessing the code that is in the #shared and #client modules, as browserify currently does some extra work parsing a namespacing system ie "@shared/data-structures/lists.js" refers to the code in list.js and everything in that folder uses that "@shared" prefix.