This may seem like a bit of an odd request, but one I think is important to help with knowledge transfer when site admin(s) may change hands and/or when there are new content editors.

This request is specific to a way for a page developer to be able to add notes to a page regarding custom content, where any such notes are only visible when a page is in edit mode. There may be cases where the design of a page is not straightforward and being able to document any "need to know" information on a page can be useful to someone who is new who may not see what's happening under the covers. Some examples of custom content that may not be apparent to someone unfamiliar with a page design:

* Use of custom HTML

* Use of forms

* Use of customer-defined custom CSS classes

* Use of ChurchCo-defined custom CSS classes

* Page dependency assumptions

Yes, this type of information can be documented separately, but that is not likely to happen and the ability to supply "in-place" page design notes would be easier to keep updated.