WordPress development, client support, and recurring maintenance systems

Project Details

This work covered both Nonprofit Resources’ internal website needs and a wide range of client-facing development work. On their own site, the goal was not just to refresh the design. The backend also needed to be more organized so content could be managed more cleanly over time. We redesigned the website and restructured the WordPress setup with custom post types and custom code modules, which made data organization and content creation more streamlined and easier to maintain.

The larger part of the relationship was ongoing web and technology support on behalf of Nonprofit Resources for the nonprofit organizations they served. That included full website builds, recurring website maintenance, consulting, progress meetings, and day-to-day technical problem-solving. Because many of those organizations used WordPress for their public-facing websites, the work often included plugin updates, backups, content changes, troubleshooting, and general upkeep across multiple sites.

To make that maintenance work more consistent, we set up a repeating workflow in their task management system so client updates were scheduled instead of handled manually each time. We also built a changelog process and an email notification flow so clients could see when work was scheduled and when it was completed. That gave Nonprofit Resources a clearer proof-of-work process and helped keep communication active instead of reactive.

Some projects were straightforward maintenance. Others involved full website development from the ground up. That work often meant joining meetings with board members and stakeholders, helping guide discussions around goals and milestones, and then handling the actual build work behind the scenes. In other cases, the job included site migrations, domain and DNS setup, email setup, and technical handoff work tied to launches or platform changes.

Another layer of complexity came from the association management systems used by some nonprofit clients. Those systems often supported core parts of the organization’s operations, including member dues, directories, paywalled content, documents, and events. Keeping those systems updated, aligned with website content, and working cleanly alongside the public-facing site was part of the broader support role.

Several clients also went through larger platform migrations, which meant existing data, documents, and workflows had to be reviewed before anything moved. That work required auditing what should be kept, what could be retired, and how to move the right information into a new platform without creating service disruption for members or staff.

Because Nonprofit Resources did not have a dedicated developer on staff, this relationship gave them a practical way to expand what they could offer. It helped them support existing clients more consistently and also take on organizations whose biggest need upfront was web development, while still fitting into the broader consulting and support work their internal team already handled.