See https://developer.microsoft.com/en-us/microsoft-edge/platform/status/beacon/ on the right.

cc @MelSumner

The current builds page only really mentions Ember.js, but the Ember project now consists of at least three components: Ember.js, Ember Data and Ember CLI. The landing page's copy should be updated to include the following information:

1. Ember JS/CLI/Data are on a shared six-week release cycle
2. They have the same major/minor version number (but can have different patch versions)
3. (maybe) the best way to get the latest everything is to use the blueprints shipped with Ember CLI (i.e. just run ember new)

Goal

The goal of this issue is to recreate the page https://emberjs.com/learn/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /learn
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

See @mixonic's graph in Announcing Ember's First LTS.
Node's LTS schedule also has a similar graph.

Using d3 possibly? Should be self-updating with manual overrides. This could be developed as a tidy lil' component so we don't bikeshed about where it should go.

At the moment, various core and non-core teams have recurring weekly meetings.
It is hard to keep track of this, so having this information consolidated in a single page would be a boon.

Tasks

• Gather time, day of the week, and whether the meeting is generally open to the public or not
• List it on the teams page
• Make a nice calendar visualization

We received the feedback that it was hard to find the unadorned versions of the masccots in the website.
Following #17, an unadorned Tomster and Zoey pair should be added to the top of the page, below the "Tomster and Zoey" header.

Goal

The goal of this issue is to recreate the page https://emberjs.com/tomster/commisson in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /mascots/commission
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)
• make sure that you also implement the "commission sent" page from the old website that is intended to display once the form has been submitted. This doesn't necessarily have to be a route but you can do it that way if you like 👍 (if you don't then delete the this.route('commission-sent'); route)

Additional Info

• When you submit a PR for this issue, please reference the issue so others can see that there is an existing PR.
• If you submit a PR for this issue, please let us know in the dev-ember-learning channel with a message to the @core-learning team.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

We'd like to add a new feature to the website that showcases 3-4 projects using Ember. We intend to cycle these on a regular basis.

• add showcase as a child route to community
• each showcase should then also have it's own child route (https://guides.emberjs.com/release/routing/redirection/#toc_child-routes)
• use json api to structure the data for the showcase- it should support a thumbnail, a link, a title, a description, and a date added.
• front-end presentation should be an unordered list in the HTML (for accessibility purposes)
• CSS styling should be written in a mobile-first way
• a screenshot should be included in your PR

Questions? Visit the dev-ember-learning channel in Ember Discord chat.

This issue is to track work that is related to creating a "Why Ember" page for the new Ember Website. This is separate from the work that is happening in the Ember Website Redesign RFC

Motivation

It can sometimes be difficult to communicate why someone might want to consider using Ember as a technology, especially because there are many different kinds of stakeholders that would have different reasons to consider Ember. For example, many of the people in the Ember Community Discord are Ember developers that use Ember on a daily basis and could probably speak at length about some of the technical merits and potentially ergonomic benefits of using Ember, but might not have much of a grasp on the business reasons for using something like Ember. If you ask a develper they may talk about the powerful template syntax but a C-Level executivive might want to hear about our dedication to backwards compatibility and LTS release structure.

Note: C-Level executive refers to the decision makers of a business such as CTO, CEO or CIO. In the UK and other parts of the world they may be referred to as Managing Director or Technical Director. See https://en.wikipedia.org/wiki/Corporate_title for more information

While this effort doesn't proclude us from adding some sections in the theme of "Why Ember" to the homepage, having a whole page dedicated to it will allow us to give it the space it deserves.

Research and Previous efforts

This initiative has been spearheaded by @MelSumner in early 2018 and there has been a lot of discussion and research put into collecting content and opinions for this section. There was a survery form circulated to the community in 2018 that was used to collect a wider sample of "Why people have chosen Ember".

@MelSumner has also published a Gist here that was intended for people to have extra points of discussion that they might bring up when asked "Why should I use Ember"

Requirements

• Add a route /why that will be used for this efforts. This means that https://emberjs.com/why will always link (or redirect) to something that helps to answer the question "Why should you consider using Ember"
• Add a section for Developers and group some of the content on why developers should consider using Ember
• Add a section for C-Level exeutives
• Collect responses from the "Why Ember" survey and decide with the Learning Team which items will be included in which sections

Open Questions

• Do we need any other sections for the initial version? Should we have a section for project-managers or other parties?
• Would it be useful to have testimonials on this page?

Since this app was initially setup, we've landed a bunch of pages from the ember website. We'll need to update the nav bar links to point to the routes configured in this app so that whenever we launch preview apps & navigate via the navbar we end up landing on a page within this app instead of being redirected to emberjs.com

The goal of this issue is to recreate the Tomster FAQ page found on https://emberjs.com/tomster/faq/ in an Ember app. The routing names and the content look should be the same as the live site. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

