We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

MiniTalk: The Learning Team

00:00

Formal Metadata

Title
MiniTalk: The Learning Team
Title of Series
Number of Parts
37
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
VideoconferencingCodeBit rateXML
Group actionAlgebraic closureCommon Language InfrastructureTask (computing)File viewerWeb pageElectronic program guideWhiteboardFermat's Last TheoremIntrusion detection systemFormal languageSource codeText editorContent (media)Lattice (order)TouchscreenState observerBlogPhysical lawVideoconferencingService (economics)Event horizonElectronic program guideFunctional (mathematics)Block (periodic table)Online helpModule (mathematics)TrailGroup actionVideoconferencingRight angleText editorStability theoryTemplate (C++)Projective planeRewritingWeb pageWebsiteTranslation (relic)File viewerCore dumpQuicksortVideo gameMereologySource codeAlgebraic closureForcing (mathematics)Revision controlSoftware developerState observerBuildingNumberFormal languageMathematical optimizationCASE <Informatik>Cartesian coordinate systemAnalogySatelliteSoftware maintenanceFamilyBlogForm (programming)Sheaf (mathematics)Plug-in (computing)Content (media)Common Language InfrastructureMultilaterationStack (abstract data type)TwitterFocus (optics)Mobile appRankingRoundness (object)Computer animation
Transcript: English(auto-generated)
have seen me around Slack, Stack Overflow, Twitter has logs, I also go by my human name, Ricardo,
and I'm part of the recently announced learning team, which is what I'm gonna be talking about today. So, the learning team mission is to improve the Ember.js experience, and what does this rather vague sentence mean?
It means that we want to improve both the life of Ember users, so guys, documentation, et cetera, as well as anyone that wants to contribute. And I'll explain how we're trying to do that.
Okay, but first, let's take a look back at the last year. The last year was an interesting year. We started improving the guides, and then a documentation team was informally formed, which then turned into the learning team.
We did a lot in the guides. We did the Ember CLI rewrites, I think, in 1.13, so it uses ES6 modules and all of that. We did a small rewrite when closure actions landed,
so all of the guides use closure actions, which are the way forward and the recommended way, and that's one of the goals of the guides, is to impart what are the optimal ways of building a Ember app, what we call the happy path.
There was also an Ember data rewrite of that section of the guides when the 1.13 stable Ember data got released. We did a redesign that was started long ago
by some friends at Thoughtbot. We also started having a tutorial, which isn't finished, but I'll get there, and we also added a quick start. I would like to give out a special thanks to Trek, who was the driving force
of all of the documentation and the guides, Michael, who was one of the first members along myself and Trek of the documentation team, but right now he isn't part of it, and to Brandon for his work on the Ember data rewrite
for the stable 1.13 release. Round of applause, please. Okay, so you've probably seen this blog post by Matthew, or Mcsonic, depends on how you know him,
about being the bark, and in this analogy, essentially, Ember is growing as a community. It has to cover more use cases. There's a lot of diversity in the people using it,
and what's important right now is the projects surrounding Ember, because we have a pretty stable core with a lot of functionality. The core team is continuing to improve the API, so you can release new features like Ember engines,
and Fastboot has add-ons, which is kind of impressive, and that also ties into the learning team philosophy. So we have a couple of projects in the works. We started translating the guides. We have a new welcome page for Ember CLI applications.
We're working on finally solving the SEO problem for the guides. We are very, very aware of the problem of Google ranking and we're still trying to solve it because it's not an easy topic.
We're also working on a living style guide. This is for the Ember resources themselves, like the Ember website, the guides, and like projects in the family, like Ember CLI, Ember Twiddle, and also eventually for Ember add-on developers
so they can have a template for documentation pages and et cetera. We also started working on dog-fooding Ember, which means that we're writing a guides
and an API viewer in Ember itself. We're like halfway maybe. We'll need help with that as well. I'm mostly focusing on the guides viewer and Stanley is focusing on the API viewer.
We're also gonna improve the builds page on the website to feature features status bar. So people will have an easier way to figure out which features are coming down the pipeline and what they can expect.
And then there's also a lot of community-related projects. So quickly about translations. For the first version, we decided that the core languages are gonna be English and that's the source language. Portuguese, because I'm Portuguese so I can help proofread and translate.
And then Japanese because there was a big Japanese group that came to us asking to help out with that. And then for the second version, we already have French and Spanish translators and you can suggest your language if you're interested. Okay, this is a screenshot of the new Ember welcome page.
You can find more about this later. This is also a project that I'm trying to organize. It's Ember Her. It's basically an Ember CLI GUI. So it makes it easier for new developers
to use Ember apps and to generate and maintain and et cetera. And so the community aspects, we're trying to bring more focus into satellite projects like Ember Observer, Ember Twiddle.
We're working on a way to survey the text editor plugins and improve the situation, try to help out the maintainers of the projects so everyone can have a nice editing experience. And then also try to curate and make it more discoverable, the community content.
So meetup videos, blog posts, books, screencasts, all that sort of thing. Okay, that's it. Thank you and we hope to hear from you.