Website Developer — Elementor Build

Less than 1 month, Less than 30 hrs/week Website — Elementor Build Brief Platform: WordPress + Elementor Pro Sitemap reference: DPG 2026 Website Working What we need: Build the DPG Diesel website using Elementor Pro's Theme Builder — reusable templates and global widgets, not separately hand-coded pages. This keeps cost down and makes future pages fast to add. • Pages (7-10 total, built from 6 templates) • Homepage — 1 page (already designed, just needs to be built) • Engine Family page — 1 template, used 3 times (CAT, Detroit, Cummins) • Engine Model Detail page — 1 template, used 1-3 times at launch (e.g. CAT C15), reused for every future engine model added later • Service page (In-Frame Overhaul) — 1 page • Category hub (Reman Engines) — 1 page • Contact page — 1 page Build

Requirements • Global Widgets (build once, use on every page): • Header/Nav • Footer • Mobile sticky call/quote bar • Quote form (Name, Phone, Email, Engine Make/Model, VIN optional, Location, Message) • Form platform: Use Gravity Forms (not Elementor's native form widget) for the quote form. It needs to route submissions into our D365/CRM pipeline, not just email. • 3-column comparison table (Used Engine / Rebuilt Engine / DPG Reman Engine) • Urgency strip banner • Engine Family template (Theme Builder template, used for CAT/Detroit/Cummins): One template, same layout for all three brands — only text, images, and model cards change per brand. Needs: hero section, model card grid, photo gallery, testimonials, comparison table, 4-step process, certification bar, quote form, fleet program banner. Engine Model Detail template (new, reused for every engine model): One template covering: model name/headline, spec table, corrective-mod detail, testimonial, quote form. Every "View Details" link on the site should point to an instance of this template. Dynamic content setup: Use Advanced Custom Fields (ACF) with a custom post type for engine models, so each brand/model is a data entry feeding the templates above — not a manually duplicated page. This is required, not optional — it's what makes future engine models cheap to add later. In-Frame Overhaul & Reman Engines hub pages: Reuse the Engine Family template's sections wherever possible (hero, process steps, etc.) instead of building new ones from scratch. Rule for bidders Do not build a new component if an equivalent one already exists elsewhere on the list above. If something looks like it needs a new component, flag it to us first before building — we're paying to build each module once, not once per page. Deliverable Fully responsive WordPress + Elementor Pro site, using global widgets and Theme Builder templates as described above, with ACF-powered dynamic content for engine model data.