Repository navigation
Update Introduction - #9684
Update Introduction#9684hmullen wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
My thoughts on this: it's jargon one way or the other. Lets avoid jargon and tell people something that has meaning on its own. I think that "Attaching code behind/to DOM elements." is definitely an attempt at this, but I'm not sure it goes far enough.
How about something like "Attaches behaviour to DOM elements.", "Brings direction", etc.
There are a lot of ways I think we could make this a more meaningful piece of information, what do you think? I don't feel like "Attaching code behind/to DOM elements." is telling me anything concrete. I sort of get the meaning it's trying to evoke, but I think it can be said better. I'm not a writer, but perhaps someone who is can say this better?
|
I'm sorry, but I wasn't able to verify your Contributor License Agreement (CLA) signature. CLA signature is required for any code contributions to AngularJS. Please sign our CLA and ensure that the CLA signature email address and the email address in this PR's commits match. If you signed the CLA as a corporation, please let us know the company's name. Thanks a bunch! PS: If you signed the CLA in the past then most likely the email addresses don't match. Please sign the CLA again or update the email address in the commit of this PR. |
This commit tries to remove the jargon and explain in plain English what it means to add "code-behind" via a directive. Closes #9684
Is there such a thing as code-behind? I'm thinking the slash is a better choice here. http://www.grammarly.com/handbook/punctuation/other-punctuation-marks/4/slash/