ANanthonyjb·Oct 1, 2015
Thank you for the feedback. Right now all dependencies are included with the package in a folder called '/externals' and the build process concatenates them to the start of the final output file - which 'hands up' isn't ideal and moving towards correct node/npm support is a goal for the very near future.
To provide a very quick overview: ContentTools is a collection of libraries all written in CoffeeScript (this is up for debate https://github.com/GetmeUK/ContentTools/issues/10), the collection includes:
- FSM (https://github.com/GetmeUK/FSM) [no dependencies]
- HTMLString (https://github.com/GetmeUK/HTMLString) [depends on FSM]
- ContentSelect (https://github.com/GetmeUK/ContentSelect) [no dependencies]
- ContentEdit (https://github.com/GetmeUK/ContentEdit) [depends on HTMLString, ContentSelect]
- ContentEdit (https://github.com/GetmeUK/
Read the rest
ContentTools) [depends on ContentEdit]
For developers each library does have other grunt related dependencies which are required to transcompile the CoffeeScript and SASS as well as perform some base concatenation. Instructions on building/testing each library is provided on each of the GitHub pages.
Along with implementing better dependency support, for those looking to contribute:
- I still haven't added a release numbers to the builds yet (so that's first priority)
- I haven't posted any contributor guidelines as of yet.
Please bare with me, didn't expect the amount if interest so far (though that's been awesome), not released an open-source project before, still learning about git (everything was on Mercurial before release) and publishing packages using bower/npm.