<commit_before>---
layout: page
title: Community Versioning for Ember Content
---

Web content never expires. A blog post written in 2011 will live on in search
engine results for years.

[Ember.js](http://emberjs.com/), the JavaScript framework for ambitious apps, has already been
around for several years. This means the Internet is littered with content
and posts that were accurate at the time, but have since been obsoleted.

To ensure old content gets properly flagged, with no effort needed by the
author, we've created a GitHub-driven badge service.

<iframe width="178px" height="20px" style="border:0px" src="/ember-community-versions/2015/05/13/previewing-ember-2-0-on-canary.html"></iframe>

Posts with this badge should work (without deprecation) when using an appropriate
version of Ember.

If you see an inaccurate badge, please help us by
[opening a pull request](https://github.com/mixonic/ember-community-versions)
to change the version number. All entries are made as blog post files for
Jekyll, and should include the URL of the original entry. For example:

{% highlight yaml %}
layout: post
url: http://madhatted.com/2015/5/14/ember-js-2-0-preview-with-canary
title: "Previewing Ember 2.0 on Canary"
date: 2015-05-13
start_version: 1.13
end_version: 2.0 # end_version is optional
{% endhighlight %}

Please help ensure your own blog posts are correctly flagged by add a badge
upon publication, even if you only provide a starting version. See
[mixonic/ember-community-versions](https://github.com/mixonic/ember-community-versions)
for more information.
<commit_msg>Fix height on demo iframe<commit_after>---
layout: page
title: Community Versioning for Ember Content
---

Web content never expires. A blog post written in 2011 will live on in search
engine results for years.

[Ember.js](http://emberjs.com/), the JavaScript framework for ambitious apps, has already been
around for several years. This means the Internet is littered with content
and posts that were accurate at the time, but have since been obsoleted.

To ensure old content gets properly flagged, with no effort needed by the
author, we've created a GitHub-driven badge service.

<iframe width="178" height="24" style="border:0px" src="/ember-community-versions/2015/05/13/previewing-ember-2-0-on-canary.html"></iframe>

Posts with this badge should work (without deprecation) when using an appropriate
version of Ember.

If you see an inaccurate badge, please help us by
[opening a pull request](https://github.com/mixonic/ember-community-versions)
to change the version number. All entries are made as blog post files for
Jekyll, and should include the URL of the original entry. For example:

{% highlight yaml %}
layout: post
url: http://madhatted.com/2015/5/14/ember-js-2-0-preview-with-canary
title: "Previewing Ember 2.0 on Canary"
date: 2015-05-13
start_version: 1.13
end_version: 2.0 # end_version is optional
{% endhighlight %}

Please help ensure your own blog posts are correctly flagged by add a badge
upon publication, even if you only provide a starting version. See
[mixonic/ember-community-versions](https://github.com/mixonic/ember-community-versions)
for more information.

{'fraction_non_alphanumeric': 0.08668341708542714, 'fraction_numerical': 0.02763819095477387, 'mean_word_length': 4.657193605683837, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1928111', 'n_tokens_mistral': 981, 'n_tokens_neox': 877, 'n_words': 392}