Budget: 3000 UAH Deadline: 7 days
Здравствуйте. Работаю на OpenCart 3. Обращайтесь. Telegram: +380939975696
Нужно разработать на шаблоне OpenCart интернет-магазин с оплатой и доставкой.
Есть пример структуры по которой нужно настроить новый шаблон. Но думаю что лучше подобрать 5 шаблонов на выбор, а там уже посмотрим.
Жду Ваши предложения и сроки.
Budget: 3000 UAH Deadline: 7 days
Здравствуйте. Работаю на OpenCart 3. Обращайтесь. Telegram: +380939975696
Budget: 5000 UAH Deadline: 14 days
Добрый день!
✅ Есть опыт в разработке сайтов
✅ Заинтересовал ваш проект!
✅ Давайте обсудим детали.
✅ Буду рад сотрудничеству)
Budget: 3000 UAH Deadline: 4 days
Добрый день! Готов сотрудничать. Большой опыт.
Готов обсудить детали и приступить к работе. Обращайтесь.
Budget: 6000 UAH Deadline: 30 days
Добрый день! Имею большой опыт работы с разработкой интернет магазинов портфолио можно посмотреть на:
https://rubik.com.ua/
Хочу предложить вам не шаблонный интернет магазин, ибо Сео-оптимизация таких магазинов трудно настраиваемая, со своим дизайном такой магазин будет примерно от 400$.
Связаться можно через сайт оставив заявку, или позвонив
с 11:00 до 18:00 по номеру: +38 (099) 362 69 47
Или же написав в телеграмм: @agenpel
Design a letter for sending to clients (an example is attached), I will provide the text and the top image. This is just an example from GPT, could you make it more interesting?
What is needed: responsive layout (mobile-first), interactivity (model switcher, ROI calculator, comparison table, quiz selection), form with CRM integration and UTM tags, analytics setup, speed optimization. Design and layout: implement the website in our corporate style according to the technical specifications and brand book, adhere to corporate colors (accent orange CTA buttons), fonts, header style, and overall premium look of the brand. A consistent visual style across all screens, neat spacing and typography, quality work with photos and tables. We are ready to provide a design mockup, a color/font guide, and examples.
Hello, I need your help in implementing a task. Fix the bugs on the website page, the page displays a 404 error.
It is necessary to connect the application form on the landing page to keycrm. I will provide all necessary access. Please write how much time and cost this task will take.
Website for evaluation: https://copy.eurobrands-shop.de/ Task: fix frontend bugs at the Magento 2 / Amasty theme level: CSS/LESS/JS, mobile, RTL, minicart, language dropdown, layout shift/CLS. Work format: - without local Magento deployment; - work through DevTools + theme source files; - edits in CSS/LESS/JS/template files of the theme; - result: diff / commit / archive of changed files; - deployment and assembly on our side; - work through a secure deal; - NDA until the transfer of source files/accesses. What needs to be checked and evaluated: 1. RTL / Arabic version: - phone in the header is displayed incorrectly; - element offsets in header, minicart, wishlist/account, product page; - margins, direction, unicode-bidi, positioning. 2. Header: - language dropdown; - cart/wishlist; - hit-area of icons. 3. Minicart: - opens unstably on some pages; - check Console / Network / Event Listeners / customer-data / z-index / overlay. 4. Mobile: - cart/wishlist badges are too large; - Categories block is compressed/cut off; - mobile menu / Menu-Account. 5. Product page: - layout shift / CLS of images; - Add to Cart / Quantity / BOX / PALLET in RTL. 6. Wishlist/account: - /wishlist/ - /mwishlist/ - tabs, Back button, overflow of counters. Problematic URLs: - https://copy.eurobrands-shop.de/alpro - https://copy.eurobrands-shop.de/producers - https://copy.eurobrands-shop.de/wishlist/ - https://copy.eurobrands-shop.de/mwishlist/ In your response, please write: 1. Do you have experience with Magento 2 frontend? 2. Do you have experience with RTL? 3. How many hours do you need for the first stage? 4. What is the cost? 5. When can you start? 6. What accesses do you need? 7. Are you ready to work through a secure deal and sign an NDA? Important: a specific result is needed — corrections or a technical explanation for each point: fixed / not reproducible / not a frontend issue.