I started a small blog series about some isues I find in ember

[stefan]

@yonjah

Since you shouldn’t use emebr-cli server in production CSP. setting CSP headers by ember-cli has no real meaning. its only importance is that emebr-cli users will be more aware of this feature and will take the effort to implement it on their production servers.

incorrect, by building your app in a CSP strict environment you:

1. will catch some violations immediately
2. will be ready to role from day 1 no need back-tracking, simply add the headers to production.
3. will work from day 1 in Firefox OS, PS3, and other strict environments.
4. also protect yourself while developing and working against production data. (common practice before you deploy)

@yonjah

But if this is an educational feature why does this commit doesn’t change any documentation in ember-cli ?

Firstly, this is not an educational feature. (See above)

Secondly I am glad you noticed the lack of docs: https://github.com/stefanpenner/ember-cli/tree/gh-pages is a great places to submit such documentation. As a continuation of your post, I welcome your writing skills in the form of helpful material that you noticed is lacking.

@yonjah

It would be highly beneficial if there was a readme file intended to explain the structure of ember-cli and how it runs it tasks so it would be easier to explore the code ( as I said maybe this document is already exist and I just failed to find it).

as mentioned several times: https://github.com/stefanpenner/ember-cli/blob/master/ARCHITECTURE.md If you have question about specific architectural questions that is missing. Take a chance, open a PR, and iterate with the community on improving that document.

@yonjah

I don’t think it should only be you and others who currently know the inner working who write this documentation. as a community we should all pitch in and try to improve the documentation but more people will do it if this would be declared as a priority by you and other main developers

This comment is concerning and I am unsure how to respond.

Roughly 1/5 of all commits to this project are documentation related. http://www.ember-cli.com/ and the Architecture.md did not appear without effort or priority, but they are the result of an ongoing community effort to improve the experience for all.

• Is it perfect, absolutely not
• does it need much TLC, yes!
• does the current state convey a lack of priority in documentation, I thought not…

If I have somehow conveyed that documentation is not a priority, please elaborate I would like to ensure others do not feel this way.

just to be sure, my public declaration of documentation priority:

https://twitter.com/stefanpenner/status/514247780593070080

Proposed Constructive Resolution & OSS Experiment

this discussion has value, we should ensure the value makes it out of this forum and into real tangible value for the community.

When you (or anyone) encounter documentation lacking, or confusion on a topic. Open a pull-request to the website. This PR should contain an outline of the confusion in the form of an explanation. Feel free to leave out the parts that are confusing. Then you, me and the community will in collaboration flesh out a well form piece of literature on the topic.