You are an expert Senior UI/UX Designer, Hospitality Website Designer, PHP Full-Stack Developer, MySQL Database Architect, SEO Specialist, and Conversion-Focused Web Engineer.

Your task is to design and build a production-ready premium hotel website for:

HOTEL ASTHA GRAND
Location: Banaras / Varanasi, Uttar Pradesh, India

The website must feel like a premium hospitality brand while maintaining a subtle connection with the culture, heritage and visual character of Banaras.

---

1. PRIMARY OBJECTIVE

Build a modern, premium, responsive and conversion-focused hotel website that helps visitors:

- Discover Hotel Astha Grand
- Explore rooms
- View room details and amenities
- Check availability
- Submit booking requests
- Contact the hotel
- Start a WhatsApp conversation
- Explore hotel photography
- Discover Banaras experiences
- Find the hotel location
- Understand hotel facilities and policies

The website must be designed for real-world implementation, not as a static visual mockup.

The complete system must be compatible with:

- PHP
- MySQL / SQL
- HTML5
- CSS3
- Vanilla JavaScript where possible

Avoid unnecessary frameworks unless there is a strong technical reason to use them.

---

2. CORE DESIGN CONCEPT

Use the design concept:

"MODERN BANARAS"

Combine:

Banaras heritage + contemporary luxury + warm Indian hospitality

The website should feel:

- Premium
- Elegant
- Warm
- Sophisticated
- Trustworthy
- Welcoming
- Modern
- Culturally connected

Do NOT make it look like:

- A generic hotel template
- A cheap booking website
- An overly colorful Indian wedding website
- An excessively religious website
- An old-fashioned hotel website
- A cluttered tourism website

Banaras-inspired elements should be subtle and tasteful.

---

3. VISUAL DIRECTION

Use a refined hospitality aesthetic.

Suggested palette:

Primary:
Deep Maroon — #5A1825

Secondary:
Antique Gold — #B08A45

Background:
Warm Ivory — #F7F3EC

Dark:
Charcoal — #1C1C1C

Accent:
Muted Ganga Blue — #496D76

White:
#FFFFFF

Use CSS variables for the color system so the entire theme can be changed easily.

Do not overuse gold.

Use gold mainly for:

- Fine borders
- Small highlights
- Icons
- Dividers
- Selected states
- Premium accents

---

4. TYPOGRAPHY

Use an elegant serif font for major headings and a clean modern sans-serif font for body/UI.

Typography hierarchy should be clearly established:

- Large editorial hero heading
- Strong section headings
- Medium card headings
- Comfortable body text
- Small metadata
- Clear CTA typography

Maintain excellent readability on mobile.

---

5. IMAGERY

Use large, high-quality hospitality photography.

Preferred visual subjects:

- Hotel exterior
- Hotel entrance
- Lobby
- Rooms
- Beds
- Bathrooms
- Dining
- Hotel details
- Banaras architecture
- Ganga/ghats
- Local culture
- Banarasi details

Use cinematic photography in hero sections.

Do not use random unrelated stock photography.

Where actual Hotel Astha Grand images are unavailable, use clearly replaceable image placeholders or appropriate temporary imagery.

Structure image components so actual hotel images can easily be replaced later.

---

6. WEBSITE INFORMATION ARCHITECTURE

Create these main pages:

1. Home
2. Rooms
3. Room Details
4. Amenities
5. Experience Banaras
6. Gallery
7. About Us
8. Contact
9. Booking
10. Booking Confirmation
11. Privacy Policy
12. Terms & Conditions
13. Cancellation Policy
14. 404 Page

Primary navigation:

HOME
ROOMS
AMENITIES
EXPERIENCE
GALLERY
ABOUT
CONTACT

Primary CTA:

BOOK NOW

---

7. HOMEPAGE

Create a premium long-form homepage.

SECTION 1 — HERO

Full-width cinematic visual.

Overlay:

EXPERIENCE BANARAS

A Grand Stay in the Heart of Banaras

Buttons:

EXPLORE ROOMS

BOOK YOUR STAY

Add a subtle scroll indicator.

Header should initially be transparent over the hero and transition into a solid/light background after scrolling.

---

8. BOOKING WIDGET

Place a highly visible booking/search widget.

Fields:

