What's the situation?

We have a Webflow site that needs some love from an experienced developer. The previous developer left us with inconsistent spacing, confusing class names, and components that aren't built in a scalable way. We need an experienced developer who can help us clean this up and set standards for future development.

What kind of developer are we looking for?

We want a developer first, not a designer who knows some Webflow. You should be comfortable with:

• Writing and debugging JavaScript (we have real JS issues to solve, like fixing our table of contents scroll behavior and audio player bugs)

• Understanding how to structure components properly in Webflow

• Implementing a client-first design system

• Making sure everything works perfectly across all screen sizes

• Having enough design sense to spot and fix obvious visual issues

Here are some real examples of what you'll work on:

Fixing Existing Issues

• Our class names are a mess - we need help getting things in order using something like Finsweet's Client-First Style System

• Our table of contents doesn't highlight the active paragraph correctly, and the formatting needs work

• Audio player freezes on desktop and don't work on mobile

• Navigation menu needs to be rebuilt with a better drill-down design for mobile

• Text spacing and line height issues across different screen sizes

• Blog posts have inconsistent text hierarchy and spacing

Building New Stuff

• Creating reusable components for landing pages

• Building new page templates (like an author page - you will be provided with a design)

• Adding features like an automatic read-time calculator for blog posts

What makes you the right person?

• You know Webflow inside and out

• You can work quickly

• You can write code from scratch without using templates or components taken from other sites

• You have strong opinions about how to organize code and components

• You can look at our site structure and say "here's how we should reorganize this to make it maintainable"

• You can help us decide when something should be a custom page vs. a CMS collection

What we DO NOT need

• Someone who just knows how to customize Webflow templates

• A designer who dabbles in development

• Someone who needs detailed design direction and a Figma mockup for every small fix

We have a Notion board with a list of issues that we want to work though. After that, we'll have a couple of hours of work a week as we continue to produce new content and optimize the site.

• We want a developer first, not a designer who knows some Webflow
• Writing and debugging JavaScript (we have real JS issues to solve, like fixing our table of contents scroll behavior and audio player bugs)
• You know Webflow inside and out
• You can write code from scratch without using templates or components taken from other sites
• You have strong opinions about how to organize code and components
• Someone who just knows how to customize Webflow templates
• A designer who dabbles in development
• Someone who needs detailed design direction and a Figma mockup for every small fix

• You can work quickly

• Understanding how to structure components properly in Webflow
• Implementing a client-first design system
• Making sure everything works perfectly across all screen sizes
• Having enough design sense to spot and fix obvious visual issues
• Fixing Existing Issues
• Our class names are a mess - we need help getting things in order using something like Finsweet's Client-First Style System
• Our table of contents doesn't highlight the active paragraph correctly, and the formatting needs work
• Audio player freezes on desktop and don't work on mobile
• Navigation menu needs to be rebuilt with a better drill-down design for mobile
• Text spacing and line height issues across different screen sizes
• Blog posts have inconsistent text hierarchy and spacing
• Building New Stuff
• Creating reusable components for landing pages
• Building new page templates (like an author page - you will be provided with a design)
• Adding features like an automatic read-time calculator for blog posts