DH: Build Elementor templates using signed-off Figma Design -- (fixed)

Hello. I am seeking an experienced Elementor Pro developer to build Templates for a multipage WordPress website (example layout attached) The final templates should be authentic, pixel-perfect, and fully responsive designs covering the 7 standard breakpoints used in Elementor (see below). Up to two review cycles should be allowed. We provide access to a fully licensed and optimized staging environment to which the developer will have Admin access. The tech stack for this project includes Elementor Pro and Gravity Forms THEME - Custom Figma design TEMPLATES RQD (6) - Header, Footer, Single Page, Single Post, Archive, 404 PAGES RQD (9) - Home, About, Services (3), Courses (placeholder), Privacy, Contact IMAGES RQD - None. All media assets provided ELEMENTOR-SPECIFIC GUIDELINES 1. Theme: Elementor Hello and Child 2. Default kit to be created for items including Global Colours, Fonts, Typography, Buttons etc 3. Headings: Use H1, H2, H3, etc, NOT Element Styling, Page Level, or Inline CSS styling 4. Element Styling: Must be default and link to Default Kit ie. Settings > 5. Additional CSS: MUST be saved as Custom Code ie. Elementor > Custom Code and NOT Customr CSS ie. Appearance > Customise > Additional CSS 6. Elementor Templates: Must build using TEMPLATES ie. Templates > Published from which new PAGES can be created. 7. Typography: Follow these below the design calls for something different. ELEMENTOR SET UP 1. DESIGN SYSTEM Site Settings > Global Colours - As per the design brief using Custom Colours as called for in the design Site Settings > Global Fonts - As per the design brief using Custom Fonts as called for in the design - Text Size: 1.2rem (c19px) 2. THEME STYLE Site Settings > Typography - Use default settings stated in the design brief Site Settings > Buttons - Use default settings unless stated in the brief Site Settings > Images - Use default settings unless stated in the brief Site Settings > Form Fields - Use default settings unless stated in the brief Site Settings > Header - Use default settings unless stated in the brief Site Settings > Footer - Use default settings unless stated in the brief 3. SETTINGS Site Identity - Use default settings unless stated in the brief Background - Use default settings unless stated in the brief Layout - Site Settings > Layout > Breakpoints + Mobile Portriat: 767px + Mobile Landscape: 880px + Tablet Portrait: 1024px + Tablet Landscape: 1200px + Laptop: 1366px + Widescreen: 2400px Lightbox - Use default settings unless stated in the brief Page Transitions - Use default settings unless stated in the brief Custom CSS - All Custom CSS should be defined in Elementor > Custom Code Additional Settings - Use default settings unless stated in the brief Running multiple sites efficiently means that all Devs must follow the same Processes and Procedures for quick and efficient Maintenace. These are 'House Rules' that have developed over years. These MUST be adhered to rigidly. IMPORTANT NOTES 1. Correct use of Fonts, colours, padding/margins is demanded. We will supply image and icon assets. 2. No use of Inline CSS styling eg. <span class="mz_heading">Efficiency</span>. Inline CSS should be considered as a LAST resort PROJECT PROGRAM 1. Target development time around 5-7 days (including reviews). TASK LIST 1. Kick-off and access to staging environment provided - day 1 3. Alpha release (internal review plus whitebox testing) - day 3 4. Beta Release (Client/limited release plus black box testing) - day 4 5. RC Release (go live and snags resolved) - day 5 6. Gold Release - day 7 ATTACHMENTS None. DESIGN TOOL Figma PS. If you are interested in this project, please 1. Provide examples of similar work 2. Suggest any improvement to the methodology above 3. Explain why you are a good fit for this project (and many others too) I will respond to all queries once the majority of submissions are in c4-5 hours time