An association website redesign needs a plan for the people and records behind the public pages. Membership dates, account access, conference registrations and payment history all need attention before a new design becomes the association’s working system.
Innovative Marketing Solutions (IMSWebWorks) is applying that approach to the Florida Association of School Social Workers (FASSW). The project combines a custom WordPress website with membership software that replaces core administrative workflows previously handled in WildApricot.
Project status as of October 30, 2026: The redesigned public website and FASSW Membership Portal v0.4.0 are deployed. The migration includes 871 contact records. Live payments and outgoing member emails remain disabled pending verification, configuration and approval.
This article explains the planning decisions behind that work. For the project overview and actual before-and-after screenshots, visit the FASSW Website and Membership Platform Case Study.
Start With the Tasks Members Need to Complete
A prospective member needs to understand the association, find the right membership option and know how to join. A returning member needs account access, renewal information and useful resources. Staff need a different set of tools to maintain records and respond to requests.
The FASSW public website organizes membership, professional resources, advocacy, conferences and news. Its responsive design presents those sections on desktop and mobile screens. That public structure gives visitors a route into the association without exposing administrative tools.
For your own redesign, list the tasks people must complete before choosing page layouts. Include exceptions. A member who cannot access an old email address needs a different response from someone joining for the first time.
That task list becomes part of the written scope for Website Redesign. It also helps distinguish visual changes from database work, account functions and integrations. Those are separate responsibilities, even when they appear within one website.
Preserve the Records Before Rebuilding the Interface
The FASSW migration imported 871 contact records, including 656 archived contacts. The recorded import checks found no duplicate records or data conflicts. Original identifiers, membership dates and statuses were retained rather than replaced with a new signup date.
Those 871 contacts should not be described as 871 active members. A contact database can contain current members, former members, event participants and other contacts. Preserving those distinctions matters when deciding who receives access, a renewal notice or a general announcement.
IMS also backed up historical event registrations, communications and financial records. Preserving a historical invoice does not turn it into a new order, and importing an old payment does not authorize a new charge. The new system must keep that history separate from future transactions.
A useful migration review checks more than the total number of records. Compare membership states, expiration dates and archived status against the source. Review representative records with different histories. Record any export exceptions instead of treating a successful file download as proof that everything transferred.
Keep those checks private. Public project screenshots should never expose member names, email addresses, financial details or administrative access information.
Separate Public Pages, Member Accounts and Administration
The website and membership portal serve different audiences. A public page explains a membership option. A member account shows information relevant to that member. An administrator needs access to broader records and tools.
WordPress roles and capabilities provide a way to define permitted actions. The custom application still needs to enforce the right permission for each protected operation. A hidden menu item alone does not establish access control.
The FASSW member functions include login, administrator-issued activation or password-reset links, profile editing, and membership status and dates. Staff have separate Contacts and Members administration rather than one undifferentiated list.
This is an association management system (AMS) with customer relationship management (CRM) capabilities. Its focus is the member lifecycle, records and association operations. It is not a standard sales pipeline with membership labels added.
For an organization with similar requirements, Custom CRM and Business Software and Web Application Development describe the software work involved. The scope should identify who can view, change, export and approve information.
What IMS Has Delivered for FASSW
The deployed work spans the public website and the system behind it. The custom FASSW Shoreline theme provides the public-facing WordPress design. The FASSW Membership Portal supplies the association-specific account and administrative tools.
The confirmed release includes:
- Public website and content structure: A responsive design with organized membership information, resources, conference content and association news.
- Contact and membership migration: The imported contact inventory, retained legacy identifiers and membership information, and preserved historical records.
- Member self-service: Account access, profile editing, membership information and administrator-issued activation or reset links.
- Administrative tools: Separate Contacts and Members areas, membership levels and renewal handling, search and reporting tools, historical financial information and a searchable Help Center.
- Event and communication tools: Event and registration administration, free-event and waitlist functions, and protected email drafting and queue controls. The v0.4.0 release also added paid-event and donation functionality, with live payment processing still disabled.
WooCommerce and the GoDaddy Payments gateway are installed as part of the commerce foundation. That installation is a development milestone, not confirmation that a real member can complete a payment and that the association can receive the payout.
The project record reports 98 backend checks and 25 browser checks for v0.4.0, followed by production verification. Those checks support the release record. They do not establish client acceptance, verified payment settlement or successful delivery of member emails.
Payments and Member Emails Need Separate Release Checks
FASSW’s remaining launch work includes merchant verification and banking setup, a supervised payment test, sender configuration, delivery verification and approval of email templates.
For a membership system, a payment test should follow the entire request. Confirm the selected membership or event, the amount, the resulting transaction record and the correct account update. Check what happens when payment fails or a person returns to the page before confirmation.
These are acceptance tasks for the FASSW release, not claims that production checkout has passed. Recurring donations, guest checkout, event sessions and advanced cohort tools are outside the confirmed v0.4.0 release.
Email requires its own checks. An account invitation should reach the intended recipient, identify the association and lead to the correct account action. Renewal and event notices need approved wording and timing. A stored draft or a populated queue does not prove delivery.
Keeping outgoing messages disabled during these checks prevents a development action from becoming an unintended member announcement. Associations considering E-Commerce Development should include membership, event and payment relationships in the scope.
Protect Useful Content and Search Visibility
A redesign should account for existing resources, documents and links that people already use. Build an inventory before deciding what to replace. Identify current material, outdated announcements and resources that belong in an archive.
For FASSW, fassw-fl.org remains the primary website. Changes to the older fassw.org domain need their own approved plan. This project update does not claim that the old domain has been transferred, redirected or retired.
When public URLs change, Google’s site-move guidance calls for mapping old URLs to appropriate destinations, implementing redirects and monitoring the move. That is different from sending every old address to the homepage. A redesign also needs accurate internal links and updated page references.
Search Engine Optimization belongs in that planning. Page headings and metadata should describe the public information available. Private member records should not become public content for the sake of search visibility.
Google states that its normal SEO fundamentals also apply to AI Overviews and AI Mode. Pages need to be indexed and eligible for a search snippet to appear as supporting links. There is no special AI-only schema requirement. The Google Search Central guidance on AI features explains those requirements.
No search-ranking or traffic improvement is claimed for FASSW in this article. The work described here concerns the design, migration, software and release process.
Give Administrators a Handoff They Can Use
The searchable Help Center is part of the deployed portal. The broader handoff still includes administrator training, final operating instructions and acceptance of the remaining launch tasks.
A useful manual follows the work a person needs to perform. Show how to find a member, check a renewal date, review an event registration and handle an account-access request. Explain which actions change a record and which only display historical information.
Include failure cases. Staff need to know how to respond when a reset link expires, a payment is unresolved or a message fails to arrive. Each situation should have an owner and a documented next action.
A custom platform also needs an agreed maintenance plan. Backups, software updates, account permissions and ongoing support do not disappear after launch. Define those responsibilities before the association relies on the system for daily work.
Define Your Association’s Redesign Scope
Before requesting a quote, gather your current website address, membership rules, sample administrative tasks and an inventory of the systems you depend on. Identify the records that must be retained, the people who need access and the payment or email functions that require approval.
Separate the launch requirements from later improvements. That gives the developer a basis for estimating the work and gives your team a way to accept each deliverable. It also prevents a public website quote from being mistaken for the price of a complete membership application.
IMS quotes association portals, migrations and custom software around the defined scope. The IMS Website Pricing Guide explains the difference between a basic business website and more involved development. A membership migration needs its own assessment.
To discuss your association’s website and member-management requirements, Contact Innovative Marketing Solutions. Work directly with Timothy McGuire to identify the public pages, data and administrative functions your project needs. Call (904) 439-6279 or email info@imswebworks.com.
