We welcome and truly appreciate contribution in all forms - issues, pull requests, questions, or fancy examples of apps/elements build on to of your elements.
Our team heavily uses Github for all of our software management. We use Github issues to track all bugs and features.
If you find an issue, please do file it on the repository.
We love examples for addressing issues - issues with a Plunkr, jsFiddle, or jsBin will be much easier for us to work on quickly. You can start with this jsbin which sets up the basics to demonstrate a Juicy element.
Occasionally we'll close issues if they appear stale or are too vague - please don't take this personally! Please feel free to re-open issues we've closed if there's something we've missed and they still need to be addressed.
If you would like to start to fiddle with element's code, here is the flow we use.
- Make a local clone of this repo:
git clone [email protected]:Juicy/juicy-iframe.git
In order to develop it locally we suggest to use polyserve tool to handle bower paths gently.
- Go to the repo's directory:
cd juicy-iframe - Install bower & polyserve:
$ npm install -g bower polyserve - Install local dependencies:
$ bower install - Start development server
$ polyserve -p 8000 - Open the demo/preview: http://localhost:8000/components/juicy-iframe/
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature - Commit your changes:
git commit -m 'Add some feature' - Push to the branch:
git push origin my-new-feature - Open corresponding issue if needed
- Submit a pull request :D