Local Association Member Portals

[BigSnicker]

Purpose

To help Local Member Associations (EDAs) advertise their activities within their region, connect with other members, associations, and the general public.

Success Metrics

• Increased member recruitment from the general public.
• Increased member retention among WeDecide users.
• Increased attendance at regional events.
• Increase in fundraising, particularly conversions to monthly memberships.

Feature 1: Having Participants set a "Home Area" and automatically follow it

Description: Introduce a "Home Area" variable to the Participant object to indicate the geographic area where the participant resides, influencing their homepage.

Requirements:

• Add "Home Area" field to the Participant object using the Decidim Area.
  • This field will determine the participant's Home Page and can appear as "Avalon" or "Avalon (10001)".
  • Home Areas can be local (e.g., Calgary Centre) or can be a region that combines local areas (e.g., Calgary or Alberta).
  • The variable does not need to understand regional hierarchies, except in any dropdown list.
• Participants should select their "Home Area" in their profile settings or via "Make [this EDA] your home EDA" buttons.
• The participant's chosen "Home Area" should not be visible to other members to respect data privacy.
  • To show their EDA in their Decidim profiles, participants can request EDA administrators to be members of EDA assemblies
• Automatically follow the related assembly when a participant sets their "Home Area."
  • Include a tooltip or note next to the "Home Area" field informing users: "Setting your home EDA will set your WeDecide homepage and, if your notifications are turned on, send you updates from your home EDA."

Acceptance Criteria:

• Addition of "Home Area" field to Participant object.
• Home Area selection available in profile settings and via buttons.
• Privacy of Home Area selection ensured.
• Automatic participant following of related assembly upon Home Area selection.
• Informative tooltip or note next to Home Area field.

Feature 2: Navigation to Home Area Homepage

Description: Enhance navigation by directing members to their Home Area homepage based on their Home Area selection.

Acceptance Criteria:

• Member's homepage is correctly derived from their Home Area (e.g., wedecide.green.ca/assemblies/avalon).
• "Take me to my Home EDA" navigation option is available (for example, in the site header)
• Field is added to all email digests when "Home Area" is set ("Check out what's happening in your local area by clicking here")

Feature 3: Postal Code-Based Redirect to Local or Regional Homepage

Description: Implement a feature that allows users to find their EDA or regional assembly based on their postal code.

Acceptance Criteria:

• "What's your postcode" / "Find your EDA" field added to the website header or front page.
• Correct redirection to the designated EDA or regional assembly based on postal code entry.

or

Technical Requirements of all the above features:

1. Database Changes:
   • Add Home Area field to the Participant object.
2. Frontend Changes:
   • Update profile settings to include Home Area selection (possibly by dropdown or postal code)
   • Create Local Association (EDA) assemblies that include "make this your local assembly/EDA" button for Home Area selection
   • Include navigation option to go to Home Area Local Association (EDA) assembly
   • Add "Look up your local association" postal code input field to the website header or front page.
3. Backend Changes:
   • Implement logic for automatic assembly follow and homepage redirection.
   • Ensure correct redirection based on postal code entry, including lookup of postcode-to-local association mapping
   • Update outgoing email digests with navigation to Home Area

Optional: Creation of assemblies for each Home Area or Home Region (~50-80)

[BigSnicker]

Note, it will be worth discussing options for "Post Code" to "Riding"/"EDA"/"Local Association" mapping. There are a few options, such as:

1. A lookup table of postcode -> riding
2. An API of postcode->riding
3. A shape file based on an address look-up and geo-coordinates