Kotsu
Kotsu copied to clipboard
:sparkles: Clean, opinionated foundation for new projects — to boldly go where no man has gone before
There seems to be very few suitable solutions for extraction of gettext strings into `.pot` file, which then could be used for translation into different locales, and all of them...
We need to have way to work with i18n databases too. Resource for some thoughts: https://github.com/TAPevents/tap-i18n-db
It is possible to generate proper font-face based on provided fonts in `source.fonts`. Each font probably have to carry with it json or yaml file with it's properties which Grunt...
Add i18n support - [x] Nunjucks - [ ] Scripts - [ ] Styles - [ ] Data - [ ] Images
We need to update our [Werker CD guide](https://github.com/LotusTM/Kotsu/wiki/Continuous-Delivery-with-Wercker-Docker-and-CoreOS) - Update with latest configs - Make similar guide for CircleCI - Add information about Travis, David and Slack integrations setup (?)...
Current `Nav` component doesn't work well because of issues, introduced in Nunjucks 3.0.0: * https://github.com/mozilla/nunjucks/issues/912 * https://github.com/mozilla/nunjucks/issues/906 So far the only way is to pass parameters of `Nav` to each...
[Nav component](https://github.com/LotusTM/Kotsu/blob/master/source/templates/_components/_Nav.nj) worked quite well, untill we've hit needs to accomplish following things: - Display items only from specified route - Check, does Nav actually returns anything. Especially actual when...
Currently Kotsu tries to render and template (with sprintf) everything you pass to main `config()` of base template. It also forces rendering of everything that goes throw `getPage()` global function,...
Hello lovely humans, [grunt-nunjucks-2-html](https://www.npmjs.com/package/grunt-nunjucks-2-html) just published its new version 3.0.0. State Update :rocket: Dependency grunt-nunjucks-2-html New version 3.0.0 Type dependency This version is **not covered** by your **current version range**....
`grunt-webfont` started to screw some icons during font generation, though, strangely, not all of them. See https://github.com/sapegin/grunt-webfont/issues/321 for details.