Marco Biedermann

A nice addition would be to have a small button in the markup section which copies the code to the clipboard. [clipboard.js](https://github.com/zenorocha/clipboard.js) is super light weight and is pretty easy...

It would be a super useful addition to add a syntax highlighter to the markup panel. This way, it is easier to read it. [highlight.js](https://github.com/isagalaev/highlight.js/) is really robust and works...

Use CSS Classes instead of IDs

1

I suggest using classes instead of ids because of it's specificity.

Could you submit your plugin to [Bower.io](http://bower.io/). The benefit would be that you could add `jQuery` and `normalize.css` as a dependency.

How about renaming all animation classes to be compatible with [animate.css](https://github.com/daneden/animate.css). This way, it would be way easier to add new animations

It would be great if there would be an option to support the plugin if source and destination are the same folders. My idea is to create a hash database...

* Wrap navigation into `` tag * Only render class attribute if set * Only render target attribute if set

Library Name

4

Is this library called `voxel` or `voxel.css`. Either way, we should use one of both names. https://github.com/HunterLarco/voxel.css/tree/master/dist https://github.com/HunterLarco/voxel.css/tree/master/Server/voxelcss Which one do you prefer? ``` voxel.css voxel.js ``` or ``` voxel.css.css...

Prefix CSS Classes

2

I suggest prefixing all CSS classes with "voxel-" to avoid any collision. `.scene` should be `.voxel-scene`. If you agree, I could send you a PR :)

It would be great if you could your lib to the bower package repository