Now that you have the project information above, help me work through it using the following process.
I don't want you to immediately give me code or assume that the first Squarespace block I mention is the solution.
Instead, act as my pre-build thinking partner.
Your job is to help me figure out what I'm actually trying to build, identify multiple possible approaches, and compare them before I commit to one.

1. THINK
First, challenge my assumptions.
Look at the project information I provided and identify anything where I may already be assuming that I need:
- a particular Squarespace block
- a particular section type
- a particular interaction
- a particular coding method

If I'm jumping straight from "I want it to look like this" to "I need this specific thing," point that out.
Suggest alternative ways of thinking about the requirement.
Do not recommend code yet.


2. LOOK
Break the requested customization down into its core elements.
Focus on what needs to exist rather than what Squarespace feature might create it.

Identify:
- the core visual/content elements
- any functionality those elements need
- how those elements need to interact with each other
- any relationships between elements that matter
- how the layout needs to behave on mobile

Keep this focused on the actual requirements, not implementation yet.
Do not assume that a specific Squarespace block is required just because the reference or my description resembles one.


3. GATHER
Based on those requirements, give me multiple possible ways I could build this in Squarespace.
Don't assume that the most obvious block or section is the best choice.

For each option, tell me:
- What Squarespace structure could be used
- Which required elements it handles natively
- What would need to be added or changed
- Where custom code might be necessary
- Any obvious limitations or complications

Give me enough alternatives to make a meaningful comparison, but don't invent unnecessarily complicated solutions just to create more options.


4. EVALUATE
Now compare the options.
For each one, consider:

FUNCTIONALITY
- Does it provide what I need natively?
- What would require code?

IMPLEMENTATION
- How much custom code would likely be involved?
- Does the structure create unnecessary complexity?

MOBILE
- How naturally does the option adapt to mobile?
- Would I need additional code to make it work?

BACKEND / EDITING
- How easy would this be for the client to manage after delivery?
- Would the structure make adding, changing, or duplicating content unnecessarily difficult?

FUTURE CHANGES
- Would this approach be easy to modify if the client changes their mind later?
- Are there obvious constraints that could become a problem?

OVERALL
- What compromises am I making with each option?

Do this evaluation before recommending a final approach.


5. DECIDE
Based on everything above, recommend the option that makes the most sense for this particular project.
Don't simply choose the option requiring the least code.

Consider the balance between:
- implementation time
- code complexity
- Squarespace's native capabilities
- mobile behavior
- backend/editing experience
- future flexibility
- and my own comfort level with implementing it

Explain why you recommend it and what compromises I'm accepting.
Then give me a concise summary of:

WHAT I'M ACTUALLY BUILDING
[Summarize the actual requirements]

RECOMMENDED STRUCTURE
[Summarize the recommended approach]

WHAT NEEDS CUSTOM CODE
[Summarize what code is likely needed]

THINGS I SHOULD WATCH OUT FOR
[List the important considerations]

Only after we've settled on an approach should you help me identify or write the specific code needed.
If you think my chosen approach is unnecessarily complicated, tell me that too.