Serhii Zasadinsky
Winning proposal- Projects 29
- Rating 5.0
- Rating 2 013
Budget: 5000 UAH Deadline: 7 days
Let’s write, discuss the details and begin the work.
Quality is guaranteed. Waiting for feedback
Budget: 4000 UAH Deadline: 5 days
I do according to TZ and in time for clarification and agreement of the details write ls.
Budget: 4000 UAH Deadline: 5 days
Hi, I have met the makets and tz. I will do everything in time. I will be happy to cooperate.
Budget: 4000 UAH Deadline: 7 days
Good night, I will do it according to tz and makets. I will be happy to cooperate
Proposals concealed
Proposals are currently absent
Proposals concealed
-
Veronika Ovlieva
21 June 2020
это важный критерий языка для возможности подключения к трекеру (его особенность)
-
Veronika Ovlieva
21 June 2020
это важный критерий языка для возможности подключения к трекеру (его особенность)
-
Nikolay Ryzhenko 21 June 2020Вы же мне в телеге обещали скинуть макеты, так и не скинули, и тут проект опять выкинули, что за люди пошли)
-
Sergey Aleksandrov 21 June 2020Дизайн за кусочек хлеба рисовался? Как из 90х, главное побольше картинок , что бы вообще терялся взгляд от целевого текста
Current freelance projects in the category HTML & CSS
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?
Landing Page Development
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.