Budget: 10000 RUB Deadline: 7 days
Здравствуйте,
Никаких сложностей в сотрудничестве не будет, опыт есть, примеры предоставлю, есть возможность работать по договорам
Требуется за 5 дней натянуть дизайн на WordPress. Верстка должна быть адативная. Обязательны примеры работы на Wordpress где будет адаптивная верстка.
Сайт создается на иврите, нужно быть готовым к некоторым сложностям в связи с этим, хотя они минимальны.
В целом ищу человека для постоянного сотрудничества, и создания сайтов для Израиля.
Budget: 10000 RUB Deadline: 7 days
Здравствуйте,
Никаких сложностей в сотрудничестве не будет, опыт есть, примеры предоставлю, есть возможность работать по договорам
Budget: 200 USD Deadline: 15 days
Готов взять за интересный проэкт
писать в скайп Pokki15
наша работа:http://whspace.ru
Budget: 9000 RUB Deadline: 8 days
зделаю
Budget: 150 USD Deadline: 17 days
Готов обсудить детали проекта, есть опыт работы с сайтами на иврите, буду рад сотрудничеству.
Budget: 10000 RUB Deadline: 5 days
Готов к работе.
Budget: 10000 RUB Deadline: 5 days
Добрый день.
Ваш проект заинтересовал меня и потому хотелось бы с вами сотрудничать.
В моём профиле Вы можете ознакомиться с моими работами.
Жду вашего ответа.
Budget: 10000 UAH Deadline: 4 days
Здравствуйте! Готов приступить
Budget: 10000 RUB Deadline: 5 days
Готова обсудить детали.
Примеры своей работы покажу при личном общении.
______________________
С уважением, Юлия
Budget: 300 USD Deadline: 15 days
+
Budget: 300 USD Deadline: 20 days
Готов взяться. Для точной оценки нужно взглянуть на макет.
Budget: 10000 RUB Deadline: 5 days
Покажите макеты, можно и в jpg/png
Budget: 150 USD Deadline: 4 days
готов вам помочь
Budget: 10000 RUB Deadline: 5 days
Здравствуйте, готов выполнить Ваш проект.
Опыт работы в создании сайтов более 6 лет.
Сделаю качественно и в срок. Всегда на связи.
Ответственно отнесусь к Вашему проекту.
Обращайтесь,цену и сроки можно обсудить.
Работы в портфолио.
Budget: 100 USD Deadline: 5 days
Здравствуйте,готов выполнить ваш проект.
Примеры работ в портфолио.
Обращайтесь,буду рад сотрудничать - skype:dmitrii_antonenko22
Budget: 100 USD Deadline: 5 days
Здравствуйте! Готов заняться созданием шаблона под WordPress. Адаптивная верстка с использованием bootstrap, верстка под большинство устройств. Обращайтесь оговорим, своевременная демонстрация результатов на своем сервере.
Budget: 10000 RUB Deadline: 5 days
Готов выполнить ваш проект. Пример адаптивного сайта на Wordpress: http://agatha.s27.wh1.su/
Budget: 10000 RUB Deadline: 5 days
Здравствуйте. Мой скайп olejka222.
Последние адаптивные работы на вордпресс http://arcosgroup.by/arcos/ http://arcosgroup.by/
Пишите обсудим, сделаем в лучшем виде.
Budget: 10000 RUB Deadline: 7 days
Обращайтесь.
Skype - a.el_gringo
Пример - http://vokzal.in.ua
Budget: 400 USD Deadline: 21 days
Добрый день.
Я представляю компанию WebDevExp, специалисты нашей компании выполняют задачи любой сложности (особенно на WordPress). С радостью поможем в реализации данного проекта. Цена и сроки предварительные, более точные при согласовании.
Если хотите получить действительно качественный продукт - пишите.
Почта: [email protected]
Скайп: eugen.kasparov
Сайт с портфолио: webdevexp.net
С уважением менеджер компании WebDevExp Евгений.
К чему этот комментарий Виталий? Я покажу макет тому кто захочет работать.
А чего дублируете вакансию? Вы же ее размещали пол часа назад - https://freelancehunt.com/project/natyanut-psd-na-wordpress-nuzhna-adaptivnaya/105907.html
Ща получите бан за спам.
он сначала мне писал в скайпе, после того, как я попросил сбросить тз и макет в скайпе, он сказал -"вы мне не подходите". О адекватности заказчика я сделал свои выводы.
Виталий ) Что за женские ообиды? я обратился к Вам, но Вас надо уговаривать, Вы отвечаете очень нехотя, ну ладно покажите макеты, но не на емэил а в скайп и вообще я не знаю занят я или нет. Я принял решение что такой тип работы мне не подходит и все.
Спасибо ) И Вам всего хорошего. И не обижайтесь. Ну не понравились Вы мне в общении, а я не понравился Вам, зачем растягивать удовольствие? Тем более что я ищу человека для постоянного сотрудничества и мне должно быть комфортно и человеку тоже. Еще раз всего хорошего и удачных проектов.
Я недавно на этом сайте, не досмотрел что там работа "через сейф" а исправить уже было нельзя
за 5 дней вам сделают такое что будете потом переделывать, в общем деньги на ветер, наверно вам потому и уже накликали 7 спамов
а из опыта скажу что торопится как правило посредник
Странное мнение. Конечно, если на сайте 10+ полностью разных страниц с разным функционалом, можно и не успеть. Но для обычного сайта-визитки (предполагаю, в данном случае) это вполне приемлимые сроки
Единственное правильное решение если сомневаетесь с выбором, это смотреть портфолио исполнителя и читать отзывы тех с уже работал фрилансер.
а учитывая, что заявка не только на этом ресурсе, то заказчику прийдется немало потрудится в выборе исполнителя )))
Development of the Architecture for a Unified Fleet Management Platform for WordPress SitesProject Context There is a fleet of several dozen WordPress sites hosted on a single server and maintained by one team. The sites are gradually being transitioned to a unified development and support standard — a common design system with a unified block library (ACF + Gutenberg) and a unified security standard. An architecture is required for centralized management of this fleet.Task A technical architecture for a unified fleet management platform for WordPress sites needs to be developed. The platform is not a metrics dashboard, but a full-fledged system for centralized management and access.Platform Requirements Single Sign-On for Super Administrator — a single entry point for managing all sites in the fleet: overview of status, versions, compliance status. One-click access to the admin panel of each site — the ability to enter the wp-admin of any site in the fleet from a single interface, without storing/entering passwords for each site separately. A well-thought-out authentication mechanism is required (tokens with limited lifespan, binding to a specific user, complete access logging). Role Segmentation: the super admin sees and manages the entire fleet; administrators of individual sites have access only to their own sites. Unified Design System with Site-Level Customization — a common block library (ACF + Gutenberg), distributed to all sites through a central update mechanism, but with the ability for local customization of blocks for a specific site without losing compatibility with future updates of the library. Common Monitoring and Alert Dashboard — status of sites and server, alerts about outages/problems, update status and compliance of each site with respect to the unified standard. Convenient Addition of New Sites to the Network — the platform must support quick cloning/deployment of a new site based on a unified standard (Core plugin, design system) and connect it to the Hub with minimal manual steps.Architectural Constraints (Important) WordPress Multisite is not considered and is not suitable for this task. The reason is not the convenience of the interface, but the fundamental architectural properties of Multisite: A shared database and core for all sites in the network mean a single point of failure: an incorrect plugin or core update can simultaneously disable all sites in the network, not just one. A shared pool of server resources (PHP workers, database connections) means that abnormal load on one site (promotion, traffic spike, attack) degrades the performance of all other sites in the network, including those not related to this load. This systemic property of Multisite cannot be eliminated by process or discipline — therefore, an architecture is required where each site remains an independent installation (own database), and unification and centralized management are achieved by other means.Preliminary Architectural Direction Currently, the most promising architectural approach appears to be Hub & Spoke, where independent WordPress installations (“Spokes”), each with its own database, are united: by a common distributable Core plugin (block library, security baseline, bridge module for connection to the Hub); by a central management application (“Hub”) — site registry, one-click login, monitoring, alerts. However, this architecture is not a predetermined solution. If the executor believes that there is a more suitable architectural approach, they may propose an alternative provided it is technically and economically justified. A separate task within the terms of reference — a reasoned analysis and recommendation: to build the Hub from scratch custom or to take a ready-made self-hosted solution (MainWP, InfiniteWP, ManageWP or analogs) as a basis and expand it under specific requirements (integration with the Core plugin, compliance tracking of block versions, future marketing layer). A comparative assessment of timelines, support costs, flexibility, and limitations of each option is needed, with a clear recommendation.Architectural Requirements When designing the solution, the following non-functional requirements must be considered: fault tolerance and absence of a single point of failure for the fleet of sites; the ability for independent updating, rollback, and maintenance of each site; minimization of blast radius during failures and update errors; the ability for horizontal scaling as the number of sites grows; security of centralized management and delegated access; the possibility of subsequently isolating the Hub into a separate infrastructure without changing architectural principles; expandability of the platform for adding new centralized services. Moreover, the architecture must remain viable when the number of sites increases from several dozen to 100+ without the need for a fundamental revision of the chosen approach.Long-Term Development of the Platform The platform is viewed as a long-term foundation for the company's digital ecosystem, not just as a tool for administering WordPress sites. When designing, the possibility of subsequently adding centralized services (for example, managing marketing activities, analytics, component library, integrations, and other modules) without the need to rework the basic architecture must be considered.Technologies The specific stack is not predetermined — the executor independently proposes and justifies technologies in the architectural document (language/framework for the Hub, hosting/deployment model, authentication mechanism, etc.), based on the requirements of the task. A reasoned proposal for technologies is a mandatory part of the work result, alongside a comparison of custom vs ready-made solutions for the Hub.What is Required from the Executor Experience in designing multi-site/multi-tenant architectures on WordPress (principally — NOT based on Multisite) Practical experience with MainWP/InfiniteWP/ManageWP or similar fleet management systems — understanding their capabilities and limitations at the API/extendability level Experience in developing production-level WordPress plugins (ACF, Gutenberg block development, REST API) Understanding security issues when building centralized/delegated access systems (token-based auth, access auditing, minimizing blast radius) Ability to prepare architectural documentation: diagrams, API contracts between Hub and sites, data schemaWork Format The first stage — an architectural document with a reasoned solution (custom vs ready-made solution), a scheme of component interaction, API contract Hub ↔ Core plugin, phased implementation plan. The document should include a wireframe scheme of the platform interface (key screens: site registry, admin access, monitoring dashboard). Following the approval of the architecture — further cooperation may be possible. Important Note Independent architectural development is expected, based on practical experience in designing and operating similar systems. It is not sufficient to provide a compilation of general recommendations or standard responses generated by AI. Each key architectural decision must be accompanied by a technical justification: why this approach was chosen, what alternatives were considered, what its advantages, limitations, and potential risks are in the context of this project. If necessary, the executor should refer to practical experience, existing solutions, documentation, open-source projects, or other sources that confirm the viability of the proposed architectural solutions.
Hello! It is necessary to ensure that on the relevant pages, below the main text, a link is displayed which was specified in a separate field in the admin panel (on the same page) and styled with CSS.
It is necessary to add 129 products. There is an export file with the products, however, the standard import does not fit, as it is necessary to create the catalog structure before uploading: categories, sections, and if necessary, subcategories. After that, perform the product import and check that all cards are correctly distributed among the categories. If you have experience with similar tasks, please send examples of your work, completion times, and costs.
WHAT NEEDS TO BE DONE The work is divided into blocks; you can take on everything or individual blocks: Block 1 — Speed Optimization (Mobile-First) The current PageSpeed score for the mobile version is 51/100. It needs to be raised to 80+. Target metrics: LCP < 2.5 s (currently 7.4 s), FCP < 1.8 s (currently 3.9 s), TBT < 200 ms. Tasks: critical CSS inline, deferred JS, WebP/AVIF, lazy load, plugin audit. Block 2 — GTM and Analytics Remove hardcoded GA4/Google Ads scripts from header.php. Install and configure the GTM4WP plugin. Implement Google Consent Mode v2 (script or cookie banner). Block 3 — Product Card Template A single Mobile-First Single Product template in Elementor. Sticky "Buy" button while scrolling on mobile. Cross-sell block of services under the purchase button. Check the automatic transmission of events view_item, add_to_cart via GTM4WP. Block 4 — Product Feed for Google Merchant Center Install Product Feed Pro (AdTribes) or CTX Feed. Configure XML feed with correct field mapping (id, title, gtin, brand, price, availability). Daily updates via WP-Cron, auto-exclusion of products "out of stock". Block 5 — 6 Landing Pages in Elementor 3 e-commerce pages: catalog of components, ready solutions for UPS, SES kits. 3 lead generation pages: turnkey UPS installation, SES for home, solutions for business. There are detailed prototypes with the structure and blocks of each page. Block 6 — Forms and dataLayer Events 6 unique dataLayer events upon successful form submission (CF7 and Elementor Pro Forms). Mandatory requirements for all forms: phone input mask, protection against resubmission, reCAPTCHA v3 or Honeypot. --- REQUIREMENTS — Practical experience with Elementor Pro (Single Product templates, custom Page Templates) — Understanding of WooCommerce dataLayer and GTM4WP functionality — Experience in WordPress speed optimization (Critical CSS, WebP, WP Rocket or similar) — Experience in setting up dataLayer events for CF7 or Elementor Pro Forms — Portfolio or examples of similar work — mandatory Knowledge of Google Consent Mode v2 will be an advantage. --- WORK CONDITIONS The site is on live hosting — all changes only through staging or test duplicate. Any optimization should not disrupt the initialization of GTM and the dynamic dataLayer. A detailed technical specification will be provided after the first contact. Payment is staged by blocks or for the entire project (we will agree) Please write in your response: 1. Your experience with similar tasks (links or a brief description of the case) 2. Whether you are ready to perform the entire project or individual blocks 3. Estimated cost and timelines after reviewing the technical specification
Order description: We are looking for an experienced frontend developer/OpenCart specialist to optimize the loading speed of the website (categories and product cards) according to Google Core Web Vitals requirements. About the project: * CMS: OpenCart. * Specifics: The site operates in catalog mode (no cart or checkout). * Volume: 2900 items. * Server part: Already optimized (runs on OpenLiteSpeed). * Stack: Work is done exclusively with the template code, modifiers, and frontend. No work with the database. What needs to be done (Technical task): 1. Delayed loading of scripts (Delay JS): * Problem: Third-party analytics scripts (GTM, Google Tag) block the main thread on mobile devices for about 4.3 seconds. * Task: Set up delayed execution of these scripts. The scripts should activate strictly on the first user action (first scroll, tap on the screen, or mouse movement). * Important: Data collection, analytics, and ad functionality must remain intact. 2. Fixing the CLS metric (Layout Stability): * Problem: The page "jumps" and shifts during image loading. * Task: In the style files or theme template, hardcode the HTML attributes width and height for all product images in the catalog (listings) and product cards. * Goal: Reserve space for images in the DOM tree until they are actually loaded to prevent content shifting. Ensure that responsiveness (CSS) is not broken. 3. Optimization of the critical path (LCP): * Task: Add the fetchpriority="high" tag for the main product image on the first screen. This will instruct the browser to load the main product photo as a priority. Requirements for the performer and acceptance conditions: 1. No unnecessary modules: Work is performed with clean code/modifiers, without installing additional third-party or paid optimization plugins. 2. Security and layout: You are fully responsible for the layout. After making changes, the visual display of the site on mobile and PC, as well as functionality (filters, photo switching in the gallery, menu) must remain unchanged. 3. Criteria for job submission (DoD): Provide a screenshot and a link to a live test report from Google PageSpeed Insights (for the mobile version). The performance score must be no lower than 75 points, and the CLS metric must be no more than 0.1 (in the green zone). Changes must be made strictly through modifiers (OCMOD) or a copy of the theme to avoid overwriting core updates. In your response, please indicate: 1. Have you had experience configuring Delay JS specifically for GTM on OpenCart? 2. The estimated time for task completion. 3. The cost of the work.