We are looking for a very senior Webflow developer who:

Can debug and re-engineer the current setup.

Is comfortable with implementation of Lottie animations, Webflow’s CMS limits, custom code injections. Can create a future-proof and scalable structure for our project library.

GOAL: Refactor and fix the current case study implementation so it is functional, maintainable, and scalable (especially for +100 CMS projects with custom sliders per project).

The current Webflow implementation was developed using a custom script architecture layered on top of a CMS system. However, it is unstable and not functioning as intended.

Project URL: firestarters360.webflow.io/

ISSUES TO RESOLVE:

1. Lottie Animation Triggering

Problem: Lottie animations are auto-playing and looping for all slides on page load.

Expected: Animations should only play when the user navigates to the corresponding slide, and stop after completion. No looping.

1. Pagination Bar Interaction

Problem: The pagination bar has incorrect z-index, blocking interactions.

Expected:

Pagination should be interactive—user should be able to click on left/right side to go to previous/next slides.

Ensure proper layering/z-index so interactions aren't blocked.

1. Navigation Arrows

Problem: Arrows are visually too large and are always visible.

Expected:

Match arrow dimensions to design (can provide Figma specs).

Arrows should be hidden by default and only show on hover over the project slider area

1. Cursor Interaction

Problem:

The "Iris" dot cursor trails too slowly behind the actual cursor.

The blurred background shape behaves erratically.

Expected:

Cursor "iris" should follow more closely and smoothly.

Background shape should move intuitively and fluidly in sync with cursor motion.

1. Mobile Dot Positioning

Problem: Dots (including interactive elements and/or cursor-related graphics) are misplaced or invisible on mobile.

Expected: Responsive design fix ensuring full visibility and alignment of interactive elements on all screen sizes.

1. General Code Maintainability

Problem: Current implementation is difficult to maintain or iterate on.

Expected:

Streamlined, modular code architecture.

Use reusable Webflow classes and interactions where possible.

Leave commented code or documentation where custom scripts are required.

• Arrows should be hidden by default and only show on hover over the project slider area
• Cursor Interaction
• The "Iris" dot cursor trails too slowly behind the actual cursor
• Cursor "iris" should follow more closely and smoothly
• Background shape should move intuitively and fluidly in sync with cursor motion
• Problem: Dots (including interactive elements and/or cursor-related graphics) are misplaced or invisible on mobile
• Problem: Current implementation is difficult to maintain or iterate on
• Streamlined, modular code architecture

• Can debug and re-engineer the current setup
• Is comfortable with implementation of Lottie animations, Webflow’s CMS limits, custom code injections
• Can create a future-proof and scalable structure for our project library
• GOAL: Refactor and fix the current case study implementation so it is functional, maintainable, and scalable (especially for +100 CMS projects with custom sliders per project)
• The current Webflow implementation was developed using a custom script architecture layered on top of a CMS system
• However, it is unstable and not functioning as intended
• Lottie Animation Triggering
• Problem: Lottie animations are auto-playing and looping for all slides on page load
• Expected: Animations should only play when the user navigates to the corresponding slide, and stop after completion
• Problem: The pagination bar has incorrect z-index, blocking interactions
• Pagination should be interactive—user should be able to click on left/right side to go to previous/next slides
• Ensure proper layering/z-index so interactions aren't blocked
• Navigation Arrows
• Problem: Arrows are visually too large and are always visible
• The blurred background shape behaves erratically
• Mobile Dot Positioning
• Expected: Responsive design fix ensuring full visibility and alignment of interactive elements on all screen sizes
• General Code Maintainability
• Use reusable Webflow classes and interactions where possible
• Leave commented code or documentation where custom scripts are required