I would love to see more configuration options within the platform to be able to accomplish these best practices without having to go down the customization path.
@Tim Engstrom in the Now Learning course we try to align the leading practices to specific configuration choices in the platform. Of course there are differences when creating a form view of a table versus a catalog item. Are there specific examples of input experiences you encounter that require customization?
per the articles above, one of things I like to do for users is control the length (width and character count) of the fields. For example, a zip code would be 5 characters, maybe 10 if you are feeling saucy and want the plus 4. Instead of having a field that spans the width of the column (user assumes a lengthy input) it would be a field that has only space for those characters. If we look at what jot form has created or the form builders in Wordpress, there are configuration options that allow the builders to control some of these factors.
Perhaps a built in progress bar for multi-page forms (or even long form scrolling forms).
I could go into "one-click" forms (where single actions enter the data and drive to the next entry section) which would be cool, but that would be another ask completely.
I am not against customizing but would be nice to have some more configuration options built into the platform.
@AJ SiegelI can't speak for Tim, but from my perspective as an architect, the out-of-the-box widgets simply aren't built well. Putting the widget code aside for this conversation (that could take up an entire thread), the fact that some widgets have CSS that overrides the CSS set on the portal theme just doesn't make sense at all. Because CSS is applied in order of specificity, when this is the case, we're forced to either put the CSS on the widget instance level, or put it on the theme level and use !important everywhere to override the more specific widget CSS. All of this makes it super difficult and time-consuming to build portals to specific designs. If I were building portal widgets intended to be added to a page and have theme-level styling applied, I wouldn't put any CSS in the widget at all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
