Ember Froala Editor Addon

Bring the Froala WYSIWYG Editor into an ember-cli project with this addon. Besides importing the required Froala Editor files, the main part of this addon is the {{froala-editor}} component. Checkout the documentation Website for installation, configuration, and usage details.

Compatibility

ember & ember-cli 2.15.0+

Installation

ember install ember-froala-editor

Configuration

Take a look at the configuration documentation page for details on the exact configuration options. But basically you add 'ember-froala-editor':{} within your ember-cli-build.js file and adjust the available configuration options. Ex:

// ember-cli-build.js
// ... (snip)

  'ember-froala-editor': {
    languages: ['es','fr','de'],
    plugins  : true,
    themes   : 'royal'
  },

// ... (snip)

Usage

Take a look at the documentation Website for full usage details. But basically this addon comes with a few Ember Components and Helpers to use within your project templates.

{{froala-editor}}
{{froala-content}}

(froala-method)
(merged-hash)

Test Helper

This addon also provides a convenient test helper to interact with the editor in acceptance tests. It functions similar to the ember provided fillIn() test helper. Take a look at the Testing page on the docs Website for more details.

fillInFroalaEditor('#my-editor', '<p>Foobar</p>');

License

The ember-froala-editor project is under MIT license. However,in order to use Froala WYSIWYG HTML Editor plugin you should purchase a license for it.

Froala Editor has 3 different licenses for commercial use. For details please see License Agreement.

Release Process

1. npm install froala-editor@x.y.z --save - Updates the editor dependency and lock-file to the specific version
2. npm version x.y.z - Updates the version in package.json and tags in git
3. git push origin master --follow-tags - Pushes any changes and the new version tag up to Github
4. Update the new tag on the Github Releases page
5. npm run deploy - Deploys the docs to gh-pages using ember-cli-github-pages
   • May need to git push, deploy will say if this is needed
6. git checkout master - Need to switch back to master after deploying the docs..
7. npm publish - Release the new version to the world!