Freelancer Posting (Mini Brief) We are seeking an experienced WordPress developer to rebuild our church website. An existing Tithely site is available as a reference: https://mychurch218.tithelysetup5.com It contains approved wording and base content, however it was never launched as it cannot support the advanced functionality we now require. We are looking for a site that is: • Visually polished and professional • Easy to read and navigate for all ages (especially older visitors) • Simple for non-technical staff to update The project will be delivered in stages. Stage 1 focuses on confirming navigation, layout, and overall visual direction before proceeding to full build. (A full detailed brief is attached.) ________________________________________ Scope Overview (Summary – Refer to Full Brief) Initial Direction • Confirm mobile menu/navigation approach • Confirm landing page structure and user flow • Establish overall visual style and layout direction • Validate usability (particularly mobile and older-user accessibility) before full build ________________________________________ Core Website • Build all key pages using existing approved content (no copywriting required) • Apply a clean, modern, and accessible design aligned to the approved direction • Follow a minimalist, mobile-first style (similar to Life.Church reference in full brief) ________________________________________ Sermons System • YouTube → website workflow • Automatic or near-automatic sermon publishing • Searchable archive (series, date/month, topic) ________________________________________ Events System • Centralised calendar (single event creation as the source of truth) • Display across relevant areas of the site using filtered views • Event pages with registration (free + paid) • Stripe integration for payments/sponsorships ________________________________________ Online Giving • Mobile-friendly donation system • Support for one-off and recurring giving ________________________________________ QR Landing Page • Dedicated, highly mobile-friendly landing page for QR visitors • Large, simple call-to-action elements (first-visit experience) • Easy for staff to update links, buttons, and images ________________________________________ Member Database & Communication • Secure, permanent storage of member/contact data • Support for email communications (EDMs) and event registrations • Simple sign-up and/or login functionality ________________________________________ Admin & User Management • Easy updates for non-technical users • Role-based access with page-level permissions • Backup and restore capability (revisions + recovery / “time machine”) ________________________________________ Tracking & Integrations • GA4 and Google Ads tracking-ready setup • Zapier integration capability strongly preferred, with the ability to trigger automations from key site actions (e.g. form submissions, event registrations, payments, user activity) without requiring custom code for each use case ________________________________________ Project Management • Use of a structured task/review system (not email) • Must support multiple reviewers for approvals ________________________________________ Proposal Requirements (Important) Please include the following in your proposal: 1. Relevant Experience • 2–4 examples of similar WordPress projects (church/community sites preferred, or sites with media libraries, member systems, and payments) 2. Technical Approach (Required) Please clearly explain how you would structure the following: • Sermon system (YouTube → website automation) • Events system (single calendar + registrations + Stripe payments) • Member database (user data, registrations, and communications) • Automation approach (how WordPress events trigger Zapier or similar systems) 3. Proposed Stack (Required) • Theme • Page builder (if any) • Key plugins (events, forms, membership, automation, etc.) • Any automation tools (e.g. Zapier, webhooks, internal automation plugins) 4. Workflow & Delivery • How you would approach Stage 1 (navigation/layout validation) • Estimated timeline • Estimated cost ________________________________________ Important (Read Carefully) • Please do not submit a generic proposal • Proposals without a clear technical approach will not be considered • Preference will be given to developers who demonstrate clear system architecture thinking (not just design or page building) ________________________________________