Configuration notes for the FWDR (Financial Wellness Done Right) website hosted at finwellu.com, covering domain setup, email delivery, and email template requirements. Derived from the [1] launch planning session.
The site uses the domain finwellu.com (selected over myfwdr.com). The domain is registered through GoDaddy and requires a coordinated handoff to update DNS/domain settings:
finwellu.com so outbound emails originate from that domainAll references to "Next Level" must be removed from the site, emails, and any confirmation messaging. Approved names are:
- "Financial Wellness Done Right" (preferred for formal contexts)
- "FinWellU" / finwellu.com (acceptable shorthand, especially for HR audiences)
WordPress sends all confirmation emails natively. Key delivery concerns surfaced during testing:
Recommended: Configure a dedicated SMTP service (e.g., SendGrid, Mailgun, or similar) rather than relying on WordPress's default PHP mail. Ensure SPF/DKIM records are set for finwellu.com.
Two categories of transactional email need to be built out:
Sent when a user creates a personal login on the site. Current state is a plain, generic "success" message that needs a full overhaul.
Required elements:
- FWDR logo (Logo D variant) at the top
- Branded colors and FWDR identity — no "Next Level" references
- A brief "hype" statement about Financial Wellness Done Right
- Clear instruction to save the email as a reference for future logins
- Call to action: prompt the user to log in and register for a workshop ("you're halfway there" framing)
- Login link and password reset link
Sent when a user registers for a specific workshop. Must support dynamic content based on event type:
| Event Type | Required Content |
|---|---|
| Virtual | Join link / webinar URL |
| In-Person | Venue address, room/suite details (e.g., "Conference Room C, 3rd Floor" or full street address) |
Both email types should be sent from a finwellu.com address. The reply-to address strategy (centralized FWDR inbox vs. rep-specific) is pending a decision by Peter Tourville after consulting with Paul — see [1] action items.
The site uses individual user logins (not a shared company login). This was a deliberate architectural decision to enable:
Registration flow:
1. User visits the registration page
2. Enters: username, first name, last name, email, company website URL
3. Company website URL is used to associate the user with a company profile
4. User receives account confirmation email
5. User logs in and lands on their company-specific page to browse and register for events