Refinement of PWA for a fast food cafe chain + app compilation

Project Overview We are looking for an experienced Make.comautomation specialist to help us build one additional automation for our existing workflow. Our business already has several Make.com automations connected with Monday.com, so the overall system is already in place. We only need assistance with this specific automation, ensuring it integrates smoothly with our current setup.Workflow When a client reaches a specific status in Monday.com: Detect the new client in Monday.com. Read the following fields from the board: Client Name Email Address Client Portal URL (Notion) Populate our existing HTML welcome email template with those dynamic values. Automatically send the personalized email to the client. (Optional) Update the Monday.com item to indicate that the Welcome Email has been sent.Current Setup We already have: Monday.com CRM Make.com automations Client Portal links stored in Monday.com Existing email template We only need help creating this single automation and integrating it into our existing automation ecosystem.Tech Stack Make.com Monday.com MailchimpDeliverables Fully functional Make.com scenario Dynamic mapping of all fields Error handling for missing information Duplicate email preventionRequirements Strong experience with Make.com Experience building Monday.com automations Good English communication Estimated Timeline 2–4 hours

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)

Good day, there is a feed with products in the following format: we need to upload them to the website and ensure that the maximum number of products are indexed by Google. I will send the details privately.

Hello! We are looking for a person that can create Elementor website from figma. Figma file - https://www.figma.com/design/oZbnOEiWFrNtWVMXp4oc1K/CODY-x-Sprendimai?node-id=0-1&t=NB2DtJ589hB4jvOv-1 I think its self explainatory, but we had one accident in this platform so i just want to remember - DO NOT CONTACT CLIENT/US DIRECTLY FROM CONTAS IN FIGMA FILE Main things - It can be fully elementor page, without ACF etc. All plugins/starting theme will be provided. All typography, colors, spacing (padding and margins), buttons, and other global styles should be configured in Elementor Site Settings (Style Kit). This ensures that if the client adds new text, sections, or pages in the future, they will automatically match the existing design without requiring additional styling or adjustments. There is desktop + Mobile, both of them should be pixel perfect as possible, adapted to most of the breakpoints. Developer should be speaking English, as sadly, we didn't learn UA language (yet :) ).

Development of a similar functionality - CMS or custom-built is required. There is a store to be used as a basis - bnwtech.com.ua Important: - multilingual support - product filtering - clear import - duplication of requests in Viber/Telegram - role-based access to the admin panel Detailed information upon request