# emberjs Published articles for emberjs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ember CLI Addon Docs: Shared Documentation for the Ember Ecosystem DevFeed: [Ember CLI Addon Docs: Shared Documentation for the Ember Ecosystem]() Original publisher: [Read original article]() Author: pzuraq Published: 2018-03-07T21:00:37Z Content type: article Language: en Sources: [Addepar]() Topics: [Ember](), [Documentation](), [code productivity](), [JavaScript]() Tags: [automated](), [developer-productivity](), [documentation](), [ember](), [ember-cli](), [emberjs](), [examples](), [experimental](), [full-text-search]() ### AI overview Addepar describes the development of ember-cli-addon-docs, a shared documentation solution for Ember addons. The project addresses limitations in existing tools by providing Ember-focused API documentation, Markdown templates, live demos, versioning, automated deployments, search, and pluggable API documentation generators. ### Source excerpt On our road to modern Ember here at Addepar, we've been hard at work developing a new component library to replace a lot of our older components, such as the now deprecated Ember Widgets library. As anyone who has built a shared toolset of components will know, one of the more tedious tasks faced by a library developer is documentation -- users of the new components need to be able to reference the APIs to know how to use them, and having a single source of truth for your docs is invaluable to developer productivity, but setting up docs in the first place is a lot of hard work! For Ember, part of the problem is that there is no standard documentation solution as of yet. The core Ember and Ember-CLI API docs use YUIDoc to generate docs automatically, but it is an aging library which doesn't have much support for modern javascript features. JSDoc is also falling behind the times lately, and newer doc tools like ESDoc and Documentation.js are still too experimental for widespread use. Moreover, none of these tools targets Ember -- they are meant for generic Javascript usage and don't highlight things that Ember devs need to know, like what arguments a component receives, what actions it sends, or what values it yields. Worse yet, none of these tools has support for live examples and demos. To get those, most addon authors resort to building an Ember app, usually using the test application (or Dummy app) included with the addon. Building an app takes time and effort, and in the end this means that very few addons in the ecosystem are fully documented with good examples and well described APIs. When we started to set up our documentation we ran into all of these issues, and we began wondering where the shared solution was for Ember documentation. As often happens in the Ember community, it turned out others had been wondering this as well! We joined forces with Sam Selikoff, Dan Freeman, and the Ember Learning team to work on ember-cli-addon-docs, a project whose goal is t ## ES Classes in Ember.js DevFeed: [ES Classes in Ember.js]() Original publisher: [Read original article]() Author: pzuraq Published: 2017-11-15T20:01:01Z Content type: tutorial Language: en Sources: [Addepar]() Topics: [Ember](), [JavaScript](), [Web Development]() Tags: [classes](), [code](), [ember](), [emberjs](), [es-classes](), [es2017](), [javascript](), [syntax]() ### AI overview This guide explains how ES classes, class fields, and decorators can be used with Ember.js. It describes the accepted ES Classes RFC, potential benefits such as improved tooling and clearer syntax, and caveats involving currently broken features and evolving JavaScript proposals. ### Source excerpt Classes have been an emerging standard in Javascript for some time now. With features like class fields, private methods and fields, and decorators on the way, pretty soon Javascript will have a fully featured class syntax with capabilities that haven't been available in the language before. While Ember.js has had its own, trusty, custom object-model in Ember.CoreObject since the very beginning, these broader advancements are going to be the future of the language and the web itself, so in time we will have to build out and replace the existing system with one based on ES2017+ classes. If you've been paying attention to Ember RFC process you may have noticed that an RFC for ES Classes was accepted recently. The RFC was very minor: it didn't propose any overhauls or breaking changes to the Ember object model as it stands. In fact, it was really just formalizing an existing oddity -- ES classes work with Ember as is, right now, as far back as Ember v1.11 (and possibly even farther). You can use them today, along with class fields and decorators, and get the benefits of modern JS syntax, including: Better tooling from editors like VS Code and Webstorm Better static analysis tools and documentation generators, like ES Doc Shared code and solutions with a wider ecosystem, including other decorator libraries such as core-decorators Shared knowledge with a wider ecosystem -- no more needing to teach the Ember object model to new developers, they just need to know Javascript and they're good to go A simpler, cleaner, declarative syntax that's easier to understand and makes your code more readable Of course, there are some caveats with switching to classes today. Certain Ember features are currently broken and being fixed as-per the RFC. Others, like class fields, have changed dramatically, and you'll likely need to update your mental model just a bit. This guide will lay out all you need to know about using classes in Ember today, including some new techniques that add additi