- Check-in
- Check-out
- Adults
- Children
- Rooms

CTA:

CHECK AVAILABILITY

Validate dates.

Rules:

- Check-out cannot be before check-in
- Past check-in dates should not be accepted
- Guest count must be valid
- Required fields must be validated both client-side and server-side

The widget must eventually connect to the PHP/MySQL booking system.

---

9. WELCOME SECTION

Heading:

WELCOME TO HOTEL ASTHA GRAND

Create a sophisticated split layout.

Left:

Hotel story/content.

Right:

Large hotel image.

Copy direction:

Hotel Astha Grand provides a comfortable and refined stay for travellers visiting Banaras, combining modern hospitality with the warmth and character of the city.

Do not invent unsupported facts.

Use editable content where hotel-specific information is unknown.

CTA:

DISCOVER OUR HOTEL

---

10. ROOMS SECTION

Heading:

STAY IN COMFORT

Subheading:

Thoughtfully designed rooms for a comfortable stay in Banaras.

Create premium room cards.

Each room card must contain:

- Image
- Room name
- Short description
- Occupancy
- Bed type
- Room size if available
- Starting price if available
- Key amenities
- View Details
- Book Now

Example room categories can be:

- Deluxe Room
- Executive Room
- Premium Room
- Suite

IMPORTANT:

Do not assume these exact rooms exist.

Make room categories database-driven so actual Hotel Astha Grand room inventory can replace them.

---

11. ROOM DETAILS PAGE

Create a dedicated dynamic room details page.

Example URL:

/rooms/deluxe-room

Page structure:

- Breadcrumb
- Large image gallery
- Room title
- Short description
- Price
- Occupancy
- Bed type
- Room size
- Amenities
- Detailed description
- Policies
- Availability
- Booking CTA
- Similar rooms

Gallery must support:

- Thumbnail navigation
- Lightbox
- Swipe on mobile

Primary CTA:

BOOK THIS ROOM

---

12. AMENITIES

Create a premium icon-based amenities section.

Potential items:

- Free Wi-Fi
- 24/7 Front Desk
- Housekeeping
- Room Service
- Restaurant
- Parking
- Air Conditioning
- TV
- Hot Water
- Laundry
- Travel Assistance
- Elevator

IMPORTANT:

Only display facilities that are confirmed by the hotel.

Amenities should be database-driven.

---

13. EXPERIENCE BANARAS

Create an editorial tourism section.

Heading:

DISCOVER BANARAS

Categories:

Ganga & Ghats

Explore the timeless atmosphere around the Ganga.

Temples

Discover the spiritual and architectural heritage of Kashi.

Food

Experience Banaras through its famous local flavours.

Culture & Heritage

Discover the lanes, markets, traditions and living culture of the city.

Use image cards.

Each experience should support:

- Title
- Image
- Description
- Detail page
- SEO metadata

Do not fabricate historical claims.

---

14. LOCATION SECTION

Create a location section containing:

- Hotel address
- Interactive map
- Nearby attractions
- Directions CTA
- Contact information

Nearby distances must only be shown after they are verified.

CTA:

GET DIRECTIONS

---

15. GALLERY

Create a visually rich responsive gallery.

Categories:

- Hotel
- Rooms
- Dining
- Amenities
- Banaras
- Experiences

Features:

- Masonry/grid layout
- Lightbox
- Mobile swipe
- Lazy loading
- Image alt text

Gallery must be controlled from the admin panel.

---

16. REVIEWS

Create a guest review section.

Display:

- Guest name
- Rating
- Review
- Date

Do not create fake reviews.

Reviews must be database-driven.

Admin should control:

- Add
- Edit
- Delete
- Publish/unpublish

---

17. FINAL BOOKING CTA

Create a strong conversion section:

YOUR BANARAS JOURNEY STARTS HERE

Supporting text:

Plan your stay at Hotel Astha Grand and experience Banaras with comfort and convenience.

CTA:

CHECK AVAILABILITY

---

18. CONTACT PAGE

Create a premium contact page.

Include:

- Hotel name
- Address
- Phone
- Email
- WhatsApp
- Map
- Contact form

Form:

Name
Phone
Email
Subject
Message

Show clear validation and success/error states.

Success:

"Thank you. Your enquiry has been received."

Error:

