Has anyone successfully implemented the utility first CSS class convention in Webflow and have any tips on the initial setup, utility classes included, obstacles faced while building the site, if they would take this approach again, and a URL to the site?

Yes, many users have successfully implemented the utility-first CSS class convention in Webflow. This approach can have several benefits, such as faster development, easier maintenance, and increased consistency across the site.

To set up utility classes in Webflow, you can follow these steps:

1. Plan your utility classes: Determine the common utility classes you'll need in your project, such as margin, padding, font sizes, text alignment, background colors, and border styles.
2. Create a set of classes: In the Webflow Designer, navigate to the Styles panel and click on the "+" button to create a new class. Give the class a name that reflects its purpose (e.g., "u-margin-small-top").
3. Customize the class properties: Set the desired properties for each utility class, such as the margin or padding values, text styles, or colors.
4. Apply utility classes: Select the elements on your page where you want to apply the utility classes, navigate to the Style panel, and add the desired utility classes to the element.

During the development process, you may face a few obstacles when using utility classes in Webflow. Here are some common challenges and potential solutions:

1. Specificity conflicts: Sometimes, utility classes may conflict with existing styles or override each other. To resolve this, you can increase the specificity of the utility classes or redefine the conflicting styles.
2. Balancing customization and reusability: In a utility-first approach, it can be challenging to find the right balance between customization and reusability. You may need to fine-tune and create additional classes to accommodate specific design requirements.
3. Learning curve for teams: If you're working in a team, it may take some time for everyone to get comfortable with the utility class convention. Proper documentation, training, and consistent naming conventions can help overcome this obstacle.

Regarding whether users would take this approach again, it ultimately depends on their specific needs and preferences. Utility-first CSS is valuable for projects that require rapid development and maintainability. However, for projects with highly customized designs or complex layout requirements, a more traditional CSS approach might be preferred.

As for sharing a URL to a site using utility classes in Webflow, please note that as an AI, I don't have access to real-time data or specific URLs. However, you can find examples of utility-first CSS implementations by searching for Webflow sites using this approach online. Many professional Webflow designers and developers showcase their work on platforms like Dribbble, Behance, or personal portfolios, where you might find relevant case studies or examples.