Make FluentCart's Bricks elements nestable

Right now, FluentCart elements behave like closed containers. That limits layout flexibility and forces us into predefined structures.

1. Make FluentCart elements nestable

Allow standard Bricks elements (Div, Block, Container, custom HTML, etc.) to be placed inside FluentCart elements.

This would give full control over layout, structure, and styling for:

• Product cards
• Cart items
• Checkout sections
• Order summaries
• Add to cart / Buy now buttons
• Quantity selectors
• Variation selectors (size, color, etc.)
• Checkout forms and fields

These are core UI components, and right now they can’t be composed freely. That makes it difficult to build anything beyond the default layouts.

This nesting pattern is already how Bricks works natively (e.g. Query Loop), and aligning with that would make FluentCart feel like a natural extension instead of a locked system.

2. Expose FluentCart data through Bricks dynamic data

FluentCart data should be available via Bricks dynamic tags, so it can be used anywhere, not only inside FluentCart elements.

For example:

• {fc_product_price}
• {fc_order_total}
• {fc_customer_name}

This should include:

• Product, cart, order, and customer fields
• Support for building custom loops (products, cart items, orders)
• Conditional logic (e.g. cart empty, user purchased, order status)

Why this matters

These changes remove structural limitations and unlock full design freedom inside Bricks.

Right now, FluentCart has the functionality, but the layout system is the bottleneck.

Open that up, and it becomes viable for fully custom builds instead of only predefined layouts.