@ppcano wrote:

After a conversation about the EmberJS adoption, the ecosystem, and benefits, I found the Ember.js Wikipedia page describing very well the Ember philosophies and principles:

• Focus on ambitious web applications

• More productive out of the box

• Stability without stagnation

• Future web standards foresight

I have been using Ember for many years and I have experienced the reality and consistency of these principles over the time, while we get their benefits building and maintaining our SAAS product. But after evaluating the low Ember.js adoption even in some large apps in my location (Stockholm, Sweden), I wondered if the principles and benefits could not totally resonate to decision makers who finally select technologies based on other arguments like for example the lack of experienced developers (discussed in another topic ).

To help the communication of the Ember.js strengths, I propose creating the Ember.js Story Page:

The our story page is a commonly used to inform about the history behind a company, team or product; here a few examples: freshbooks, freshworks, airbnb, hyperloop, canva, instagram.

In the Ember.js case, the story page could show a timeline describing the different milestones the community has achieved and how the framework has evolved in its history. I think a visual representation of the past achievements helps to communicate some of the principles and benefits:

• stability without stagnation

• adoption for web standards.

• vibrant contributors and community

• rich ecosystem

• mature and long-term project

• ….

I am not sure if the proposal makes total sense, but I wanted to share the idea, so any feedback will be appreciated.

Related discussions

• How to I pitch Ember at my company
• What are our brand principles
• I am your secret admirer

Posts: 1

Participants: 1

Read full topic