Senior WordPress Strategist & Developer

Senior WordPress Strategist & Developer Needed Website Evolution (Project, Oct 2026–March 2027) Overview We are seeking a professional who can deliver a focused WordPress website evolution and modernization for, a Detroit-based arts & culture membership organization. This is not a full site rebuild. It is a priority-page modernization built on reusable blocks and patterns so their small staff can maintain the site independently after launch. Budget for the complete engagement will be negotiated and confirmed from proposal. We need one highly qualified senior web designer or specialist who can own strategy through launch and stabilization. You will work directly with our project lead and become a core part of the delivery team. Project Timeline (Non-Negotiable) Kickoff: October 12, 2026 Discovery + Audit complete: October 30, 2026 IA, taxonomy, and component system approved: November 14, 2026 Priority template designs approved: December 5, 2026 Development + 25–50 page migration complete: January 16, 2027 Testing, training, and soft launch: January 30 – February 20, 2027 Final launch window: Late January – March 2027 30–45 day post-launch stabilization: Through mid-April 2027 Daily/weekly output must keep us on this schedule. Missed milestones will not be accepted. Exact Needs That Must Be Met (from RFP pages 14–18 and full scope) You will be responsible for producing or contributing to every item below so our final delivery fully satisfies requirements: Executive-level understanding of, its audiences, and strategic needs Clear project approach covering discovery, IA, design system, development, testing, migration, launch, and support Complete response to all current-phase functional and technical requirements Named project roles, availability, and time allocation Realistic milestone timeline with responsibilities and assumptions Transparent breakdown by phase (discovery, IA, design, development, migration, testing, training, stabilization) Strong work samples (at least one nonprofit/membership site + one component/block-based WordPress build) Three comparable client references Risks, exclusions, assumptions, and any recommended adjustments Full disclosure of any AI tools used, with human oversight and accountability practices Contracting readiness (IP transfer, warranty, insurance, standard terms) Plus the specific Questions requires answered: How the system stays coherent while allowing new programs and content types How non-technical staff can build consistent pages without creating rigid or repetitive layouts Clear decision framework for core WordPress vs. plugins vs. custom blocks vs. external services Future-phase evaluation plan for member login, gated content, Neon CRM, and LMS (no implementation in this phase) How accessibility, performance, privacy, SEO/GEO, analytics, and governance shape the architecture from day one Definition of successful post-launch adoption and how staff will be supported to reach it Core Deliverables You Will Own or Co-Own Focused discovery findings, technical recommendations, and prioritized roadmap Approved sitemap, navigation, taxonomy, search approach, and content models for programs, resources, events, stories/news, and jobs Homepage content hierarchy + responsive designs for all priority templates Documented web component system (branded blocks + prebuilt patterns) Fully configured WordPress site with improved search, Resource Library filtering, event calendar, Mailchimp signup, and Formstack patterns Migration/formatting of 25–50 priority pages + redirects + year-based story archives Practical WCAG 2.2 AA implementation with documented testing 6–10 GA4 priority actions + one practical reporting dashboard Focused training for two staff members + concise editor/maintenance guide 30–45 day post-launch stabilization support Future-phase recommendations for member login / Neon / LMS (documentation only) Required Skills & Daily Task Expectations Must-have skills (we will test these): Advanced WordPress (Gutenberg preferred; strong WPBakery experience acceptable if you can justify maintainability) Custom block and pattern development that non-technical editors can use safely Information architecture and taxonomy design for membership/resource-heavy sites Practical WCAG 2.2 AA implementation and testing GA4 event tracking + simple dashboard setup Performance, security, and plugin health within cPanel/Hosting.com environments Clear technical writing (you will help produce the final proposal language and the staff guide) Daily/Weekly Expectations Daily progress updates in shared channel (what was completed, blockers, next 24 hours) Weekly milestone check-ins with recorded decisions All designs and code delivered in a way that another WordPress developer could take over Zero scope creep without written approval Accessibility and quality checks performed continuously, not only at the end Budget & Payment Total project compensation: either fixed fee or hourly. Payment tied to approved milestones. Ongoing monthly maintenance after stabilization is a separate conversation. How to Apply – Required Application Materials Link to 2–3 live WordPress sites you personally built or led that use reusable blocks/patterns (preferably nonprofit or membership). Short note (max 250 words) answering: “How would you keep a site coherent for an adaptive arts organization while making it easy for non-technical staff to publish?” Confirmation you can meet the October 12, 2026 kickoff and the full timeline above. Your proposed weekly availability (hours) through April 2027. Any questions about the scope. Applications that do not include the above will not be reviewed. We are looking for one strong senior generalist (or a very tight specialist pair) who can move fast, communicate clearly, and leave the client with a site their staff can actually own. If this matches your experience and you can commit to the timeline we would like to work together.