<![CDATA[Category: Community | Home Assistant]]> 2018-03-11T22:06:17+00:00 https://home-assistant.io/ Octopress <![CDATA[Disabling Disqus comments]]> 2018-02-09T01:00:00+00:00 https://home-assistant.io/blog/2018/02/09/disabling-disqus <![CDATA[Thank You]]> 2017-12-28T22:00:00+00:00 https://home-assistant.io/blog/2017/12/28/thank-you <![CDATA[Translating Home Assistant]]> 2017-11-06T01:00:00+00:00 https://home-assistant.io/blog/2017/11/05/frontend-translations The Home Assistant sidebar in 12 different languages The Home Assistant sidebar in 12 different languages.

## Translations As mentioned in the [0.57 release notes](https://home-assistant.io/blog/2017/11/04/release-57/), Home Assistant has launched a translated frontend. With the immediate influx of translations, we’ve made integration with a translation tool a top priority. [@c727] took the initiative to evaluate several tools, and we’re happy to announce that Home Assistant will be partnering with [Lokalise](https://lokalise.co/) to manage our translations! Lokalise allows us to open up translations for all of our multilingual users willing to contribute. Users can join the project using our [public signup link](https://lokalise.co/signup/3420425759f6d6d241f598.13594006/all/), and start translating right away. We’ve created a [translation startup guide](https://home-assistant.io/developers/frontend_translation/) with additional details about how to contribute. Instructions are provided there for how to request a new language. Now that we have a system in place, expect a lot more of the interface to be translatable soon. We still have some technical hurdles to overcome, but the hardest work is behind us now. The community has already done an outstanding job of providing translations. The future is looking bright! [@c727]: https://github.com/c727 ]]> <![CDATA[Templates, dates and times]]> 2017-10-15T06:00:00+00:00 https://home-assistant.io/blog/2017/10/15/templating-date-time We want it simpler, right? [Templating](/docs/configuration/templating/) offers `now()` and `utcnow()`. We will stick with `now()` in this blog post but it applies to `utcnow()` as well. Our documentation said:
`now()` will be rendered as current time in your time zone.
Hmmm, ...OK, that's a start. How to get the year? `{{ now() }}` gives you `2017-10-14 20:27:23.700401+02:00` which is far more than we are looking for. As an user you don't want to dive into the code but there would you find the solution. You will get a [Python `datetime` object](https://docs.python.org/3.6/library/datetime.html#datetime.datetime) from `{{ now() }}`. This means that you can access more than you think in a template: - For the time: `now().microsecond`, `now().second`, `now().minute` and `now().hour` - For the date: `now().day`, `now().month` and `now().year` - Misc: `now().weekday()` and `now().isoweekday()` For the year it would be: `{{ now().year }}`. I guess that there are rare use cases for `now().resolution`, `now().min` and `now().max` too. [Hacktoberfest](/blog/2017/09/29/hacktoberfest/) is still running. Working on the documentation is pretty easy. If you know a nice [trick](/cookbook/), want to help improving the page of a platform or just fix typo then please do. Our [Website/Documentation section](/developers/documentation/) contains some requirements which are defined in the [Documentation Standards](/developers/documentation/standards/) and the "[Create a page](/developers/documentation/create_page/)" documentation for other useful details. Thanks to [Egor Tsinko](https://github.com/etsinko) for bringing this issue to our attention. ]]> <![CDATA[Participating in Hacktoberfest]]> 2017-09-29T08:00:00+00:00 https://home-assistant.io/blog/2017/09/29/hacktoberfest