Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Update Introduction #9684

Closed
wants to merge 1 commit into from
Closed

Update Introduction #9684

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/guide/introduction.ngdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ browser new syntax through a construct we call directives. Examples include:
* Data binding, as in `{{}}`.
* DOM control structures for repeating/hiding DOM fragments.
* Support for forms and form validation.
* Attaching code-behind to DOM elements.
* Attaching code behind/to DOM elements.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

* Grouping of HTML into reusable components.


Expand Down