To get started with this issue, please add a comment that you are interested in helping out with it, and share your ideas for how to solve the issue. If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Slack (https://ember-community-slackin.herokuapp.com/), click on "Channels", and join the #-team-learning channel. Thank you!

There is a Code Splitting section in the status board that is related to the Tree shaking feature commented at the Packaging RFC.

I have been searching for the Tree shaking status but it was not easy to figure out, there were a few issues: ember-cli/ember-cli#7308, ember-cli/ember-cli#7139 and finally the Bundler API was merged.

@twokul posted the Ember CLI 2018 Edition info; this post was the latest update I could find and when I asked on Discord, @kellyselden shared the WIP on ember-cli-rollup-packager.

I think creating a Quest issue with the pending work could help to improve the communication of the feature status and attract early adopters and/or contributors, as well as the quest issue could be linked in the Ember.js status board which is the default place to know the status of the latest initiatives.

We need to setup linters like template-lint, scss-lint and eslint for the project

It's hard to know if there has been any movement on something without any dates. Something like a date last updated would be a good start. Going further I'd love to see a history with dates.

• RFC Submitted - May 2017
• RFC Accepted - June 2017
• In Progress - June 2017

Someone new who looks at this page might miss the memo that the builds from source are for advanced use cases - mostly developers for ember itself or apps with edge cases that need to get the absolute latest code.

Add a note to the top that most people who are getting started with Ember should refer to the quickstart guide to download the latest stable cli, and link to it. Optional: maybe say something about what the builds page is for, if you understand it.

As described in #89, we added template linting for the app but disabled any rules that would require any further investigation or added work to fix.

The no-triple-curlies rule fails because of https://github.com/ember-learn/ember-website/blob/master/app/templates/learn/index.hbs#L111

This will probably be solved by moving the data into a MD file, using broccoli-static-site-json and implementing Ember Data for the website 👍

Goal

The goal of this issue is to recreate the page https://emberjs.com/sponsors/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /about/sponsors
• The content look should be the same as the live site
• remove the top level route sponsors
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

• Statusboard (#-team-learning)
• Marketing/website push (#wb-marketing / #st-website)
• Infrastructure modernization: dog-fooding our work (#-team-learning)
• Ember Data modernization. Could make folks nervous, so let's be careful on how we describe this (#dev-ember-data)
• jQuery removal. Could also make folks nervous to hear us wondering about this (#dev-jquery-removal)
• Tutorials: RFC for it? (#st-tutorials)

Goal

The goal of this issue is to recreate the Meetup Assets page https://emberjs.com/meetup-assets/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /community/meetups/assets
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)
• remove the top level meetup-assets route
• ensure that the project builds and all tests pass

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

Seems like as more things get shipped, we'll see those shipped items being "clutter" that makes it hard to see the other items, especially since there is no sort by status.

An idea might be to put them in another view, like tab based, or even better, adding filters that don't enable "shipped" by default.

Goal

The goal of this issue is to recreate the Team page https://emberjs.com/team/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /about/team
• move the content from the current top-level team page template to about/team page template
• use ember-styleguide components (and make notes where there is not an appropriate component)
• ensure that the final product looks like the https://emberjs.com/team
• remove the top-level team route
• ensure that the project builds and the tests pass

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

The various builds will be covered in the new navbar.

• Remove the sidebar for this app.
• ensure that the main content area takes up the full width of the page

Goal

The goal of this issue is to recreate the page https://emberjs.com/community/meetups in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /community/meetups
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

This needs to be dynamic based on the page rather than a static one.

Goal

The goal of this issue is to recreate the page https://emberjs.com/legal/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• remove /legal as a top-level route
• re-add route to /about/legal
• The content look be the same as the current template
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

Goal

Consolidate https://github.com/ember-learn/builds into this app under the /builds route

Todo

• Add what is currently the application route of the Builds App as the /builds route of the new website
• add each of the routes in the Builds App as subroutes of build e.g. builds/canary, /builds/beta, /builds/release
• add all of the added routes to the premberUrls https://github.com/ember-learn/ember-website/blob/master/ember-cli-build.js#L23

Goal

The goal of this issue is to recreate the page https://emberjs.com/learn/examples in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /learn/examples
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

Currently when you go to / on this app it automatically redirects you to /release/ but if we have the power to update links we should link directly to release 💪

This is something that seems to exist on the existing website and needs to be replicated here.

Netlify redirects are defined here: https://github.com/ember-learn/ember-website/blob/master/.netlifyredirects

Also make sure to remove the /about route from the Ember routes definition

Goal

The goal of this issue is to recreate the page https://emberjs.com/mascots/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /about/mascots
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

This will require significant broccoli development and will likely be implemented in a similar way to the new Ember Guides app.

This is likely work that will be done directly by @mansona but if anyone would be interested in a challenge please reach out on the #-team-learning channel in the Community Slack. Details of joining are on the Community page on the website

Update the statusboard page to use the accordion in the statusboard, so we have collapsing and expanding sections.

We recently turned on template linting for this project but in an effort to get the PR merged we temporarily turned off the rule img-alt-attributes https://github.com/ember-learn/ember-website/blob/master/.template-lintrc.js#L6

We should turn that rule back on and add alt attributes to all images 👍

Goal

The goal of this issue is to recreate the Community Page https://emberjs.com/community/ in an Ember app. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

Criteria

• Add route: /community
• The content look should be the same as the live site
• use ember-styleguide components (and make notes where there is not an appropriate component)

Additional Info

• To get started with this issue, please add a comment that you are interested in helping out with it.
• If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Discord and join the #dev-ember-learning channel. Thank you!

Goal

Consolidate https://github.com/ember-learn/deprecation-app into this app.

To Do

• add the deprecations route as a child route to releases
• add ember-data, ember-cli and ember as child routes to deprecations
• each major version should have its own child route within the relevant project
• move over deprecation content

This site is perpetually out of date because everything is hard coded.

This app should be data-driven for confirmed past dates, such as "latest minor release". Forward looking dates should be removed because they are not able to be extrapolated from data.

It's a hack, but the versions.json used by the API docs would probably be ok to depend on.

The /tomster/ route was already being redirected- the Ember version of the website should go ahead and use the /mascots/ route instead.

To-Do:

• update the route name for /tomster/ to /mascots/
• update the subroutes
• update any tests
• ensure all tests pass and the project builds successfully

The goal of this issue is to recreate the Logos page https://emberjs.com/logos/ in an Ember app. The routing names and the content look should be the same as the live site. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

To get started with this issue, please add a comment that you are interested in helping out with it, and share your ideas for how to solve the issue. If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Slack (https://ember-community-slackin.herokuapp.com/), click on "Channels", and join the #-team-learning channel. Thank you!

They are broken because they depend on a font that's not installed. Rather than add the font, locate the github, twitter, and google plus SVGs used in Ember-API-docs, save them, and replace the icons in the footer.

This is a temporary fix until the Ember-styleguide component is ready.

@rwjblue should we pull the current beta version from http://builds.emberjs.com/beta.json to auto update the beta version and where we are on the progress to the next release?

The goal of this issue is to recreate the Ember Users page https://emberjs.com/ember-users/ in an Ember app. The routing names and the content look should be the same as the live site. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

To get started with this issue, please add a comment that you are interested in helping out with it, and share your ideas for how to solve the issue. If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Slack (https://ember-community-slackin.herokuapp.com/), click on "Channels", and join the #-team-learning channel. Thank you!

The goal of this issue is to recreate the Guidelines page https://emberjs.com/guidelines/ in an Ember app. The routing names and the content look should be the same as the live site. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

To get started with this issue, please add a comment that you are interested in helping out with it, and share your ideas for how to solve the issue. If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Slack (https://ember-community-slackin.herokuapp.com/), click on "Channels", and join the #-team-learning channel. Thank you!

The goal of this issue is to recreate the Security page https://emberjs.com/security/ in an Ember app. The routing names and the content look should be the same as the live site. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

To get started with this issue, please add a comment that you are interested in helping out with it, and share your ideas for how to solve the issue. If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Slack (https://ember-community-slackin.herokuapp.com/), click on "Channels", and join the #-team-learning channel. Thank you!

The goal of this issue is to recreate the Meetup Getting Started page https://emberjs.com/community/meetups-getting-started/ in an Ember app. The routing names and the content look should be the same as the live site. The currently deployed site is a Ruby app found in a different repository, and we are working towards converting the whole site over.

To get started with this issue, please add a comment that you are interested in helping out with it, and share your ideas for how to solve the issue. If you have questions, need to get someone's attention for feedback, or it's your first time contributing, the learning team can help you out! The best way to get in touch is to join the Ember Community Slack (https://ember-community-slackin.herokuapp.com/), click on "Channels", and join the #-team-learning channel. Thank you!

• gather the items to be tracked on the status board.
• add them to the app in a data/projects.json file

Note: anyone who takes on this essential task should note that the final structure may differ from what you submit. Please don't take it personally. We'll need to figure out exactly what we want to track, and as such this might mean a few iterations. Thank you so much for helping!!

Currently, the statusboard is located in a separate app. Now that the entire site will be in Ember, we can eliminate this bifurcation by moving the statusboard content to this repo.

To Do

• ensure that the correct route exists
• Use the es-accordion component from ember-styleguide to implement the accordion found on the statusboard page
• put the data for the page in json format for now- we're still figuring out the best way to track overall projects.

This is essentially a follow on from #142 and should likely not be worked on until that issue is finished 👍

Note: this might turn into more of a meta/tracking issue- it's definitely a bigger chunk of work than typical single issues.

Goals

The idea is that the new /releases page will replace the current /builds, as well as integrate the release blog posts. This in turn will enable the release blog posts to be much more about the why, instead of technical implementation details, aiding in marketing efforts.

To do

• Include information on:
  • http://emberjs.com/builds/
  • http://emberjs.com/blog/2013/09/06/new-ember-release-process.html
  • http://emberjs.com/blog/2015/06/16/ember-project-at-2-0.html
  • http://emberjs.com/blog/2016/02/25/announcing-embers-first-lts.html
• Document releases separately from blog

Features

• current version should be prominent on the page
• widget that will show a yearly calendar in the releases pages, with the releases calculated :x
• release train visual (like current builds)
• description of release process
• list of channels
  • make sure we list all active LTSs