I have an editor on my Material-based site that lets users edit entity data. Each item might have a large number of key-value pairs, only a few of which are required, and I'm trying to surface the most commonly used ones near the top, but I still quickly wind up in Your Company's App territory.
I've seen this older question on SO about
fieldset in Material forms, and am planning on taking an approach along the lines of this example from that question's sole answer as a starting point. Flat organization will still result in an editor that might scroll for several pages, though. I'm afraid it wouldn't make sense to use a Stepper (or possibly Tabs?) either, since a user popping in to edit one field shouldn't have to click through several mystery pages to figure out where the thing they're looking for might be.
Am I right to try to make sure that all the fields stay on one page? If so, does Material have an opinion about how to make my wall-of-fields less off-putting for the user?