# RC-006
## Landing Page Architecture & Tailwind Refinement

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

IMPORTANT

This is NOT feature development.

This is NOT authentication work.

This is NOT dashboard work.

This patch ONLY improves the Landing Page architecture and Tailwind implementation.

The objective is to produce a clean, production-ready SaaS landing page structure.

Visual polishing will be handled later.

Do NOT over-design.

---

Current Status

Landing page exists.

Tailwind has been repaired in RC-005.

Dashboard layouts have been stabilized.

Business logic is complete.

Authentication is complete.

Only Landing Page refinement is required.

---

Environment

Development

http://localhost/inveetaire/

Project runs inside:

localhost/inveetaire/

Production target

https://inveetaire.com/

Maintain BASE_PATH compatibility.

Never hardcode localhost.

Always use existing helper functions.

---

Objective

Refactor ONLY the Landing Page into a proper SaaS architecture.

Focus on:

Layout

Spacing

Container

Responsive behavior

Tailwind implementation

Semantic HTML

Accessibility

NOT visual creativity.

---

Keep Existing Content

Reuse all existing sections.

Do NOT invent new features.

Do NOT add testimonials.

Do NOT add blog.

Do NOT add FAQ.

Do NOT add animations.

Do NOT add videos.

Do NOT change product positioning.

Do NOT change wording unless required for layout consistency.

---

Required Page Structure

<header>

Sticky Navbar

</header>

<main>

Hero

Why Inveetaire

Features

Packages

Call To Action

</main>

<footer>

Footer

</footer>

Use proper semantic HTML.

---

Navbar

Implement:

Maximum width container

Centered navigation

Consistent spacing

Desktop

Mobile hamburger

Sticky behavior

Transparent at top

Solid background after scrolling

Proper z-index

Buttons aligned correctly

Do NOT overlap content.

---

Containers

Every section must use a consistent max-width.

Example:

max-w-7xl

mx-auto

px-6

lg:px-8

Spacing between sections must be consistent.

Avoid full-width text blocks.

---

Hero

Create a true two-column layout.

Left

Headline

Description

CTA Buttons

Right

Dashboard mockup

Image must scale correctly.

Prevent overflow.

Maintain aspect ratio.

Vertically center content.

---

Typography

Create proper hierarchy.

H1

Largest

H2

Section titles

Paragraph

Comfortable reading width

No extremely long lines.

---

Spacing

Audit every section.

Remove cramped layouts.

Increase whitespace.

Consistent vertical rhythm.

Use Tailwind spacing scale.

---

Cards

Features

Packages

Why section

Use consistent:

Padding

Rounded corners

Border

Shadow

Gap

Hover transition

Do NOT redesign.

Only standardize.

---

Responsive

Verify:

320px

375px

768px

1024px

1440px

Hero stacks correctly.

Navbar collapses correctly.

Cards wrap correctly.

Buttons remain usable.

No horizontal scrolling.

---

Accessibility

Use:

<header>

<nav>

<main>

<section>

<footer>

Proper heading hierarchy

Alt text

ARIA labels where appropriate

Keyboard accessible navigation

---

Assets

Verify:

Dashboard mockup

CSS

Icons

JavaScript

No broken assets.

No broken image paths.

---

Performance

Avoid unnecessary DOM nesting.

Avoid duplicate wrappers.

Keep Tailwind utilities clean.

Do NOT introduce additional CSS frameworks.

---

Constraints

Do NOT

Modify routing

Modify controllers

Modify authentication

Modify session

Modify dashboard layouts

Modify business modules

Modify database

Modify Tailwind configuration

Introduce JavaScript frameworks

Implement animation libraries

Implement SEO changes

Implement CMS

Implement marketing features

---

Verification

Verify:

Landing page loads correctly.

Tailwind classes render correctly.

Responsive layout works.

Navbar behaves correctly.

Hero alignment correct.

Cards consistent.

Footer aligned.

No overflow.

No console errors.

BASE_PATH compatibility.

localhost/inveetaire compatibility.

Production compatibility.

PHP syntax passes.

---

Acceptance Criteria

PASS only if:

Landing page has a clean SaaS structure.

Responsive layout is correct.

Spacing is consistent.

Typography hierarchy is correct.

Tailwind implementation is clean.

No business logic changed.

No routing changed.

No authentication changed.

PHP syntax passes.

---

Output

Provide:

1. Files modified.

2. Layout improvements.

3. Tailwind improvements.

4. Responsive improvements.

5. Accessibility improvements.

6. Verification results.

7. Acceptance checklist.

8. PHP syntax results.

Stop after implementation.

Wait for Human Approval.