The bulk of this PR is setting up the gem to be developed in the normal way that you build an engine. I wrote up a little development paragraph in the README.
There is now a test Rails app at spec/dummy that is configured to load the gem code.
Any view that we want to override we just have to build in our app/views folder of the gem.
I haven't specifically tested adding our own assets but that may be overriding the blazer assets or perhaps creating a new layout which includes a new css file that we write.
Close #4.
The bulk of this PR is setting up the gem to be developed in the normal way that you build an engine. I wrote up a little development paragraph in the README.
There is now a test Rails app at
spec/dummythat is configured to load the gem code.Any view that we want to override we just have to build in our
app/viewsfolder of the gem.I haven't specifically tested adding our own assets but that may be overriding the blazer assets or perhaps creating a new layout which includes a new css file that we write.