-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
New Feature: "Why Ember" Page #131
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still a valid issue and will likely be done after the current effort on the Ember Website RFC 🤔 @MelSumner @pichfl do you think that we should include this in the content map that we're now working on? is there enough material for it to be included in the current work? |
As the RFC is merged, it would be appropriate to put it into consideration for the content structure 🙂 |
This issue has been automatically marked stale. If this issue is something that still needs work, please add a comment and it will remain open, otherwise it will close in 7 days. You are welcome to open a new issue if you miss the window. Thanks! |
I think we should start looking into this after the redesign is complete, commenting so we can keep it open 👍 |
This issue has been automatically marked stale. If this issue is something that still needs work, please add a comment and it will remain open, otherwise it will close in 7 days. You are welcome to open a new issue if you miss the window. Thanks! |
I am very much looking forward to staring on this issue 😍 |
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 informationWhile 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
/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"Open Questions
The text was updated successfully, but these errors were encountered: