You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a number of places where references are made to customization (SDK) subjects from inside end user content. For example, see preferences-schema-aware.dita, which has a reference to AuthorSchemaAwareEditingHandler at the end.
Many readers will be confused by these references. On the other hand, I don't think we should take them out because they could alert users to the possibility of customizing behavior. So I think we need a way to set the apart clearly, so that readers are not confused by them, but are made aware of the possibilities. I would suggest something along the lines of a "Customization note" that points to the possibility of customizing a particular behavior.
Thoughts?
The text was updated successfully, but these errors were encountered:
There are a number of places where references are made to customization (SDK) subjects from inside end user content. For example, see preferences-schema-aware.dita, which has a reference to AuthorSchemaAwareEditingHandler at the end.
Many readers will be confused by these references. On the other hand, I don't think we should take them out because they could alert users to the possibility of customizing behavior. So I think we need a way to set the apart clearly, so that readers are not confused by them, but are made aware of the possibilities. I would suggest something along the lines of a "Customization note" that points to the possibility of customizing a particular behavior.
Thoughts?
The text was updated successfully, but these errors were encountered: