tleperou · June 22, 2019 12:00 · Jun 22, 2019 · Jun 22, 2019 · Jun 22, 2019 · Jun 22, 2019
diff --git a/Ember-roadmap-2019.md b/Ember-roadmap-2019.md
@@ -47,7 +47,7 @@ For general public web applications, I choose Angular. For only one reason: its
 Embroider is promising. I have to tell you that I am so excited about this initiative! That said, my wish is to get a splitting code application based on routes, addons, or whatever.
 
 
-### Scoped CSS
+### Scoped (S)CSS
 
 If you are a utils CSS oriented integrator, the paragraph below won't interest you.
 
@@ -60,9 +60,7 @@ Even if ember-css-modules is a great addon, I think developers should rely on Em
 
 Ember might be an attractive option for simple websites which follow the ideas of the JAMstack. Ember-cli should provide a way to generate all the routes. Prember requires developers to configure the routes to render. 
 
-I wish we can render all the routes with no configuration using one command line:
-
-```ember render --env production```
+I wish we can render all the routes with no configuration using one command line such as ```ember render --env production```
 
 
 ## Thanks

diff --git a/Ember-roadmap-2019.md b/Ember-roadmap-2019.md
@@ -60,7 +60,7 @@ Even if ember-css-modules is a great addon, I think developers should rely on Em
 
 Ember might be an attractive option for simple websites which follow the ideas of the JAMstack. Ember-cli should provide a way to generate all the routes. Prember requires developers to configure the routes to render. 
 
-I wish we can render all the routes with no configurations using one command line:
+I wish we can render all the routes with no configuration using one command line:
 
 ```ember render --env production```
 

diff --git a/Ember-roadmap-2019.md b/Ember-roadmap-2019.md
@@ -17,7 +17,7 @@ Let's dive into the strategic ones.
 
 My first concern with Ember is to win the clients, companies, and juniors' trust. People are more informed of the Web technologies landscape than ever. Hence, I struggle to explain that Ember fits more than another framework (when the situation is appropriate). I struggle because I fight against beliefs. Unfortunately, I fight against the trendy-hipster-effect. Not the engineering issue.
 
-That said, I wish a modern website with consistent guidelines which and promotes that Ember is a viable option. We need to gain the trust of new developers.
+That said, I wish a modern website with consistent guidelines which promotes that Ember is a viable option. We need to gain the trust of new developers.
 
 
 ### Comparatives and benchmarks