"Something went wrong. Please try again."

---

19. WHATSAPP

Add a floating WhatsApp CTA.

Text:

Chat With Us

The WhatsApp number must come from the website settings/database rather than being hardcoded throughout the application.

---

20. BOOKING SYSTEM

Create a database-backed booking system.

Flow:

Step 1

Guest selects dates and guests.

Step 2

System queries available rooms.

Step 3

Guest selects room.

Step 4

Guest enters:

- Name
- Phone
- Email
- Adults
- Children
- Special request

Step 5

Show booking summary:

- Room
- Check-in
- Check-out
- Number of nights
- Guests
- Room price
- Taxes/charges if configured
- Total

Step 6

Submit booking.

Generate unique booking reference.

Example format:

HAG-2026-000001

Do not use predictable sequential IDs as public database identifiers.

---

21. BOOKING STATUS

Support:

- Pending
- Confirmed
- Cancelled
- Completed
- No Show

Payment status:

- Pending
- Paid
- Failed
- Refunded

Initially support booking enquiry/request mode.

Design the architecture so online payment can be integrated later.

---

22. DATABASE

Create a normalized MySQL database.

Suggested tables:

admins
users
rooms
room_images
amenities
room_amenities
bookings
booking_rooms
guests
payments
enquiries
gallery
reviews
experiences
site_settings

Use proper:

- Primary keys
- Foreign keys
- Indexes
- Timestamps
- Status fields
- Unique constraints where required

Use InnoDB.

Use utf8mb4.

---

23. ADMIN PANEL

Create a secure PHP admin dashboard.

URL:

/admin/login.php

Dashboard:

- Total bookings
- Pending bookings
- Confirmed bookings
- Today's bookings
- Enquiries
- Rooms

Modules:

Rooms

CRUD operations.

Room Images

Upload/delete/manage images.

Amenities

CRUD.

Bookings

View/filter/update bookings.

Guests

View guest information according to permissions.

Gallery

Upload/manage images.

Reviews

Manage reviews.

Experiences

Manage Banaras experience content.

Enquiries

View/manage contact enquiries.

Settings

Manage:

- Hotel name
- Address
- Phone
- Email
- WhatsApp
- Social links
- Logo
- Favicon
- Footer content
- Booking settings

---

24. ADMIN UX

Admin UI should be completely different from the public website.

Use:

- Clean dashboard
- Sidebar navigation
- Responsive tables
- Search
- Filters
- Pagination
- Confirmation dialogs
- Toast notifications
- Empty states
- Loading states

Admin must work properly on tablets and desktop.

---

25. PHP ARCHITECTURE

Use reusable components.

Recommended structure:

/config
/includes
/components
/pages
/assets
/admin
/uploads

Suggested components:

header.php
footer.php
navbar.php
room-card.php
amenity-card.php
gallery-card.php
review-card.php
booking-widget.php
alert.php
pagination.php

Avoid duplicating HTML unnecessarily.

Use reusable functions for:

- Database queries
- Authentication
- Validation
- Sanitization
- Image handling
- Booking calculations
- Settings retrieval

---

26. SECURITY

Security is mandatory.

Implement:

- PDO or MySQLi prepared statements
- Password hashing using password_hash()
- password_verify()
- CSRF protection
- Server-side validation
- Input validation
- Output escaping
- Secure sessions
- Admin authentication
- Authorization checks
- Upload validation
- MIME/type validation
- File size limits
- Safe filenames
- Protection against path traversal
- Protection against SQL injection
- Protection against XSS
- Protection against CSRF

Never trust client-side validation alone.

Never store plain-text passwords.

Never expose database credentials in public files.

---

27. IMAGE UPLOAD SECURITY

Admin image uploads must:

- Validate MIME type
- Validate extension
- Restrict file size
- Generate safe filenames
- Prevent executable uploads
- Store outside sensitive executable paths where practical
- Generate optimized versions if possible

Support WebP where practical.

---

28. SEO

Every public page needs:

- Unique title
- Meta description
- Canonical URL
- One clear H1
- Semantic HTML
- Open Graph metadata
- Twitter/X metadata
- Image alt attributes
- Breadcrumbs where useful
- Structured data

Potential structured data:

Hotel
LocalBusiness
BreadcrumbList
Offer
Room-related structured data where appropriate

