1. Project Summary
We are seeking a highly capable and professional web developer (Kadence Pro Suite Expert) to finalise our company's website redesign. The project involves taking over a partially completed website on a staging environment, addressing a detailed list of pending items, suggesting improvements, and managing the final migration to the live server.
The successful partner will be proficient with the Kadence Pro theme and will deliver a fully optimised, secure, and performant website that is, critically, easy for our non-technical team to maintain.
** Please note that we are NOT looking for a service provider who ONLY works US hours as we are not based in the US and require flexibility in that sense **
2. Guiding Principles & Core Requirements
This project is governed by principles designed to ensure a smooth process and a high-quality outcome.
• Professional Communication: We require clear, prompt, and proactive communication. This includes daily progress updates and immediate notification of any changes to the agreed course of action. We expect you to arrange calls upon our request to discuss progress. The use of a task management interface such as Trello will be needed.
• Performance as a Metric: The final website must be lightweight and highly optimised across all platforms, including desktop and mobile. We will use PageSpeed Insights and GTmetrix reports to assess performance, and reasonable changes may be requested based on these reports. The final website will pass Core Web Vitals Assessments and have high scores (90+ mark) for PageSpeed Insight across all platforms (mobile, desktop etc). This performance should replicate on GT Metrix Reports. We will provide initial reports before the start of this project.
• Maintainability is Non-Negotiable: The foundational principle of this project is to ensure long-term maintainability by our team. Your first task will be to conduct a full audit of all existing custom CSS. You will then refactor the site to replace this custom code with native Kadence Pro features wherever possible. Any new custom CSS is considered a last resort and requires explicit justification and prior approval. From our own review, there does not seem to be a lot CSS but we would still like to keep this to a minimum.
3. Scope of Work
A. Global Site Architecture & Design
• Navigation: Implement and/or reformat drop-down menus for “Categories”, "Destinations," "Travel Resources," and "About" (which includes "Our Story" and "Contact Us").
• Page Enhancements/Re-Design: Review all main web pages, suggest improvements/re-design using Kadence Pro features, and discuss them with us before implementation.
• Typography Governance: All site-wide typography must be controlled globally via the Kadence Customiser to ensure maintainability.
B. Blog Post Reformatting (Key Deliverable)
• Complete Reformatting: You are responsible for reformatting all 31 existing blog posts to a professional standard using Kadence Block Features only. The content was previously built with Gutenberg, Ultimate Blocks, or Elementor.
• Layout & Feature Replication: Existing formatting (such as tables, accordions, and info boxes) must be recreated using appropriate Kadence block equivalents. The original formatting should serve as a guideline, with improvements made for optimisation and user experience.
• Process: This implementation relies entirely on you, the supplier. Our involvement will be limited to consultation and approval of any proposed new formatting approaches before they are rolled out.
• Existing Elements: The blog post sidebar and Table of Contents are already implemented but may require minor changes upon our request.
• Font Types/Sizes for Blog posts:
Font Type Desktop Size (px) Mobile Size (px) Line Height
Body Text Open Sans Regular 17 17
H3 Roboto Condensed 22 20
H2 Roboto Condensed 28 24
H1 Roboto Condensed 36 28
• Blog Post Spacing & Layout Rules: To ensure a clean, readable, and consistent layout, all content elements must adhere to the following vertical spacing guidelines. These settings should be controlled globally via the Kadence theme options wherever possible.
Previous Element / Object Next Element / Object Required Spacing Notes / Implementation
Any Block (e.g., Image, Text) H2 or H3 Heading H2: 37 px (margin-top)
H3: 34 px (margin-top) Creates clear separation for a new section.
H2 or H3 Heading Paragraph Text 15 px (margin-bottom) Tightly couples the heading with its content.
Paragraph Text Next Paragraph Text 22 px (margin-bottom) Standard paragraph spacing for readability.
Paragraph Text Any Block (e.g., Image, Table) 22 px (margin-bottom) Provides breathing room before a new element.
C. Technical Integrations & Configuration - some can only be done on the live site due to license and other restrictions.
• Forms & Security: Troubleshoot the contact form and add robust anti-spam and Cloudflare Turnstile (and not Captcha) measures.
• Plugin Configuration: Install and configure the following suite of plugins (we will provide paid licences) & making sure that there are NO conflicts between them:
1. Complianz (paid): Install and configure for cookie consent. The generated Cookie Policy must be linked in the footer. We will then provide the Terms of Use and Privacy Policy for you to upload. (on live site only)
2. Yoast SEO (free): Install and Configure for basic on-page SEO (meta tags) and sitemaps. All settings require our review and approval before final implementation.
3. WP Rocket (paid): Install and Configure for optimal caching and performance. (on live site only)
4. Imagify (paid): Install & Configure for complete image optimisation. (on live site only)
5. Perfmattters (paid): Install & Configure for optimal WP performance optimisation. (on live site only)
6. Easy Social Share Buttons (paid): Configure for social sharing functionality. (on live site only)
• Platform & Analytics:
1. Cloudflare: Check the existing configuration and ensure the cache is cleared correctly upon go-live to prevent disruption. (on live site only)
2. Google Services: Install and configure Google Search Console, Google Analytics, and Google Tag Manager. Rather than placing many different tracking codes (e.g for Google Analytics, Facebook Ads, etc) directly in our site’s code, only install GTM. Inside GTM Container, manage and add all other tags from one place. We need this to make sure the website is cleaner and faster as well as to allow for easier updates.
D. Finalisation, Testing & Go-Live
• Security & Backups: Ensure the website's backup system is working correctly. Provide a list of all security features that have been implemented for our records. Use Cloudflare Turnstile instead of Captcha.
• Testing: Conduct full testing across all major browsers and devices. The results must be sent to us for review, and any final change requests must be implemented.
• Go-Live Process: The migration from staging to live requires our final, explicit approval. The transfer must be prompt and efficient, with any potential issues communicated immediately alongside proposed remedial actions.
• Documentation: Provide user documentation for any specific or complex configurations implemented.
E. Future-Proofing
The site must be built on solid foundations that prepare for the future integration of e-commerce features, although no e-commerce functionality is required at this stage. The architecture must also be capable of accommodating several hundred articles.