Hi Scott (great name btw )
I am talking about defaulting page items (text boxes, display items, buttons, etc).
The user interface defaults seem to only apply to table items. I'm talking about when I create any item for a page, not just from a form or IG.
My thoughts are to create a "starter page" with a hidden region on it with 1 of each type set to our standards... create a new page by copying that page, and then duplicating items to get the standards I want to enforce
Isn't is just?
Template applications/pages can be useful.
UI defaults, as that thread suggests, is limited to components created via the wizards, so not always ideal.
Would there be any value in using global page items for whatever you're trying to do? Components that are defined once for an app, used many times.
Scott H. wrote:
Also, to go back and globally update existing ones to match this default would be helpful?
You can also check Cross Page Utilities. There you can grid edit most of items and use reports see that attributes match