---

By default, backup files are ignored and node turned into a node. With this change, we can ignore those backup files. There is a default list and this is user configurable.

---

This new plugin allow to combine multiple files into one. Here is an
example:

```
---
combine:
    files: luffy.*.js
    where: top
---

luffy.effects();
luffy.search();
```

All luffy.*.js files will be combined and added to the top of the file.

---

Various fixes to ensure that tests run. They now pass cleanly on my system.

BeautifulSoup is not compatible with HTML 5 and may mangle your
document. We provide a simple parser that should work in most cases.

This plugin adds `width` and `height` tags to `img` when they are not
present. It also adds them when only one of them is present
(respecting proportions).

Grab creation and modification date from git repository. To use this
plugin, `created` and `modified` meta data should be set to `git`.
They will be replaced by the proper date.

A new keyword `remove` allows to not deploy resources that have been
combined. Small rework on how the plugin work to remove one change
from hyde generator about dependencies handling.

This new plugin allow to combine multiple files into one. Here is an
example:

```
---
combine:
    files: luffy.*.js
    where: top
---

luffy.effects();
luffy.search();
```

All luffy.*.js files will be combined and added to the top of the file.

Always first sort by name then by any attributes you want. Otherwise,
tests may fail.

Use strftime instead. There seems to be no dateformat filter in jinja
documentation.

Node.js tools may be installed in /usr/bin if installed by system
package tools or in ~/bin if installed by a default installation of npm.

When the last plugin of a chain was returning None, the whole chain
return None instead of the last non-None result. For example, chain
LessPlugin with UglifyPlugin and you get all your .less files
unprocessed.

By default, backup files are ignored and node turned into a node.

This plugin allows to link pages that are translated to another
language. Each resource should have a `language` meta attribute and a
`uuid` meta attribute. Resource that have those two meta attributes
will get a new attribute with the list of other resources in a
different language that have the same `uuid` meta attribute.

It is then possible to use something like this to grab the list of
available languages for a given resource:

{% if resource.translations is defined %}
<p>Other languages</p>
<ul>
  {% for translation in resource.translations %}
    <li><a href="{{ translation.full_url }}">
       {{ languages[translation.meta.language] }}
        </a></li>
  {% endfor %}
</ul>
{% endif %}

(You need a `languages` context in `site.yaml` for this snippet to work:
    context:
      data:
        languages:
          fr: Français
          en: English
)