Budget: 500 UAH Deadline: 2 days
Обращайтесь!
http://dancingcolorsart.jimdo.com/
Требуется разработать продающее письмо с красивой графикой которое будет включать преимущества нашей компании перед другими компаниями в нашем сегменте, для ответа клиентам при подписке на сайте.
Budget: 500 UAH Deadline: 2 days
Обращайтесь!
http://dancingcolorsart.jimdo.com/
Budget: 300 UAH Deadline: 2 days
Стоимость предварительная. Нужно больше подробностей.
Примеры работ: Behance
Budget: 350 UAH Deadline: 2 days
Готова взяться за проект
портфолио в профиле
Для обсуждения деталей
пишите [email protected]
скайп k_nadin_s
Budget: 1 UAH Deadline: 1 day
Сколько платите?
Budget: 500 UAH Deadline: 1 day
Добрый день! стоимость указана за дизайн, если нужна еще и верстка, то стоимость умножаем на два. Работа до полного выполнения, обращайтесь)
Budget: 1 UAH Deadline: 1 day
+
Budget: 500 UAH Deadline: 3 days
Здравствуйте.
Разработаю Вам дизайн продающего e-mail письма для рассылки, со всеми Вашими пожеланиями.
Обращайтесь.
Портфолио: Freelancehunt
Мои контакты:
skype: b-w-d-g
icq: 682722220
qip: [email protected]
e-mail: [email protected]
Всегда на связи.
Вопрос, на самом деле чуть глубже чем подпись в почте. Готов обсудить нюансы по скайпу, мой zl.malysh.
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.