Enhance Site Builder Functionality and UI Components

- Added a new method to fetch blueprints from the API, improving data retrieval for site structures.
- Updated the WizardPage component to include a progress modal for better user feedback during site structure generation.
- Refactored state management in builderStore to track structure generation tasks, enhancing the overall user experience.
- Replaced SyncIcon with RefreshCw in integration components for a more consistent iconography.
- Improved the site structure generation prompt in utils.py to provide clearer instructions for AI-driven site architecture.

backend/igny8_core/modules/system/utils.py

@@ -253,6 +253,70 @@ Make sure each prompt is detailed enough for image generation, describing the vi
         'image_prompt_template': 'Create a high-quality {image_type} image to use as a featured photo for a blog post titled "{post_title}". The image should visually represent the theme, mood, and subject implied by the image prompt: {image_prompt}. Focus on a realistic, well-composed scene that naturally communicates the topic without text or logos. Use balanced lighting, pleasing composition, and photographic detail suitable for lifestyle or editorial web content. Avoid adding any visible or readable text, brand names, or illustrative effects. **And make sure image is not blurry.**',
         
         'negative_prompt': 'text, watermark, logo, overlay, title, caption, writing on walls, writing on objects, UI, infographic elements, post title',
+        
+        'site_structure_generation': """You are the lead IA and conversion-focused strategist for a new marketing website. Use the inputs from the site builder wizard to craft an SEO-rich, user-journey friendly site architecture that a design and content team can build immediately.
+
+INPUT DATA
+----------
+BUSINESS BRIEF:
+[IGNY8_BUSINESS_BRIEF]
+
+PRIMARY OBJECTIVES (rank by impact):
+[IGNY8_OBJECTIVES]
+
+DESIGN & STORY STYLE NOTES:
+[IGNY8_STYLE]
+
+SITE INFO (platform, audience, product/service category, any technical requirements):
+[IGNY8_SITE_INFO]
+
+TASK
+----
+1. Interpret the brief to define the core narrative arc (problem → solution → proof → conversion).
+2. Output a JSON object that matches the SiteStructure schema:
+{
+  "site": {
+    "name": "[Site or campaign name]",
+    "primary_navigation": ["..."],
+    "secondary_navigation": ["..."],
+    "hero_message": "[Top-level positioning statement]",
+    "tone": "[Voice guidance derived from style input]"
+  },
+  "pages": [
+    {
+      "slug": "kebab-case-slug",
+      "title": "SEO-friendly page title",
+      "type": "[page role e.g. hero, solution, proof, pricing, conversion]",
+      "status": "draft",
+      "objective": "Single measurable goal for this page aligned to objectives",
+      "primary_cta": "Primary call to action text",
+      "blocks": [
+        {
+          "type": "[block archetype e.g. hero, feature_grid, testimonial]",
+          "heading": "Section headline optimized for intent",
+          "subheading": "Support copy that clarifies value or context",
+          "layout": "Suggested layout pattern (full-bleed, two-column, cards, stats, etc.)",
+          "content": [
+            "Key talking points, proof, FAQs, offers, or data points"
+          ]
+        }
+      ]
+    }
+  ]
+}
+
+3. Produce 6–10 total pages covering the full funnel (awareness, consideration, evaluation, conversion, post-conversion/support) unless the objectives explicitly demand fewer.
+4. Every page must include at least three blocks ordered to tell a story, with clear internal logic (hook → build trust → guide action).
+5. Craft navigation labels that mirror user language, avoid jargon, and reinforce topical authority.
+6. Emphasize SEO signals: use keyword-rich yet natural titles, include topical coverage (solutions, use cases, proof, resources), and highlight schema-worthy elements (stats, FAQs, testimonials).
+
+RESPONSE RULES
+--------------
+- Return ONLY the JSON object described above. Do not wrap it in markdown.
+- Keep text human and specific; never say "Lorem ipsum" or "Example".
+- When objectives mention specific offers, personas, or industries, reflect them in page titles, CTAs, and block content.
+- If data is missing, infer the most logical assumption and note it inline with phrasing like "(assumed: ...)".
+""",
     }
     
     return defaults.get(prompt_type, '')