Large connector forms are hard to visually parse

[travjenkins]

Ex 1/2 are screenshots of the example that made me notice this. Some of the large connector forms (especially with a lot of long descriptions) feel like a complex tax form. They are hard to parse or quickly scan for important notes.

I think we should put some effort to handle this with purely styling. We could break up a lot of this with changing some colors/fonts/weights/etc. for different sections of the forms.

Ex 1

Ex 2

[danthelion]

Some ideas:

• What if we hide the descriptions fields under a question mark symbol triggered by a mouse hover?
• What if we don't allow toggling show/hide of config blocks but make them always visible? This way they would have a more static structure and we get rid of 3 arrow symbols from the right side.
• What if we disable connector search of the capture creation window? Don't users always come here from the connector search anyway? As in if someone clicks the "new capture" button on a PostgreSQL connector we can be sure they want a PostgreSQL capture, right? This way we could get rid of this button completely too.
• The "Details" input field in the first section doesn't make a lot of sense to me "Describe your changes or why you're changing things." -> To me this field should be called "Description" instead, with a prompt like "Add an optional description for your connector".

an example of a very busy form snippet: