# RC-007
## Brand Identity & Visual Design Refinement

You are implementing Release Candidate RC-007 for the INVEETAIRE platform.

This is NOT feature development.

This is NOT architecture refactoring.

This is NOT layout redesign.

This is NOT authentication work.

This is NOT business logic.

The application architecture has already been stabilized.

The landing page structure has already been completed in RC-006.

Your responsibility is ONLY visual refinement and brand identity.

---

Platform

INVEETAIRE

Digital Wedding Management Platform

Target Audience

• Couples

• Wedding Organizers

• Wedding Planners

• Wedding Vendors

The website should communicate:

Elegant

Premium

Modern

Romantic

Trustworthy

Minimal

Clean

NOT:

Developer Tool

Fintech

Cyber Security

AI Dashboard

Enterprise Software

---

Objective

Keep the current layout exactly the same.

Do NOT move sections.

Do NOT change content hierarchy.

Do NOT rewrite the page.

Instead, elevate the visual quality until it feels like a premium SaaS product built specifically for weddings.

Think:

Luxury Wedding Brand

+

Modern SaaS

---

Brand Direction

Primary Background

White

Off White

Very Light Gray

Very Light Lavender

Use white as the dominant background.

Avoid dark theme sections except where absolutely necessary.

---

Primary Color

Soft Lavender

Pastel Pink

Suggested palette:

#D8B4FE

#C084FC

#A855F7

---

Secondary Color

Soft Periwinkle Blue

Suggested palette

#8FA8FF

#7C9DFF

#6366F1

---

Accent

Soft Rose

Suggested

#F472B6

---

Neutral

Slate

Gray

White

Avoid heavy black.

---

Visual Style

Modern SaaS

Luxury Wedding

Large whitespace

Rounded corners

Soft shadows

Subtle gradients

Glass effect where appropriate

Minimal borders

Premium typography hierarchy

---

Improve

Only improve visual styling.

Examples:

Buttons

Cards

Navbar

Hero

Feature Cards

Pricing Cards

CTA Section

Footer

Section backgrounds

Gradients

Border colors

Shadow depth

Hover states

Typography emphasis

Spacing refinements

Container consistency

---

Do NOT

Do NOT redesign layout.

Do NOT add animations.

Do NOT add new sections.

Do NOT add testimonials.

Do NOT add blogs.

Do NOT add FAQ.

Do NOT add pricing logic.

Do NOT modify routing.

Do NOT modify PHP controllers.

Do NOT modify services.

Do NOT modify authentication.

Do NOT modify Tailwind configuration.

Do NOT change responsive structure.

---

Hero Section

Make the hero feel premium.

Improve:

Headline emphasis

Gradient text

Button hierarchy

Mockup framing

Background lighting

Spacing

Without changing layout.

---

Cards

All cards should share a consistent design system.

Rounded-xl

Soft shadow

Elegant border

Hover lift

Subtle background tint

Consistent spacing

---

Buttons

Primary

Lavender gradient

Soft glow

Rounded-xl

Secondary

White background

Soft border

Elegant hover

---

Navbar

Minimal

Premium

Light background

Glass effect

Better spacing

Elegant active states

---

Footer

Premium

Minimal

Clean typography

Better spacing

Subtle divider

---

Brand Identity

The final result should make users feel:

"This is a premium wedding platform."

instead of

"This is an admin dashboard."

---

Design Inspiration

Use inspiration similar to:

Stripe (Light)

Framer

Linear (Light)

Webflow

Notion Calendar

Tally

Lovable

Zola Weddings

Joy Wedding

Apple Marketing Pages

Do NOT copy.

Only use them as inspiration for quality and polish.

---

Maintain

BASE_PATH compatibility

localhost/inveetaire/

Production compatibility

No broken assets

No broken Tailwind classes

No broken responsive behavior

---

Verification

Verify

Desktop

Tablet

Mobile

Navbar

Hero

Feature cards

Pricing

CTA

Footer

Hover states

Typography

Spacing

Responsive

Accessibility

No overflow

No console errors

PHP syntax passes

---

Acceptance Criteria

PASS only if:

The landing page feels significantly more premium.

Brand identity matches a luxury wedding SaaS.

White becomes the dominant base color.

Lavender/Pastel Pink becomes the primary brand color.

Blue becomes the supporting color.

Visual hierarchy is improved.

Existing layout remains unchanged.

No business logic changes.

No routing changes.

No authentication changes.

PHP syntax passes.

---

Output

Provide:

1. Brand palette used.

2. Design improvements.

3. Components refined.

4. Visual hierarchy improvements.

5. Responsive verification.

6. Accessibility verification.

7. Acceptance checklist.

8. PHP syntax results.

Stop after implementation.

Wait for Human Approval.