WordPress Developer — Full Site Build with Kadence Pro, Membership & API Integrations

Budget: Seeking fixed-price proposals. Quality, demonstrated experience with Kadence Memberships Pro, and attention to detail are more important than being the lowest-cost bidder. About Us Friends of Perry Lakes Inc. is a volunteer conservation organisation based in Perth, Western Australia, managing Perry Lakes Reserve in Floreat — two urban wetlands supporting a rich ecosystem of native plants, birds, and reptiles in the middle of Perth's western suburbs. This project is funded through the NRM Community Stewardship Program, a government environmental grant. About the Project We are replacing an outdated website with a modern WordPress platform that will: Communicate the ecological story of Perry Lakes Reserve Support volunteer and citizen science programs Host a paid membership platform with Stripe recurring payments Manage events and community engagement Display live environmental monitoring data via API integration The design, content architecture, and navigation structure are already complete. We are not looking for design services. Your role is to implement what has already been designed, accurately and to specification. We have already prepared: Full working HTML prototype (all pages, desktop layout, real content) Brand guide Detailed page-by-page development specifications A3 site map Photography assets Custom SVG icon family (25 icons) Shortlisted applicants will receive all of the above at a full briefing session before build commences. Technology Stack — Fixed, No Substitutions The following stack is non-negotiable. Please do not propose alternative page builders, membership plugins, or event systems. WordPress (latest stable) Kadence Pro — page builder, header/footer builder, mega menus Kadence Memberships Pro (formerly Restrict Content Pro) — membership platform Gravity Forms — volunteer EOI and citizen science application forms Modern Events Calendar — events management and homepage feed Stripe — recurring membership payment processing Mailchimp — newsletter and membership audience management Kinsta — managed WordPress hosting (we will establish the account prior to build commencing — developer to advise on setup sequence) ArcGIS — storymap and monitoring dashboard iframe embeds DWER telemetry API — live environmental water level data fetched server-side via WordPress cron and transients Experience with Kadence Memberships Pro (post its transition from Restrict Content Pro) is essential. Please confirm this experience explicitly in your proposal. Scope The website comprises approximately 45 pages and templates. Public website: Homepage with live telemetry data bar, events feed, and photo strip The Reserve section — ecological story, threats, management, and guidance pages Science & Nature section — monitoring data, wildlife, plant life, threats, field notes blog, and research library Get Involved section — volunteer EOI, PlantFest annual event pages, citizen science application, and events calendar Membership section — public-facing membership information and join flow About Us section — governance, annual reports, impact, and grant funding Photo gallery (Photos custom post type with season filter) Field notes blog (Blog custom post type with ACF standfirst field) Species pages (Wildlife custom post type with tile grid and species modal) Integrations: Gravity Forms (volunteer EOI, citizen science application — email notifications to Works Coordinator on submission) Modern Events Calendar (What's on page, PlantFest event pages, homepage events strip, Google Calendar sync) Mailchimp (newsletter signup in footer — integrated natively via Kadence Pro) ArcGIS Storymap (static HTML embed at /water-story/ — iframe code supplied during build) ArcGIS monitoring dashboard (iframe embed on Our monitoring data page — code supplied during build by our data lead, who is developing this concurrently) Stripe (membership payments via Kadence Memberships Pro — no WooCommerce required) DWER telemetry API (live water level data from two monitoring stations — server-side WordPress cron fetch every 15–30 minutes, stored as transients, graceful fallback to last known value with timestamp) Blocked at launch — build but do not activate: Spot It · Share It sightings submission form — coordinator appointment pending Country and History page — formal cultural consultation with Whadjuk Noongar Traditional Owners pending Membership Platform The membership platform is delivered in Stage 2. Portal page designs will be supplied by FoPL at the start of Stage 2 — the developer is not required to design these pages, only to implement them in Kadence Blocks and wire up Kadence Memberships Pro. Membership tiers: Individual — $30/year Family (household) — $40/year Kadence Memberships Pro must handle: Stripe recurring annual subscriptions Member registration and account creation Automatic renewal and expiry management Content restriction — member portal pages hidden from non-members Restricted page treatment — non-members see a join prompt, not a blank page Mailchimp audience sync — members tagged separately from newsletter subscribers Member dashboard built in Kadence Blocks with dynamic visibility Member portal pages (FoPL-designed, handed to developer at Stage 2 start): My dashboard Membership card Member updates Citizen science tools Profile & settings Renew Event RSVPs Delivery Structure and Payment Milestones This is a fixed-price project with four payment milestones. All work is delivered and reviewed on a Kinsta staging environment before production deployment. StageDeliverablePaymentStage 1Fully responsive staging site — all public pages, all integrations, brand-accurate, no membership portal. FoPL reviews and approves.35%Stage 1bWritten implementation specification confirming how Kadence Memberships Pro will deliver the membership platform requirements. This unlocks FoPL's portal page design sprint.15%Stage 2Membership platform integration — Kadence Memberships Pro, Stripe, restricted content, member dashboard, all portal pages built from FoPL-supplied HTML designs. Tested on staging.30%Stage 3Production deployment and full handover (see Stage 3 requirements below). Final payment released after 14-day bug fix period.20% Payments are structured so 50% is held until full delivery and production sign-off. The 14-day bug fix period covers issues arising from live traffic, real user accounts, and real Stripe transactions. Target production launch: October 2026. Please include an indicative timeline breakdown across all stages in your proposal. Stage 3 — Contractual Handover Requirements Stage 3 is not just go-live. The following are contractual deliverables included in the Stage 3 milestone: Written documentation — all plugins, licence key locations, custom post types, ACF field groups, and any custom code written during the build Recorded handover training — minimum 60 minutes, screen recorded, covering page editing, event management, member management, and content updates. Stored in a location FoPL controls. Full admin access to everything — WordPress, Kinsta hosting, all plugin licence accounts, Stripe, and Mailchimp. Nothing to remain under developer accounts. Written WordPress update procedure — how to safely update WordPress core, Kadence, and plugins Written backup and recovery procedure — what is backed up, how often, where stored, and how to restore 30-day post-launch support window — developer available by email for questions during the volunteer team handover period at no additional charge Hosting We are using Kinsta managed WordPress hosting. Kinsta provides reliable WordPress cron execution (essential for the DWER telemetry integration), built-in staging environment, automatic daily backups, and SSH/WP-CLI access. We will establish the Kinsta account before build commences. Developer to advise on recommended setup sequence for plugins and hosting environment. All Licences Held by FoPL All plugin and hosting licences will be purchased and held under FoPL-controlled accounts. We are not looking for a developer who manages licences on behalf of clients. Developer to confirm they are comfortable with this arrangement and advise on the recommended sequence for setting up accounts before build commences. What We Are Looking For We are seeking a developer who: Has a minimum 3 years of commercial WordPress development experience Has built with Kadence Pro and is comfortable with its full feature set including mega menus, header/footer builder, and Kadence Blocks Has implemented Kadence Memberships Pro post its transition from Restrict Content Pro — not just the legacy product Has built with Modern Events Calendar and Gravity Forms Can work accurately from a supplied HTML prototype and detailed written specifications without design input Is comfortable building responsive layouts from desktop-only HTML designs Provides clear communication, meets milestones, and produces clean documentation Is fluent in English — all communication and documentation will be in English To Apply Please include all of the following in your proposal. Generic proposals will not be shortlisted. Your fixed price for the complete project across all four stages Your proposed timeline broken down by stage Links to at least two WordPress membership websites you have built — live URLs preferred Explicit confirmation that you have worked with Kadence Memberships Pro post its transition from Restrict Content Pro Explicit confirmation that you have built with Modern Events Calendar and Gravity Forms A brief explanation of your approach to responsive implementation when working from a desktop HTML prototype Confirmation that you are comfortable with FoPL holding all plugin and hosting licences under FoPL-controlled accounts Any specific questions you have after reading this description — considered questions are a positive signal To confirm you have read this listing in full, please begin your proposal with the words: Perry Lakes Proposals that do not begin with "Perry Lakes" will not be opened.