You need to make a 1 page.

TECHNICAL TASK Update of the online store bp.ua About the project An active online perfume store on OpenCart 2.x. It needs to be migrated to OpenCart 4.x, the design and functionality updated, while preserving all data, integrations, and SEO. The site is bilingual (Ukrainian + Russian). We are looking for a performer (or team) for backend and frontend. You can respond to one part or both.Part 1. Backend (OpenCart 4)Migration Deployment of a clean OpenCart 4.x (latest stable branch), PHP 8.1+. Data transfer: products, categories, attributes, options, brands, customers, orders, reviews, content pages. Preservation of SEO-URL (pretty URLs) one-to-one; a map of 301 redirects from old addresses. No direct upgrade from 2.x → 4.x: only clean deployment + controlled transfer.API integration with the supplier (priority) Porting existing custom exchange modifications with the supplier's server (prices + stock). Automatic synchronization on schedule (cron), error log, manual launch. Hiding/status for items that are out of stock. Support for a catalog of 2,000+ items.Modules Nova Poshta: selection of branches/parcel lockers, auto-generation of shipping documents from the admin panel. Payment: integration of payment system (LiqPay / Fondy / WayForPay — to be agreed), cash on delivery. Checkout: server logic, guest order, statuses, customer notifications. Mass import/update of products from the price list (xlsx/csv), linking photos by article/barcode.Bilingualism (uk / ru) Two languages of the store: uk-UA (main) and ru-RU. Bilingual fields for products, categories, content pages, meta tags. Separate SEO-URLs for each language, hreflang tags, canonical URLs. 301 redirects from old URLs of both languages (check the current scheme: /ru/, subdomain or parameter). Emails to the customer — in the client's session language.Blog Preserve the existing articles section https://blog.bp.ua/. Transfer existing articles (uk/ru) while preserving URLs and 301 redirects where necessary. Bilingualism, correct SEO markup of articles. The blog section must remain editable from the admin panel.SEO (server-side) Replacing third-party SEO module with native OC4 mechanism. Generating sitemap.xml (separate language branches), correct robots.txt. Microdata Schema.org (Product, Offer, BreadcrumbList, Article for the blog).Performance and security Cache (OPcache + built-in OC4), query optimization, gzip/brotli, HTTP/2. Images: WebP, resize with caching. HTTPS, 2FA in the admin panel, current patches, daily backups. Core Web Vitals in the "green" zone on mobile.Work order All work is conducted on staging. The old site operates until full testing of the new one. Switching to production — with the possibility of rollback for 30 days. Part 2. Frontend (design + layout)Design Style: minimalist, premium, lots of "air", focus on product photos. Mobile-first approach (most traffic is mobile). Design system in Figma: palette, typography, components, states. Mockups of key screens (desktop + mobile): homepage, catalog, product card, brand page, cart, checkout, search, blog, and article page.Layout Semantic HTML5, clean CSS, responsive (mobile-first). Integration into twig templates of OpenCart 4 (not static), working with live data. Images: WebP, lazy-load, srcset. Font with full Cyrillic (uk/ru). Cross-browser compatibility: Chrome, Safari, Firefox, Edge + iOS/Android. Core Web Vitals: LCP < 2.5 s, CLS < 0.1, INP < 200 ms (mobile).Interface functionality Facet filters for the catalog: brand, type, volume, note, gender, price. Product card: photo, description, notes, format/volume, reviews, "people also buy". Quick view, wishlist, comparison, badges (new, hit, limited quantity). Responsive checkout with minimal steps, auto-fill for Nova Poshta. Blog section: list of articles and article page in the site's style.Bilingualism (uk / ru) Language switcher in the header, correct on mobile. Layout considers different line lengths in both languages. All theme text — through language variables of OC4 (no "hardcoded" text). Acceptance and collaborationWhat to deliver upon completion Backend: access (server, DB, admin panel, repository), brief documentation on modifications and cron, deployment/rollback instructions, list of third-party modules. Frontend: Figma file with design system and screens, theme code (twig + CSS/JS), instructions for changing banners/content.Acceptance criteria (brief)

https://www.figma.com/design/bSzGOmDb3scdsBgjR3hHLb/Robo?node-id=0-1&p=f https://robo.org.ua/index.php?route=product/product&path=145802278&product_id=237 Task: redesign the product and reviews page on the main page The website is already developed and fully operational. The designer has prepared a new design in Figma that needs to be implemented on the existing site. It is necessary to: code the new design according to the layout; integrate it into the current site; adapt the pages for mobile devices, tablets, and computers; check the correct operation of buttons, forms, menus, and other elements; ensure maximum accuracy in matching the layout. There is no need to develop the site from scratch — only the redesign and replacement of the current design with the new one are required.

A virus has currently infiltrated the website. The site is not functioning properly. In particular, the main page is not working correctly. We need a developer who can fix this error as soon as possible.

There is a sales funnel for the online store that we want to replicate for ourselves. It looks like this: The main landing page (the product that is primarily for sale, for example, a shirt). Then the checkout page (where the person enters their details and chooses how many shirts they want to buy, for example). Then they go further down the funnel and are offered upsell 1 (socks) + then upsell 2 (underwear) and finally the thank you page. You can see how this should work in terms of page transitions and logic here (you need to get to the end to the thank you page) https://3plus3.heroman.com.ua/standard/. We have examples of pages that we want to create for ourselves. So for us, essentially, we will copy the design - layout - fill it in with our product. The upsell pages will have the same design and structure as on the site I shared above (underwear). You will not need to fill the pages with information, just gather the skeleton - so that the application comes through correctly. Also, you do not need to come up with the structure of the pages. From you, essentially: Copy and layout. Set it up to work technically correctly. Show how to work with this so we can do it ourselves. There are 2 website builders in mind, we are currently working closely with 1 and need to understand if we can deploy this on it (but I read in GPT that it is possible).

Task Need to create a stylish responsive email template based on the provided text and prepare it for upload to the email marketing service. What needs to be done Design the email. Code a responsive HTML email. Insert the provided text. Prepare blocks for images and icons. Add CTA buttons. Prepare links with UTM tags. Create a plain-text version of the email. Check rendering in major email clients. Prepare the final file for upload to the mailing service. Design Requirements A clean, modern, premium-style email is needed. The email should be easy to read, not overloaded, with a clear structure, short text blocks, visual accents, and several CTA buttons. Technical Requirements Responsive HTML email coding; Correct rendering on desktop and mobile; Table-based layout; Container width approximately 600–700 px; Inline CSS / email-compatible CSS; Buttons must be HTML/CSS, not images; All important data must be HTML text; Images must have alt text; No JavaScript; No forms inside the email; Links must work correctly; Preparation of UTM tags for CTA. Testing Need to check rendering in at least: Gmail; Apple Mail; Outlook; mobile email clients. Deliverables Ready HTML email file. Plain-text version. Preview or screenshots desktop/mobile. Instructions on where to change links, text, and images. File/version ready for upload to the mailing service. In your response, please attach examples of HTML email newsletters you have created and specify which mailing services you have worked with.