LIFE CONVERT WEBSITE — DEPLOYMENT README ======================================== PACKAGE CONTENTS - index.html: Home page with slider, service cards, portfolio preview, and enquiry form - about.html: Brand story, mission, vision, core values, services, process - portfolio.html: Filterable practice/concept project gallery with detail dialogs - contact.html: Contact details and enquiry form - send-message.php: Server-side validation, honeypot, and mail() handler - 404.html, favicon.svg, robots.txt, sitemap.xml, .htaccess - assets/css/style.css, assets/js/main.js, assets/icons/*.svg HOSTING / DEPLOYMENT 1. Correct the destination email in send-message.php before publishing. The supplied address `info@.mylifeconvert.com` appears malformed. It has deliberately been kept as a provisional value and the PHP handler will refuse to claim success until it is corrected. Do not launch the form without confirming the real mailbox. 2. Replace `YOUR-DOMAIN.example` in canonical tags, robots.txt, and sitemap.xml with the production HTTPS domain. Each page currently uses a placeholder canonical URL. 3. Upload the contents of this ZIP (not a nested enclosing folder) into the domain's `public_html` directory using Hostinger File Manager or FTP. 4. Confirm PHP is enabled on the hosting plan. Test with a verified recipient email. Host mail() behavior depends on the hosting provider's mail configuration. For production, use Hostinger-supported SMTP if available and store credentials outside the public web root; this package does not include SMTP credentials. 5. Replace the generic Instagram, LinkedIn, and YouTube placeholder destinations in index.html and the footer in the HTML pages with the actual Life Convert profile URLs. 6. Confirm the phone number and all contact details before publishing. 7. Test page navigation, form validation, submission success/failure, 404 behavior, mobile menu, portfolio filtering, and image loading on the live domain. 8. Run Lighthouse / PageSpeed Insights after deployment. No performance score is claimed because the deployed environment has not been measured in this build environment. IMAGES AND EXTERNAL ASSETS Photographs are loaded from stable Unsplash image CDN URLs and require an internet connection in visitors' browsers. They have not been downloaded into this package because outbound downloads were unavailable in the build environment. This also means the site is not fully self-contained for photography. If you require a no-external-asset deployment, download the relevant photographs from their Unsplash pages after checking the current license and replace the CDN URLs in the HTML with local WebP files under assets/images/. CSS loads DM Sans and Manrope from Google Fonts, with local system-font fallbacks. IMAGE-SOURCE RECORD - Hero / planning notebook: https://unsplash.com/photos/ (CDN photo ID photo-1455390582262-044cdead277a) - Creative workspace: CDN photo ID photo-1523726491678-bf852e717f6a - Analytics / digital work: CDN photo ID photo-1460925895917-afdab827c52f - Collaboration / about: CDN photo ID photo-1521737711867-e3b97375f902 - Branding visual: CDN photo ID photo-1558655146-9f40138edfeb - Website development: CDN photo ID photo-1498050108023-c5249f4df085 - Portfolio sample visuals: photo IDs photo-1516321318423-f06f85e504b3, photo-1545235617-9465d2a55698, photo-1432888622747-4eb9a8efeb07, photo-1467232004584-a241de8bcf5d Verify each photo's current source page and licensing at Unsplash before making commercial use. FUNCTIONALITY NOTES - Hero carousel, mobile navigation, category filters, project detail dialog, and reduced-motion handling are implemented in vanilla JavaScript. - PHP performs server-side field validation and checks for a honeypot value. It uses the host's mail() facility after the recipient address is made valid. SMTP deliverability must be tested. - Portfolio examples are explicitly identified as concept / practice work; no client outcomes, testimonials, awards, or performance metrics are fabricated. - This package has been checked for expected files and internal page links. It has not been run on a Hostinger server, and the PHP mail handler cannot be verified without server configuration.