Password for 1 page website

There is an active production site with a product catalog, model cards, and informational pages. Frontend stack: — Next.js; — React; — TypeScript; — existing component system; — staging and production environments. There is an approved visual direction and design for the new homepage. It is necessary to implement it into the existing project, adapt it for desktop/tablet/mobile, and bring all main types of pages on the site to a unified updated style. A complete redesign of the product and changes to business logic are not required. MANDATORY SCOPE 1. New homepage — implement the homepage according to the provided design; — maintain existing functionality, links, and routing; — correctly connect approved sections and CTAs; — use existing data and APIs; — ensure correct display of dynamic content. Main types of sections: — header/navigation; — hero; — informational blocks; — model/offering cards; — analytical or market insight blocks; — CTA sections; — footer. The exact composition of sections will be provided to the selected performer along with the layout. 2. Responsive It is necessary to implement: — desktop; — tablet; — mobile; — intermediate resolutions; — correct behavior of grids, cards, menus, buttons, and typography; — absence of horizontal scrolling and visual conflicts. 3. Typography and general styles — implement new approved fonts; — unify sizes, weights, line-height, and spacing; — update styles for buttons, cards, fields, badges, and headings; — use common design tokens or CSS variables where possible; — avoid duplicating styles separately for each page unnecessarily. 4. Unification of existing pages Check and bring to the new style the main types of pages: — catalog; — model card / PDP; — informational pages; — header; — footer; — forms; — modal windows; — existing CTAs; — loading / empty / error states, if they are already present in the project. This is about the visual unification of existing components, not a complete individual redesign of each page. 5. Catalog Check: — card grid; — images; — name, reference, and price; — filters and sorting; — buttons and links; — desktop/mobile display; — loading and empty states; — absence of visual shifts during loading. 6. PDP Check: — gallery; — main information block; — price and CTA; — analytical sections; — tables and metrics; — About Watch; — desktop/mobile layout; — long names, references, and missing data. It is necessary to maintain current functionality and existing API contracts. 7. Header and Footer — unified style across all pages; — responsive navigation; — mobile menu; — correct active/hover/focus states; — absence of discrepancies between the homepage, catalog, and PDP. 8. Interface states For dynamic blocks, check: — loading; — empty data; — API error; — insufficient data; — missing image; — missing price; — long text; — mobile display. There is no need to develop new complex business logic. It is necessary to correctly visualize already existing states. 9. Quality and performance — do not worsen SEO and current indexing; — maintain correct metadata and semantic HTML; — avoid critical layout shifts; — optimize images and fonts; — consider reduced motion for animations; — check basic accessibility: focus states, contrast, keyboard navigation; — do not include heavy libraries without justified necessity. 10. Staging and QA — deploy changes on staging; — check main types of pages; — check desktop, tablet, and mobile; — fix visual and responsive bugs; — after acceptance, perform production deployment; — ensure bug fixes for the implemented scope for at least 7 calendar days after deployment. RESULT OF WORK — Pull Request with frontend code; — implemented new homepage; — responsive desktop/tablet/mobile; — unified fonts, cards, and basic UI components; — visually agreed catalog, PDP, and informational pages; — staging deployment; — fixing identified visual errors; — production deployment; — brief description of modified components; — 7-day bug-fix period after acceptance. ACCEPTANCE CRITERIA 1. The homepage matches the provided design. 2. All sections work correctly on desktop, tablet, and mobile. 3. Header and footer are uniform across all pages. 4. Catalog and PDP visually correspond to the new system. 5. Current functionality of the site is not disrupted. 6. API contracts and backend logic are not changed without agreement. 7. No horizontal scrolling and critical layout shifts. 8. Fonts and images load correctly. 9. Loading, empty, and error states are displayed without breaking the layout. 10. Changes are checked on staging and deployed to production. 11. Visual errors identified during acceptance are fixed within the agreed scope. WHAT IS NOT REQUIRED — backend development; — changes to business logic; — creation of a new catalog or CMS; — development of a new API; — complete redesign of each informational page; — new user features not present in the layouts; — development of a complex design system from scratch; — creation of a new project instead of improving the existing one; — changes to the SEO structure without separate agreement. REQUIREMENTS FOR THE PERFORMER — confident in Next.js / React / TypeScript; — experience working with existing production projects; — quality responsive layout; — experience implementing designs from Figma; — component approach; — confident working with CSS / CSS Modules / Tailwind or the existing project system; — understanding of Core Web Vitals; — Git / Pull Request workflow; — ability to work through staging. IN RESPONSE, IT IS MANDATORY TO INDICATE 1. Fixed price for the full mandatory scope. 2. Completion time in working days. 3. Estimate in hours. 4. When you are ready to start. 5. Links to 2–3 relevant projects on Next.js/React. 6. Experience working with catalogs, product cards, or analytical interfaces. 7. What will be needed for an accurate estimate before starting work. 8. Does the price include: — staging; — responsive QA; — production deployment; — bug fixes; — 7-day bug-fix period. Template responses without reviewing the requirements and without a specific estimate will not be considered. Access to production is not provided at the first stage. Work begins after a limited code review and is deployed through staging.

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).