Toy Brand WordPress Site & Product Migration

WordPress build of a finished design — toy brand, 109 products, migration from a legacy CMS The design is finished. You will receive it as working HTML pages you can open in a browser and measure — colours, spacing, type, wording and page structure are all decided. You will also receive all product data as ready-made CSV files, and all photography cut out and ready to use. There is no design work and no content writing in this job. We are buying the build. What we need built 1. A WordPress theme matching the supplied design: homepage, two range pages, a product template, an education page, an awards page, and a contact/enquiry page. A child theme of the standard block theme, or GeneratePress. No page builder (no Elementor, Divi or WPBakery) and no WooCommerce — we sell through distributors and show no prices. 2. Products as an editable content type with fields for article number, range, age, description, play guidance, skills, photographs and YouTube film, so our own staff can maintain the catalogue afterwards. Import all 109 records from the CSV we supply (21 columns, written for WP All Import). 3. Filtering by age and by skill on the two range pages, without a page reload. 109 products is a small set — plain JavaScript preferred over a filter plugin. 4. Mobile first. 69% of our search traffic is on phones, and our mobile pages rank nine positions better than desktop. We will test on a phone before anything else. 5. A redirect from every old address to its new one. We supply the mapping file: 13 confirmed rows plus roughly 436 candidate rows generated from the old naming patterns, which we will verify and hand over as a finished list before you implement them. This is the most important single deliverable — about a quarter of our current search visibility sits on addresses that are changing. 6. Search-engine basics: editable title and description per template, sitemap, product structured data, clean addresses. We supply all 115 titles and descriptions as a CSV, already within length limits. 7. An automatic translation layer — TranslatePress with the DeepL add-on, or an equivalent you can justify — configured and run for one language. Translations must be stored in the database and served as separate indexed pages with correct language tags; a browser-side translation widget will not be accepted. Tell us what each additional language costs in hours once the first one works. 8. Enquiry forms (parent, nursery, distributor) to our existing mailbox, with spam protection. 9. Product films embedded from YouTube per product, loaded only when clicked. 10. Launch onto our live domain, with SSL, analytics and Search Console connected. Our mail runs on Zoho and those DNS records must not be touched. 11. Handover: short written instructions and one screen recording showing how to add and edit a product. The theme delivered in a Git repository. What we supply on day one The complete design as browsable HTML pages All 109 products as a CSV, 21 columns, ready to import 115 page titles and search descriptions as a CSV The final address of every page as a CSV The redirect mapping file All product photography, cut out, plus 65 award logos All product films, already on YouTube One named contact who answers within a working day Hosting The hosting account will be in our name. You will be invited as a user. Payment — fixed price, four milestones 20% staging site running, homepage built and matching the design 40% all six page types built, 109 products imported, filters working 30% redirects in place, tested on a phone, live on the domain with mail untouched 10% two weeks after launch: no broken links outstanding, handover delivered All work happens on a staging site we can see throughout. Two rounds of revisions are included; anything beyond the scope above goes on a list for after launch. When you bid, answer these four — bids without answers will not be read 1. Link two WordPress sites you built from someone else's design, where the build matches the design closely. 2. How would you handle roughly 450 redirects, and how would you verify afterwards that none of them fail? 3. Which plugins would you use for the product fields and for automatic translation, and why? 4. How many working days do you need, and how many hours a week will you actually be on this project?