Do not add inaccurate structured data.

---

29. URL STRUCTURE

Use clean URLs.

Examples:

/
/rooms
/rooms/deluxe-room
/amenities
/experience
/experience/ghats
/gallery
/about
/contact
/booking
/privacy-policy
/terms
/cancellation-policy

Avoid unnecessary query strings for public content pages.

---

30. PERFORMANCE

Optimize for Core Web Vitals.

Requirements:

- Lazy-load below-the-fold images
- Responsive images
- WebP/AVIF where appropriate
- Proper image dimensions
- Avoid layout shifts
- Minimize JavaScript
- Defer non-critical scripts
- Avoid unnecessary libraries
- Optimize CSS
- Browser caching
- Gzip/Brotli where hosting supports it

Do not sacrifice usability for extreme optimization.

---

31. RESPONSIVE DESIGN

Mobile-first.

Support:

- 320px+
- Mobile
- Tablet
- Desktop
- Large desktop

Mobile requirements:

- Hamburger menu
- Sticky booking CTA
- Touch-friendly controls
- Swipe galleries
- Responsive forms
- Proper typography scaling
- No horizontal overflow

Test every page at mobile width.

---

32. ACCESSIBILITY

Follow practical WCAG principles.

Implement:

- Semantic HTML
- Keyboard navigation
- Visible focus states
- Proper form labels
- Accessible buttons
- Alt text
- Sufficient contrast
- ARIA only where needed
- Accessible modal/lightbox
- Error messages associated with fields

Do not rely only on color to communicate state.

---

33. MICRO-INTERACTIONS

Use subtle premium animations:

- Fade-up reveal
- Image hover zoom
- Button transitions
- Navigation transition
- Smooth scrolling
- Card hover effects
- Gallery transitions

Keep animations fast and elegant.

Respect prefers-reduced-motion.

Do not over-animate the site.

---

34. ERROR STATES

Create professional states for:

404 page:

THE PAGE COULD NOT BE FOUND

CTA:

RETURN HOME

Booking unavailable:

No rooms are available for the selected dates.

CTA:

TRY DIFFERENT DATES

Form error:

Please check the highlighted fields.

Server error:

Something went wrong. Please try again.

---

35. CONTENT RULE

Do NOT invent:

- Hotel awards
- Ratings
- Guest reviews
- Room facilities
- Exact distances
- Prices
- Hotel history
- Star classification
- Certifications
- Restaurant names
- Claims of proximity

When information is unavailable, use:

- Editable placeholder content
- Admin-configurable fields
- Clearly marked temporary content

The website must remain factually safe.

---

36. CONVERSION STRATEGY

Primary conversion:

BOOK NOW

Secondary conversions:

CHECK AVAILABILITY

CALL HOTEL

WHATSAPP

SEND ENQUIRY

Place CTAs naturally throughout the website.

Do not spam users with popups.

On mobile, make booking/contact actions easily accessible.

---

37. FOOTER

Create a premium footer containing:

Hotel Astha Grand

Short brand statement.

Quick Links:

Home
Rooms
Amenities
Experience
Gallery
About
Contact

Contact:

Address
Phone
Email
WhatsApp

Policies:

Privacy Policy
Terms & Conditions
Cancellation Policy

Copyright:

© 2026 Hotel Astha Grand. All Rights Reserved.

---

38. DESIGN SYSTEM

Create reusable design tokens for:

- Colors
- Typography
- Spacing
- Border radius
- Shadows
- Container widths
- Buttons
- Inputs
- Cards
- Badges
- Alerts

Maintain consistent UI across every page.

---

39. COMPONENT SYSTEM

Build reusable frontend components:

Header
Navbar
Hero
Booking Widget
Room Card
Room Gallery
Amenity Card
Experience Card
Review Card
Gallery Grid
CTA Banner
Contact Form
Footer
Modal
Toast
Breadcrumb
Pagination
Loading State
Empty State
Error State

Do not duplicate component code.

---

40. FRONTEND TECHNOLOGY

Preferred:

HTML5
CSS3
Vanilla JavaScript
PHP templates

Use JavaScript only where necessary.

Do not introduce React/Vue/Angular unless specifically required.

Avoid large UI libraries.

The website should remain easy to deploy on conventional PHP hosting/cPanel.

