Hennadii L.
Winning proposal- Projects 21
- Rating -
- Rating 1 862
Budget: 3500 UAH Deadline: 5 days
Good day !
Ready to perform today. I will do everything according to your requirements.
It is used by gulp/scss/flexbox/bem.
Examples of work in the protopoly
Freelancehunt
Budget: 3000 UAH Deadline: 7 days
Hello to you!
There is experience working with this type of task. I would like to know more details to assess the time and volume of work.
by admin by admin by admin by admin
Open to dialogue!
Budget: 10000 RUB Deadline: 15 days
Good morning Ivan. Please answer a few questions about your project:
Can I see the maquets? Which engine should the site be on? What kind of deedline?
I look forward to your feedback!
I also give examples of my work:
by barzota.agency/
by lga.kz
Smile-clinic-kherson.com
by levercost.ru
by reactm.ru
by reus-mobile.com
Budget: 200 UAH Deadline: 30 days
Ivan, a good day!
For a real assessment of time and cost, it is necessary to assess the volume of work.
Please send the design-make, then it will be possible to talk about real numbers.
In the rest, ready to make a valid cross-browser layer, using modern technologies: BEM, FlexBox, GridCSS
Send the mail and we can agree on the rest.
I will be happy to help!
- Projects -
- Rating -
- Rating 680
Budget: 1000 UAH Deadline: 10 days
Hello, you are ready to take your site. Ready to start today.
I would like to ask you: Do you have a detailed technical task? How much time is there for the implementation of the project? Can I see the model?
I look forward to your answer, thank you!
My last work:
HTTPS://barzota.agency/
by HTTPS://lga.kz
www.smile-clinic-kherson.com
by HTTPS://levercost.ru
HTTP://reactm.ru/
HTTPS://reus-mobile.com
PS: The price is fictitious until we discuss the details
Budget: 1000 UAH Deadline: 1 day
Hello to Ivan!
Send a link to the modes.
A clear and valid code.
Go to turn. Details will be discussed.
Budget: 700 UAH Deadline: 1 day
Good day, I will be happy to take your project. At the exit you will get an adaptive, cross-browser site. In work I use all modern technologies, exactly about the steak of technologies and examples of work can be read in the profile. The work is ready to begin today, but I would like to see the model itself to more accurately assess the time and cost.
Budget: 1000 UAH Deadline: 1 day
Good day !
Experience in front-end development.
The price and time of implementation after all details are agreed.
Contact us, we will discuss.
Budget: 1000 UAH Deadline: 1 day
Hello to you!
Ready to create an adaptive and cross-browser page.
For a precise assessment of the cost and deadlines, you need to look at the model.
I can start immediately. I do it quickly and efficiently, according to the current standards.
I will be happy to work with you.
Budget: 1500 UAH Deadline: 5 days
Good day, I can help you in the slope. I know HTML, CSS, SCSS, JS, JQuery. I will be pleased to cooperate
Budget: 1000 UAH Deadline: 3 days
Hello to you!
I make an adaptive and cross-browser web page.
Can I get acquainted with the modes?
For the correct assessment of the cost and deadlines, you need to read the model and TZ,
to present a clear structure and functionality.
Portfolio: Freelancehunt
With respect, Eugene.
Budget: 1000 RUB Deadline: 1 day
Hello to you. I can start work right now. I work from 9:00 to 22:00 (according to MSC). I’m going to contact Telegram, Weber, and Whatssup.
Budget: 900 UAH Deadline: 1 day
Welcome, you are ready to complete your order right now.
I'm ready to get to know the model in detail and get to start the wrap.
Budget: 3000 UAH Deadline: 14 days
Hello to you.
Ready to implement your project.
More accurate price and time of execution I can tell you after getting acquainted with the model.
Budget: 1000 RUB Deadline: 3 days
Good day Ivan! My work experience of more than a year, I have familiar with your TZ, ready to perform the layer quality and in time. I use modern technologies and tools. It will be adaptive, cross-browser and valid. I will be happy to collaborate, I propose to discuss the details at Ls!
Budget: 3000 UAH Deadline: 3 days
Hello to you. I offer my services from Figma. I have great experience with such work. From zero without buttraps, etc. valid, adaptive and crossbrowser. I usually do not ask questions during the work process. I am going to work immediately with the approval of the rate. The price and deadlines are indicated as indicative, the final will be after familiarization with the amount of work.
- Projects -
- Rating -
- Rating 180
Budget: 3000 UAH Deadline: 1 day
Good day Ivan! I am ready to start work immediately after getting acquainted with the makets. constantly in contact. Please tell me what deadlines are for implementation? I'll be happy to get you back, I'm looking forward to your reply at L.S.
Budget: 5000 RUB Deadline: 2 days
Good day .
I will be glad to help you.
To evaluate the dates and prices, you need to read the models.
You can see my work in my portfolio.
With respect, Babbage
Budget: 1234 UAH Deadline: 1 day
Good day . I will be happy to cooperate.
I am ready to discuss the details in a personal letter.
Great experience, responsible and quality approach.
Congratulations on Roman!
Write to discuss
Budget: 5000 UAH Deadline: 10 days
Good day . Of course, to evaluate it is desirable to look at the model for the beginning. The line of execution and the price are approximate. Qualitatively, the experience is really great. He worked at the office and as a freelancer.
Budget: 1500 UAH Deadline: 5 days
Hello to Ivan. You need to look at the design, to accurately assess the cost and deadlines. All the details can be discussed in Ls. Here is my, in my opinion and at the moment the best work on the wrap: https://alexkotsubo.github.io/maldives/
On contact from 10:00 to 18:00.
All of my work, guarantees, etc. you can find in my profile.
Proposals are currently absent
Current freelance projects in the category HTML & CSS
Есть действующий production-сайт с каталогом товаров, карточками моделей и информационными страницами. Стек frontend: — Next.js; — React; — TypeScript; — существующая компонентная система; — staging и production environments. Есть согласованное визуальное направление и дизайн новой главной страницы. Необходимо внедрить его в существующий проект, адаптировать под desktop/tablet/mobile и привести все основные типы страниц сайта к единой обновлённой стилистике. Полный редизайн продукта и изменение бизнес-логики не требуются. ОБЯЗАТЕЛЬНЫЙ SCOPE 1. Новая главная страница — реализовать главную страницу по предоставленному дизайну; — сохранить существующую функциональность, ссылки и маршрутизацию; — корректно подключить согласованные секции и CTA; — использовать существующие данные и API; — предусмотреть корректное отображение динамического контента. Основные типы секций: — header/navigation; — hero; — информационные блоки; — карточки моделей/предложений; — аналитические или market insight блоки; — CTA-секции; — footer. Точный состав секций будет предоставлен выбранному исполнителю вместе с макетом. 2. Responsive Необходимо реализовать: — desktop; — tablet; — mobile; — промежуточные разрешения; — корректное поведение сеток, карточек, меню, кнопок и типографики; — отсутствие горизонтального скролла и визуальных конфликтов. 3. Типографика и общие стили — внедрить новые согласованные шрифты; — привести размеры, веса, line-height и интервалы к единой системе; — обновить стили кнопок, карточек, полей, бейджей и заголовков; — по возможности использовать общие design tokens или CSS variables; — не дублировать стили отдельно для каждой страницы без необходимости. 4. Унификация существующих страниц Проверить и привести к новой стилистике основные типы страниц: — каталог; — карточка модели / PDP; — информационные страницы; — header; — footer; — формы; — модальные окна; — существующие CTA; — loading / empty / error states, если они уже присутствуют в проекте. Речь идёт о визуальной унификации существующих компонентов, а не о полном индивидуальном редизайне каждой страницы. 5. Каталог Проверить: — сетку карточек; — изображения; — название, reference и цену; — фильтры и сортировки; — кнопки и ссылки; — desktop/mobile отображение; — loading и empty states; — отсутствие визуальных сдвигов при загрузке. 6. PDP Проверить: — галерею; — основной информационный блок; — цену и CTA; — аналитические секции; — таблицы и метрики; — About Watch; — desktop/mobile компоновку; — длинные названия, references и отсутствующие данные. Необходимо сохранить текущую функциональность и существующие контракты API. 7. Header и Footer — единая стилистика на всех страницах; — responsive navigation; — mobile menu; — корректные active/hover/focus states; — отсутствие расхождений между главной, каталогом и PDP. 8. Состояния интерфейса Для динамических блоков проверить: — loading; — empty data; — API error; — insufficient data; — отсутствующее изображение; — отсутствующая цена; — длинный текст; — мобильное отображение. Не требуется разрабатывать новую сложную бизнес-логику. Необходимо корректно визуализировать уже существующие состояния. 9. Качество и производительность — не ухудшить SEO и текущую индексацию; — сохранить корректные metadata и semantic HTML; — не создавать критических layout shifts; — оптимизировать изображения и шрифты; — учитывать reduced motion для анимаций; — проверить базовую доступность: focus states, contrast, keyboard navigation; — не подключать тяжёлые библиотеки без обоснованной необходимости. 10. Staging и QA — развернуть изменения на staging; — проверить основные типы страниц; — проверить desktop, tablet и mobile; — устранить визуальные и responsive-баги; — после приёмки выполнить production deployment; — обеспечить исправление багов по реализованному scope не менее 7 календарных дней после выкладки. РЕЗУЛЬТАТ РАБОТЫ — Pull Request с frontend-кодом; — реализованная новая главная; — responsive desktop/tablet/mobile; — единые шрифты, карточки и базовые UI-компоненты; — визуально согласованные каталог, PDP и информационные страницы; — staging deployment; — исправление найденных визуальных ошибок; — production deployment; — краткое описание изменённых компонентов; — 7-дневный bug-fix period после приёмки. ACCEPTANCE CRITERIA 1. Главная соответствует предоставленному дизайну. 2. Все секции корректно работают на desktop, tablet и mobile. 3. Header и footer единообразны на всех страницах. 4. Каталог и PDP визуально соответствуют новой системе. 5. Текущая функциональность сайта не нарушена. 6. API-контракты и backend-логика не изменены без согласования. 7. Нет горизонтального скролла и критических layout shifts. 8. Шрифты и изображения загружаются корректно. 9. Loading, empty и error states отображаются без поломки layout. 10. Изменения проверены на staging и развернуты в production. 11. Исправлены визуальные ошибки, обнаруженные при приёмке в рамках согласованного scope. ЧТО НЕ ТРЕБУЕТСЯ — разработка backend; — изменение бизнес-логики; — создание нового каталога или CMS; — разработка нового API; — полный редизайн каждой информационной страницы; — новые пользовательские функции, отсутствующие в макетах; — разработка сложной дизайн-системы с нуля; — создание нового проекта вместо доработки существующего; — изменение SEO-структуры без отдельного согласования. ТРЕБОВАНИЯ К ИСПОЛНИТЕЛЮ — уверенный Next.js / React / TypeScript; — опыт работы с существующими production-проектами; — качественная responsive-вёрстка; — опыт внедрения дизайна из Figma; — компонентный подход; — уверенная работа с CSS / CSS Modules / Tailwind или существующей системой проекта; — понимание Core Web Vitals; — Git / Pull Request workflow; — умение работать через staging. В ОТКЛИКЕ ОБЯЗАТЕЛЬНО УКАЗАТЬ 1. Fixed price за полный обязательный scope. 2. Срок выполнения в рабочих днях. 3. Оценку в часах. 4. Когда готовы начать. 5. Ссылки на 2–3 релевантных проекта на Next.js/React. 6. Есть ли опыт работы с каталогами, карточками товаров или аналитическими интерфейсами. 7. Что потребуется для точной оценки до начала работы. 8. Входят ли в цену: — staging; — responsive QA; — production deployment; — исправление багов; — 7-дневный bug-fix period. Шаблонные отклики без просмотра требований и без конкретной оценки рассматриваться не будут. Доступ к production на первом этапе не предоставляется. Работа начинается после ограниченного code review и разворачивается через 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).