-
-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quest: Octane Guides MVP Tracking issue #394
Comments
The content sections mentions |
@rtablada the plan is long term to break out the tutorials into a separate repo/app, but we need to focus on content first, and then infra after the first Octane release. |
It may be good to review what content needs to change regarding the |
Just to gently remind all of us, this is just supposed to be a minimum viable product. |
Hello @MelSumner! Do we still have some parts of the guides to migrate to the new syntax? From my understanding, everything has been migrated. If not, I can tackle some of the remaining bits. And, by the way, is there a way to see this new Guides MVP formatted somewhere? My question is a bit off-topic, but I have two newcomers arriving next week and I'd love them to start discovering Ember with the new syntax from day one! 😉 |
do some of these checkboxes need updating? |
I checked them all, mwahahaha. Thanks everyone for your help! As of EmberConf 2019, we reached MVP for the Octane Guides 🎉 Anyone who wants to see the outcomes can visit https://emberjs.com/editions/octane for the preview guides. Octane isn't in a stable release of Ember - this is a preview - but we are in really good shape for when it's time to ship. |
Hello and thanks so much for helping out with the Octane Guides! Even if you don't know much about Octane or Native Classes, there's something you can help with! Here's everything you need to know to pitch in.
The "new volunteers needed" links below that are the things we need help with more than anything else. We are aiming to finish a rough draft of the Guides by March 15th. If you volunteer for an issue, please only do so if you can have a PR with at least part of the work ready the following evening after you claim the issue. To volunteer, comment in the linked issue (not here) to say that you can help. You should
git branch
from the octane branch of the Guides, do work in the markdown files in theguides/release
directory, and when you open a PR, make it go theoctane
branch. If you want to learn the basics of what's different in Octane, have a read through this draft guide.New volunteers needed:
Please check the comments on issues to see if they are already claimed. Are they all taken? Pick a different section of the guides, copy and paste the contents of one of the "JavaScript Code Blocks to use Class Syntax" issues for a section that's not in this list, open an issue, and put at the top that you're helping with it! You can grab just one page, or a whole section. It's up to you!
High level tracking, in progress:
This section is purely for tracking how much work we still have left to do, in a very broad sense.
Content Sections:
The text was updated successfully, but these errors were encountered: