Title: Message Title
|
|
|
|
|
I was thinking the cleanest/neatest approach to this would be for it to live in dspace-xmlui/src/main/webapps/themes/mirage2, where all of the other themes live. Instead of DSpace/maven managing all of the dependencies for this theme (bower/sass/etc), it becomes the end-developer to have all of that on their machine. Also, I can see the source and compiled version of this theme living together. i.e. Have mirage2/scripts/(file1.scss, file2.scss, file3.scss) all get compiled to mirage2/scripts/_styles.css, and you version control all of them. With your compiled version of mirage2 living in dspace-xmlui/src/main/webapps/themes/mirage2, the existing deploy process will continue to work fine.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
