We've been making use of the angular-gettext module to provide translation functionality on angular sites recently. It works quite nicely, giving a simple
<translate> directive which can be used in templates to indicate strings for translation.
- Big projects using grunt can end up with long and hard to read gruntfiles
- When working on multiple similar projects, grunt task config and alias tasks are often repeated
- How do we package these files to make them self-contained with dependencies and versioning?
- There's a bunch of contrib options with pros/cons, but in the end I went with a basic self-written grunt plugin using