@@ -31,7 +31,7 @@ That said, I wish accurate comparatives with other frameworks on the website (in
 
 ### Ember, worldwide
 
-My last concern is the presence of Ember in the world. The Asian and Indian markets abound of development companies and potential contributors. What do they do? Guess, Angular, and React. They would use Ember for their projects if they knew that Ember exists. They hardly know Ember exists.
+My last concern is the presence of Ember in the world. The Asian and Indian markets abound of development companies and potential contributors. What do they do? Guess, Angular, and React. They would use Ember for their projects if they knew that Ember exists. They hardly know about it.
 
 That said, I wish a multilingual website, including the "get started".
 
@@ -58,7 +58,9 @@ Even if ember-css-modules is a great addon, I think developers should rely on Em
 
 ### Static pages rendering
 
-Ember might be an attractive option for simple websites which follow the ideas of the JAMstack. I do agree with @neojp. Ember with Fastboot could provide a way to generate all the routes. Prember requires developers to configure the routes to render. I want to avoid configurations and leverage ember-cli with a command line like:
+Ember might be an attractive option for simple websites which follow the ideas of the JAMstack. Ember-cli should provide a way to generate all the routes. Prember requires developers to configure the routes to render. 
+
+I wish we can render all the routes with no configurations using one command line:
 
 ```ember render --env production```
 

diff --git a/Ember-roadmap-2019.md b/Ember-roadmap-2019.md
@@ -17,7 +17,7 @@ Let's dive into the strategic ones.
 
 My first concern with Ember is to win the clients, companies, and juniors' trust. People are more informed of the Web technologies landscape than ever. Hence, I struggle to explain that Ember fits more than another framework (when the situation is appropriate). I struggle because I fight against beliefs. Unfortunately, I fight against the trendy-hipster-effect. Not the engineering issue.
 
-That said, I wish to get an elegant and consistent style guideline. We need to gain the trust of new developers.
+That said, I wish a modern website with consistent guidelines which and promotes that Ember is a viable option. We need to gain the trust of new developers.
 
 
 ### Comparatives and benchmarks
@@ -26,7 +26,7 @@ My second concern relates the position in general of Ember within the frontend e
 
 Ember and its community should be proud of all the contribution they have done so far in the SPA's ecosystem. The features, the performance, the development experience, and the philosophy would convince new developers and reassure the Emberistas.
 
-That said, I wish a modern website which promotes accurate comparatives with other frameworks (with benchmarks performance) and show that Ember is a viable option.
+That said, I wish accurate comparatives with other frameworks on the website (including benchmarks performance).
 
 
 ### Ember, worldwide

diff --git a/Ember-roadmap-2019.md b/Ember-roadmap-2019.md
@@ -13,14 +13,14 @@ I articulate my wishes within 2 categories:
 
 Let's dive into the strategic ones.
 
-### Get trusts
+### An efficient website
 
-My first concern with Ember is to win the clients, companies, and juniors' trust. People are more informed of the Web technologies landscape than ever. Hence, I struggle to explain that Ember fits more than another framework (for an appropriate situation). I struggle because I fight against beliefs. Unfortunately, I fight against the trendy-hipster-effect. Not the engineering issue.
+My first concern with Ember is to win the clients, companies, and juniors' trust. People are more informed of the Web technologies landscape than ever. Hence, I struggle to explain that Ember fits more than another framework (when the situation is appropriate). I struggle because I fight against beliefs. Unfortunately, I fight against the trendy-hipster-effect. Not the engineering issue.
 
 That said, I wish to get an elegant and consistent style guideline. We need to gain the trust of new developers.
 
 
-### An efficient website
+### Comparatives and benchmarks
 
 My second concern relates the position in general of Ember within the frontend ecosystem. I can't stand to keep reading benchmarks or comparatives of Ember and React. It would make sense to focus on Glimmer and React; or, Ember and React/React-dom/React-router/React-redux.
 

diff --git a/Ember-roadmap-2019.md b/Ember-roadmap-2019.md
@@ -1,3 +1,5 @@
+# My wishes for the Ember roadmap 2019
+
 I've always been amazed by what Ember can make me accomplish. I created my first SPA with its version 1.13.  Since then, I deployed a few Angular and React applications. Ember remains my favorite :)
 
 The all-features out of the box with the Component, Data, and Router boundaries is a fantastic approach. Even if - most of - other frameworks require configurations before shipping Web applications, their success is unquestionable. Why not Ember too?
@@ -7,18 +9,18 @@ I articulate my wishes within 2 categories:
 2. pragmatic, to improve the development experience
 
 
-# Strategic
+## Strategic
 
 Let's dive into the strategic ones.
 
-## Get trusts
+### Get trusts
 
 My first concern with Ember is to win the clients, companies, and juniors' trust. People are more informed of the Web technologies landscape than ever. Hence, I struggle to explain that Ember fits more than another framework (for an appropriate situation). I struggle because I fight against beliefs. Unfortunately, I fight against the trendy-hipster-effect. Not the engineering issue.
 
 That said, I wish to get an elegant and consistent style guideline. We need to gain the trust of new developers.
 
 
-## An efficient website
+### An efficient website
 
 My second concern relates the position in general of Ember within the frontend ecosystem. I can't stand to keep reading benchmarks or comparatives of Ember and React. It would make sense to focus on Glimmer and React; or, Ember and React/React-dom/React-router/React-redux.
 
@@ -27,25 +29,25 @@ Ember and its community should be proud of all the contribution they have done s
 That said, I wish a modern website which promotes accurate comparatives with other frameworks (with benchmarks performance) and show that Ember is a viable option.
 
 
-## Ember, worldwide
+### Ember, worldwide
 
 My last concern is the presence of Ember in the world. The Asian and Indian markets abound of development companies and potential contributors. What do they do? Guess, Angular, and React. They would use Ember for their projects if they knew that Ember exists. They hardly know Ember exists.
 
 That said, I wish a multilingual website, including the "get started".
 
 
-# Practical
+## Practical
 
 Now, I want to address a few practical issues.
 
-## Splitting code
+### Splitting code
 
 For general public web applications, I choose Angular. For only one reason: its lazyload module. Even for mobile-oriented usages, I pick Angular for the same reason. The size of the applications' source, especially for large ones, is a critical issue that Ember should provide a Just Work™ solution.
 
 Embroider is promising. I have to tell you that I am so excited about this initiative! That said, my wish is to get a splitting code application based on routes, addons, or whatever.
 
 
-## Scoped CSS
+### Scoped CSS
 
 If you are a utils CSS oriented integrator, the paragraph below won't interest you.
 
@@ -54,14 +56,14 @@ Set apart the abstracted components, does anyone creates components without styl
 Even if ember-css-modules is a great addon, I think developers should rely on Ember only. My wish is to get a native scoped-style system, which Just Works™.
 
 
-## Static pages rendering
+### Static pages rendering
 
 Ember might be an attractive option for simple websites which follow the ideas of the JAMstack. I do agree with @neojp. Ember with Fastboot could provide a way to generate all the routes. Prember requires developers to configure the routes to render. I want to avoid configurations and leverage ember-cli with a command line like:
 
 ```ember render --env production```
 
 
-# Thanks
+## Thanks
 
 That's all for me.  Thanks to the core team and the community for participating in this great adventure. 
 

diff --git a/Ember roadmap 2019 → Ember-roadmap-2019.md b/Ember roadmap 2019 → Ember-roadmap-2019.md
diff --git a/Ember roadmap 2019 b/Ember roadmap 2019
@@ -1 +1,68 @@
-# Ember roadmap 2019
+I've always been amazed by what Ember can make me accomplish. I created my first SPA with its version 1.13.  Since then, I deployed a few Angular and React applications. Ember remains my favorite :)
+
+The all-features out of the box with the Component, Data, and Router boundaries is a fantastic approach. Even if - most of - other frameworks require configurations before shipping Web applications, their success is unquestionable. Why not Ember too?
+
+I articulate my wishes within 2 categories:
+1. strategic, mostly to grow the Emberistas community
+2. pragmatic, to improve the development experience
+
+
+# Strategic
+
+Let's dive into the strategic ones.
+
+## Get trusts
+
+My first concern with Ember is to win the clients, companies, and juniors' trust. People are more informed of the Web technologies landscape than ever. Hence, I struggle to explain that Ember fits more than another framework (for an appropriate situation). I struggle because I fight against beliefs. Unfortunately, I fight against the trendy-hipster-effect. Not the engineering issue.
+
+That said, I wish to get an elegant and consistent style guideline. We need to gain the trust of new developers.
+
+
+## An efficient website
+
+My second concern relates the position in general of Ember within the frontend ecosystem. I can't stand to keep reading benchmarks or comparatives of Ember and React. It would make sense to focus on Glimmer and React; or, Ember and React/React-dom/React-router/React-redux.
+
+Ember and its community should be proud of all the contribution they have done so far in the SPA's ecosystem. The features, the performance, the development experience, and the philosophy would convince new developers and reassure the Emberistas.
+
+That said, I wish a modern website which promotes accurate comparatives with other frameworks (with benchmarks performance) and show that Ember is a viable option.
+
+
+## Ember, worldwide
+
+My last concern is the presence of Ember in the world. The Asian and Indian markets abound of development companies and potential contributors. What do they do? Guess, Angular, and React. They would use Ember for their projects if they knew that Ember exists. They hardly know Ember exists.
+
+That said, I wish a multilingual website, including the "get started".
+
+
+# Practical
+
+Now, I want to address a few practical issues.
+
+## Splitting code
+
+For general public web applications, I choose Angular. For only one reason: its lazyload module. Even for mobile-oriented usages, I pick Angular for the same reason. The size of the applications' source, especially for large ones, is a critical issue that Ember should provide a Just Work™ solution.
+
+Embroider is promising. I have to tell you that I am so excited about this initiative! That said, my wish is to get a splitting code application based on routes, addons, or whatever.
+
+
+## Scoped CSS
+
+If you are a utils CSS oriented integrator, the paragraph below won't interest you.
+
+Set apart the abstracted components, does anyone creates components without styling it? No, it can't be. Styling an application is an essential task throughout the development process. It directly contributes to the success of projects. Design web applications with a scope-style system should not be optional.
+
+Even if ember-css-modules is a great addon, I think developers should rely on Ember only. My wish is to get a native scoped-style system, which Just Works™.
+
+
+## Static pages rendering
+
+Ember might be an attractive option for simple websites which follow the ideas of the JAMstack. I do agree with @neojp. Ember with Fastboot could provide a way to generate all the routes. Prember requires developers to configure the routes to render. I want to avoid configurations and leverage ember-cli with a command line like:
+
+```ember render --env production```
+
+
+# Thanks
+
+That's all for me.  Thanks to the core team and the community for participating in this great adventure. 
+
+Let's make Ember better, all together.
diff --git a/Ember roadmap 2019 b/Ember roadmap 2019
@@ -0,0 +1 @@
+# Ember roadmap 2019