Web Designer & Developer for HVAC Service Landing Page

Ниже готовая версия на английском, очищенная от символов, которые Upwork запретил. Я также убрал стрелки и любые формулировки, которые могут выглядеть как внешние контактные данные. # WordPress Developer Needed for Modern HVAC Service Landing Page We are looking for an experienced WordPress designer and developer to build a modern, fast, conversion-focused website for an HVAC and ventilation service company in Estonia. ## Project Overview The current project is Phase 1, an MVP consisting of a professional one-page WordPress landing page based on an already prepared visual mockup. This is not a large corporate website, a full e-commerce store, or a complex web application. The goal is to create a professional production website where customers can: - understand the services offered - see starting prices - select a service - identify their ventilation unit when necessary - upload equipment photos - submit an order - request a quotation - select an available payment method We already have: - branding - logo - page structure - primary website copy - UX concept - service selection logic - filter selection logic - detailed visual mockup The attached mockup should be used as the main visual and UX reference for Phase 1. The developer may improve responsive behavior, usability, spacing, and minor UI details where appropriate, but a completely new design concept is not required. ## 1. WordPress Implementation The final result must be a fully functional, production-ready WordPress website. We are not looking only for a Figma design or a static visual reproduction of the mockup. The website owner should be able to edit normal content without programming knowledge, including: - text - prices - images - service descriptions - contact details - ventilation unit manufacturers - ventilation unit models Elementor, Bricks, Gutenberg, or another established and actively maintained WordPress solution may be used. Before development begins, please provide the proposed technical stack, including: - WordPress theme - page builder - form solution - proposed plugins - approach to custom functionality ## 2. Premium WordPress Templates Are Allowed We do not require a completely custom WordPress theme. A high-quality premium theme or template may be used if it allows the website to be built faster and more cost-effectively while closely matching the supplied mockup. We prefer a practical solution rather than rebuilding standard interface components from scratch when a reliable solution already exists. However, any proposed theme or template must be: - officially licensed - actively maintained - compatible with current supported WordPress versions - compatible with a modern supported PHP version - properly documented - supported by a public changelog - provided by an established vendor - reasonably lightweight - suitable for future maintenance The theme should not depend on a large number of obscure or abandoned plugins. Nulled, pirated, cracked, or unofficial themes and plugins are strictly prohibited. Before using or purchasing a premium solution, please disclose: - theme or template name - license cost - renewal cost if applicable - required premium plugins - any licensing limitations The selected solution should be approved before major customization begins. ## 3. Fragile or Improvised Page Builder Implementations Are Not Acceptable Using Elementor or another page builder is acceptable. However, we do not want a website that only visually reproduces the mockup while all business data and functionality are manually hard-coded into individual page builder sections. For example, adding a new ventilation manufacturer or model in the future should not require: - manually duplicating Elementor sections - editing the same information in several places - rebuilding dropdown lists manually - modifying multiple hard-coded widgets Manufacturer and model data must be implemented in a structured and maintainable way. We also want to avoid unnecessary dependence on: - multiple overlapping Elementor add-on packages - random code snippets - scattered inline JavaScript - excessive custom CSS fixes - fragile positioning hacks - unnecessary negative margins - poorly documented customizations Custom functionality must be implemented in an update-safe way. Important customizations must not be placed directly inside parent theme files if normal theme updates could overwrite them. Where appropriate, the developer may use: - a child theme - a custom plugin - structured custom fields - reusable components - another maintainable WordPress approach Normal WordPress, theme, and plugin updates should not remove project customizations or break the order process. ## 4. Header Phase 1 is a one-page landing website, so complex navigation is not required. The header should contain: - company logo - a clear contact or action element - primary CTA with the Estonian text Telli teenus The main CTA should smoothly move the visitor to the service selection and order section. Exact business and contact information will be provided after the project begins. The header must work correctly on desktop, tablet, and mobile. ## 5. Hero Section The hero section should clearly communicate: - what the company does - which main services are offered - the service region - how the customer can start placing an order The supplied mockup contains the intended Estonian content and visual direction. A high-quality image of a modern ventilation unit should be used as the primary hero visual. The hero section should remain clean, professional, modern, and easy to understand. ## 6. Trust Elements The hero area should include three concise trust indicators. Current examples are: Kogenud spetsialistid Kiire reageerimine 24 to 48 h Garantii tehtud töödele These should use simple icons and short text instead of large content blocks. ## 7. Service Selection Section heading: Mis teenus sobib sulle? The customer should be able to select one of three primary services. ### Diagnostika Starting price: 65 euros Description: Seadme kontroll ja rikete tuvastamine. ### Hooldus Starting price: 80 euros plus filters Description: Puhastus, kontroll ja seadistused. Filtrite vahetus on teenuse sees, filtrite maksumus lisandub. ### Filtrite vahetus Starting price: 40 euros plus filters Description: Õiged filtrid sinu seadmele ja professionaalne paigaldus. The entire service card must be clickable. When selected: - the card should have a clear active state - the radio or check indicator should change - a selected state such as Valitud should appear - the selected service should automatically be passed to the order form Only one primary service should be selected at a time. The customer must not be required to select the same service again later. ## 8. Pricing Information A short pricing disclaimer should be displayed below the service cards. Example Estonian wording: Hind sõltub seadme tüübist, ligipääsust ja tööde mahust. Lõplik hind selgub pärast objekti hindamist. The final Estonian wording will be confirmed before launch. ## 9. Conditional Ventilation Unit and Filter Selection If the customer selects Hooldus or Filtrite vahetus, an additional section should appear. Section title: Vali oma ventilatsiooniseadme filtrid The section should contain two main fields. ### Tootja Dropdown containing ventilation unit manufacturers. ### Mudel Dropdown containing the corresponding equipment models. The preferred behavior is that selecting a manufacturer limits the model list to models belonging to that manufacturer. For example, selecting Komfovent should display only relevant Komfovent models. The manufacturer and model structure should allow additional manufacturers and models to be added later without rebuilding the page. ## 10. Unknown Model Scenario Customers who do not know their ventilation unit model should be able to select: Ma ei tea seadme mudelit After this option is selected, an explanation should appear telling the customer that equipment photos can be uploaded instead. In this scenario: - manufacturer and model should no longer be mandatory - at least one equipment photo should become mandatory - the customer should not be forced to search for technical information they do not know This workflow must remain simple for non-technical customers. ## 11. No Duplicate Manufacturer or Model Entry If the manufacturer and model were already selected above, the customer should not be asked to enter the same information again in the order form. Instead, the form should display a summary. Example: Valitud seade Tootja: Komfovent Mudel: Domekt R400 The customer should have an option such as Muuda valikut to change the selection if necessary. ## 12. Order Form The main order form should be simple and conversion-focused. Suggested fields: - first and last name - phone - email - service address - preferred date and time - number of ventilation units - description or problem - automatically selected service - automatically selected manufacturer and model where applicable - photo upload The form must be particularly easy to complete on a smartphone. Previously entered information should not be requested again. ## 13. Photo Upload There should be one primary photo upload field inside the order form. Supported file formats: - JPG - JPEG - PNG - WebP Suggested limits: - up to approximately 5 files - up to approximately 10 MB per file If the equipment model is known, photos may remain optional. If the customer selects the unknown model option, at least one equipment photo must become mandatory. Ideally, customers should be able to upload: - a photo of the complete ventilation unit - a photo of the manufacturer data label - a photo of the existing filter or filter compartment File uploads must be securely validated on the server side. ## 14. Order and Payment Logic Phase 1 should support three customer scenarios. ### Immediate Online Payment Online payment should be available when the final payable amount is known. The planned payment solution is Montonio. Sensitive banking or card data must never be stored directly by WordPress. ### Pay by Invoice The customer submits the order without immediate online payment. The order can then be processed and invoiced separately. ### Request a Quotation The customer submits a quotation request without immediate payment. The primary CTA should automatically change according to the selected scenario. Exact final Estonian CTA wording will be confirmed during implementation. ## 15. Order Processing After successful form submission: - the customer should see a clear confirmation message - the complete request should be delivered to the website administrator - the selected service should be included - customer information should be included - service address should be included - manufacturer and model should be included where applicable - uploaded files should be securely accessible - the selected order or payment method should be included Preferably, submissions should also be stored securely inside WordPress Admin so that orders are not lost if an email notification fails. ## 16. Contact CTA The website should include a clearly visible contact or action CTA on desktop and mobile. Exact contact information and external communication configuration will be provided after the project begins. A compact sticky CTA may be used on mobile if it improves conversion without interfering with form completion. ## 17. Additional Trust Section Before the review section, include a compact trust block. Current examples: Kiire vastus 24 to 48 h Kvaliteetne töö ja hooldusakt Selged hinnad, ilma üllatusteta The design should remain simple and visually clean. ## 18. Reviews The website architecture should allow verified customer reviews to be displayed later. Fake reviews or fabricated ratings must not be published as genuine customer reviews on the production website. Temporary visual placeholders may be used during development only. ## 19. Footer The footer should follow the dark navy visual direction shown in the supplied mockup. It should support: - company description - contact information - service area - opening hours - privacy policy - cookie settings where required - terms of service where applicable Exact company information will be provided after the project begins. The copyright year should preferably update automatically. ## 20. Responsive Requirements The website must work correctly on: - desktop - tablet - mobile Support viewport widths from approximately 320 pixels and above. The following are not acceptable: - horizontal scrolling - overlapping elements - clipped forms - broken service cards - unreadable dropdowns - excessively small touch targets - layouts that work only at one specific resolution Testing should include current versions of: - Chrome - Safari - Firefox - Edge ## 21. Performance and Core Web Vitals The website must be technically optimized, not only visually polished. Target Lighthouse and PageSpeed Performance at launch: - mobile: 90 or higher - desktop: 95 or higher Target Core Web Vitals: - LCP: 2.5 seconds or better - INP: 200 milliseconds or better - CLS: 0.10 or better These should be considered launch targets under reasonable production hosting conditions and excluding third-party services outside the developer's control. Images should be: - correctly sized - properly compressed - preferably served as WebP or AVIF where appropriate Images below the initial viewport should use lazy loading. Avoid unnecessary: - large JavaScript libraries - heavy animations - excessive third-party scripts - excessive plugins Simply installing a cache or speed optimization plugin without properly optimizing the website does not satisfy this requirement. ## 22. Plugin Policy Before development begins, please provide the complete proposed plugin list. We prefer a minimal number of established and actively maintained plugins. Avoid installing several overlapping Elementor or page builder add-on packages simply to obtain individual UI widgets. Where functionality can reasonably be implemented using: - native WordPress features - the selected theme or builder - one reputable plugin - a small maintainable custom solution this is preferred over multiple unnecessary plugins. ## 23. Basic Technical SEO Phase 1 should include: - one primary H1 - logical H2 and H3 structure - title tag - meta description - descriptive image alt attributes - XML sitemap - robots configuration - canonical URL - Open Graph metadata - appropriate Organization or LocalBusiness structured data The production website must be technically indexable by search engines. ## 24. Security Minimum requirements include: - HTTPS - server-side form validation - spam protection - secure file upload validation - allowed file type restrictions - basic WordPress hardening - backup and restore capability Themes and plugins must come from official sources and receive ongoing maintenance and security updates. ## 25. Privacy and GDPR Only personal information genuinely required to process a customer request should be collected. The implementation should support: - Privacy Policy - cookie consent and cookie settings where legally required - appropriate consent for optional analytics or marketing technologies Unnecessary tracking scripts should not be added without approval. ## 26. Theme and Template Quality Requirements If an existing premium theme or template is used, it must: - be officially licensed - be actively maintained - have current documentation - provide a public changelog - come from an established vendor - support current WordPress versions - support modern PHP versions - remain reasonably lightweight The website must remain safely updateable after handover. The developer must disclose required paid licenses and ongoing renewal costs before purchase. ## 27. Update-Safe Requirement This is an important project acceptance criterion. Before final acceptance, the following should be performed on the staging website: 1. Create a full backup. 2. Install the available current WordPress, theme, and plugin updates. 3. Retest the page layout. 4. Retest service selection. 5. Retest conditional equipment and filter selection. 6. Retest manufacturer and model functionality. 7. Retest the order form. 8. Retest file uploads. 9. Retest the payment workflow. Normal updates must not remove project customizations or break the order process. ## 28. Staging and Production Workflow Development should be performed on a staging environment. The production website should not be used as the main experimental development environment. Once the staging version has been approved, the website should be deployed to the production environment. Production hosting and domain access will be provided after the project begins. After deployment, the developer must retest: - forms - notifications - payment workflow - HTTPS - responsive layout - PageSpeed - search engine indexability settings ## 29. Project Handover At project completion, the client must receive: - full WordPress administrator access - control over the website - relevant configuration information - access information for required premium licenses - any custom code required for future maintenance The website must not critically depend on the freelancer's personal account. If paid licenses are used, it must be clear who owns them and how the client can independently renew them later. Please also provide a short written or video guide explaining how to: - edit text - change a price - replace an image - edit a service - add or edit a manufacturer - add or edit an equipment model ## 30. Phase 2, Future Expansion Phase 2 is not included in the current fixed-price scope. In the future, the website may be expanded with: - full navigation and additional pages - separate journeys for private customers, business customers, and apartment associations - ventilation filter catalogue - manufacturer, model, and compatible filter relationships - additional services - shopping cart and checkout - multilingual support - expanded e-commerce functionality Phase 1 should therefore be built so that these features can be added later without rebuilding the entire website from scratch. However, there is no requirement to build the full Phase 2 infrastructure now unless there is a clear technical benefit for Phase 1. ## Phase 1 Deliverables The final Phase 1 deliverable should include: - fully functional WordPress landing page based on the supplied mockup - desktop version - tablet version - mobile version - service selection functionality - conditional equipment and filter selection - structured manufacturer and model functionality - unknown model workflow - photo uploads - order form - three order and payment scenarios - Montonio payment integration - administrator notifications - basic technical SEO - basic security configuration - performance optimization - staging testing - production deployment The final website must be: Stable, editable, maintainable, update-safe, responsive, fast, and production-ready. ## What to Include in Your Proposal Please provide: - 3 to 5 live WordPress projects that you personally built - preferably service-business, booking, HVAC, home-service, or e-commerce examples - examples of conditional or dynamic forms - experience with payment integrations - proposed WordPress technical stack - proposed theme or page builder - proposed form solution - complete proposed plugin list - your approach to manufacturer and model functionality - fixed-price estimate for Phase 1 - estimated delivery time - required paid licenses and their costs Please also answer these two questions. Question 1: How would you implement the ventilation manufacturer and model selection so that new manufacturers and models can be added later without rebuilding or manually duplicating page-builder sections? Question 2: How will you ensure that WordPress, theme, and plugin updates do not remove or break the custom functionality? ## Important Project Principle We are not looking for the most complicated or most expensive technical solution. We want a practical and professional MVP that can be launched relatively quickly and expanded later. Using a high-quality premium WordPress template is completely acceptable and may be preferable if it reduces development time and cost. However, a fragile implementation that only visually reproduces the mockup but relies heavily on hard-coded page-builder blocks, excessive plugins, CSS hacks, or other poorly maintainable solutions is not acceptable. The website should remain stable, editable, and maintainable after normal WordPress, theme, and plugin updates and future business growth.