---

41. BACKEND TECHNOLOGY

Use modern procedural or lightweight MVC-style PHP architecture.

Recommended:

PHP 8.x compatible code.

Use PDO.

Separate:

- Configuration
- Database layer
- Business logic
- Presentation
- Admin logic

Do not put database queries everywhere inside HTML.

---

42. DATABASE-DRIVEN CONTENT

The following must be dynamically loaded from MySQL:

- Rooms
- Room images
- Amenities
- Prices
- Bookings
- Gallery
- Reviews
- Experiences
- Contact settings
- Hotel settings

Avoid hardcoding these values in templates.

---

43. BOOKING AVAILABILITY LOGIC

Availability must consider:

- Room inventory
- Existing confirmed bookings
- Selected check-in date
- Selected check-out date
- Number of rooms required

Avoid double-booking.

Use server-side availability validation immediately before booking confirmation.

Database transactions should be used where appropriate.

---

44. TESTING REQUIREMENTS

Before considering the website complete, test:

Frontend

- Navigation
- Buttons
- Forms
- Gallery
- Mobile layout
- Tablet layout
- Desktop layout

Booking

- Valid dates
- Invalid dates
- Same-day edge cases
- Room availability
- Guest validation
- Booking submission
- Duplicate submissions
- Booking reference

Admin

- Login
- Logout
- Unauthorized access
- CRUD
- Image upload
- Booking management

Security

- SQL injection attempts
- XSS
- CSRF
- File upload abuse
- Session handling

Performance

- Image optimization
- Mobile loading
- Layout stability

---

45. IMPORTANT DEVELOPMENT RULES

1. Do not create a fake visual-only website.
2. Build actual working PHP pages.
3. Build the MySQL schema.
4. Connect pages to the database.
5. Make rooms database-driven.
6. Make bookings database-driven.
7. Make gallery database-driven.
8. Make admin content manageable.
9. Keep the code modular.
10. Keep the design premium and uncluttered.
11. Do not invent hotel facts.
12. Make every important CTA functional.
13. Make forms actually submit and validate.
14. Build proper success/error states.
15. Keep the application deployable on normal PHP hosting.
16. Use secure coding practices.
17. Make the UI responsive from the beginning.
18. Do not leave critical functionality as fake buttons.
19. Use placeholder data only where actual hotel information has not yet been provided.
20. Keep all hotel-specific information easy to replace from the admin panel.

---

46. FINAL VISUAL EXPERIENCE

The final website should communicate:

HOTEL ASTHA GRAND

A Grand Stay in the Heart of Banaras

The visitor should immediately understand:

- What the hotel is
- Where it is
- What rooms are available
- What facilities are offered
- Why they should consider staying
- How to check availability
- How to contact the hotel

The visual experience should be:

Elegant + Warm + Modern + Premium + Indian + Timeless

---

47. IMPLEMENTATION ORDER

Build in this order:

STEP 1

Set up project architecture.

STEP 2

Create database schema and seed/demo data.

STEP 3

Create global design system.

STEP 4

Build header/footer/navigation.

STEP 5

Build homepage.

STEP 6

Build rooms listing.

STEP 7

Build dynamic room details.

STEP 8

Build amenities.

STEP 9

Build Banaras experience pages.

STEP 10

Build gallery.

STEP 11

Build contact/enquiry system.

STEP 12

Build booking engine.

STEP 13

Build admin authentication.

STEP 14

Build admin dashboard.

STEP 15

Build admin CRUD modules.

STEP 16

Implement SEO.

STEP 17

Implement security hardening.

STEP 18

Optimize performance.

STEP 19

Test responsive layouts.

STEP 20

Run final QA.

---

48. DELIVERABLE

At completion, provide:

1. Complete responsive website
2. PHP source code
3. MySQL database schema
4. SQL seed/demo data
5. Admin dashboard
6. Booking system
7. Contact/enquiry system
8. Image/gallery management
9. SEO implementation
10. Security implementation
11. README/setup documentation
12. Deployment instructions for conventional PHP/cPanel hosting

The final result must be production-oriented, maintainable, responsive, secure, SEO-friendly and visually premium.

Do not stop at a static homepage.

Build the complete Hotel Astha Grand website ecosystem according to this specification.