My rule is simple. If a section shows up on more than one page with different content, it becomes a component with props. If it's the same everywhere, like the navbar or footer, I skip props completely. Webflow's docs say the same.
The fastest start now is suggested props. Select the section, click the "create component" icon at the top of the Components, Style or Element settings panel, then expand the suggested props list. I rename every one to something a client gets ("Hero heading", not "Heading 2"), untick anything that should stay fixed, and hit Create. For whatever it didn't suggest, double-click the instance, select the element and click the purple dot next to the value in Element settings.
What I add on nearly every section:
A Switch prop on the button wrapper, because some pages need a CTA and some don't. Hidden elements are removed from the DOM, so screen readers don't hit an empty button.
A proper default for every Image prop, so a new instance never lands with a placeholder.
Groups and tooltips. Eight loose props in the right panel is a mess. I group them (Content, Buttons) when I create them and add a tooltip to anything unclear.
And the stuff that caught me:
Styles aren't props. To change styles per instance, the docs point you to the class custom attribute.
Deleting a prop wipes the custom content in every instance using it, and they all fall back to the default. Rename instead of deleting and recreating.
On Collection pages you can bind props to CMS fields without unlinking. Exit the main component, select the element, click the purple dot on the prop and pick the field. One layout, every template.
That binding doesn't work for a component inside rich text.
If an instance gets into a weird state, open the more options menu on the instance and pick Reset all properties.