Closed KidkArolis closed 10 years ago
One of the reasons it's not documented is that I'm not confident that the current implementation is the best way. I guess it's good enough for now? If anyone has opinion, please speak up. :)
My current feelings about docs is that we need an overall explanation about how users should extend and customize a rave-based application. overrides
would fit into that nicely.
On the other hand, there's no need to hold you up. It'll be easy to refactor the docs when I get around to writing the overall explanation.
tl;dr docs/overrides.md
is fine for now.
Added as of 0.3.0.
In the top level package.json/bower.json:
I could write this up, but what would be the best place for it?
README.md
docs/overrides.md
docs/rave.md