Diversability Village Resource Website Roadmap

A visual map of the work required to move from idea and identity to beta embeds, feedback, strategic launch, and long-term stewardship.

14tasks
4phases
3loops

Phase 01

Identity + Foundation

  • Purchase and establish the new .com domain through Bluehost.
  • Finalize the Diversability Village rebrand and logo.
  • Develop the resource website logo.
  • Build the website foundation at diversabilityvillage.com.

Phase 02

Resources + Polish

  • Assign who is adding each list of resources.
  • Add resource lists and entries to the site.
  • Refine the site content, photos, and user experience.

Phase 03

Beta + Feedback

  • Launch beta versions at the County and Full Access High Desert.
  • Max and Mia embed the resource website into agency sites.
  • Max, Laura O'Neill, and Mia Swanson collect feedback data.

Phase 04

Launch + Sustain

  • Strategically add the website to other agencies.
  • Create the elevator pitch and talking points.
  • Market the website across the region and state.
  • Set ongoing delegation, meetings, and review committee rhythm.

Decision Points

Choose the final Diversability Village logo direction.
Choose the final resource website logo direction.
Assign who owns each resource list.
Create ongoing site management documentation.
Schedule regular team and review committee meetings.

Stewardship Loop

01 Gather Collect resource additions, agency needs, and beta launch feedback.
02 Review Use submission checklists and review committee guidelines.
03 Publish Update the website, inform partners, and keep the roadmap moving.
Identity and setup Resource buildout Beta testing Launch and governance

Diversability Village Priority Map

Tasks from Asana reorganized by priority, with workstreams and dependency order preserved.

High

Must anchor the system

2

These affect safety, quality control, and whether resources should appear publicly.
Medium

Important build items

3

These improve site completeness, resource inventory, and public partnership clarity.
Low

Lower-risk follow-up

12

Useful tasks, but most can wait until the structure and approval process are stable.

Priority View

High Do First

Task Workstream Why it matters
Vetting process for new resource entries and automations
All new resources should default to not public until approved.
 Vetting + Airtable This is the safety gate. Without it, unverified resources can accidentally go live.
Rubric for people vetting sites
Checklist for what reviewers should look for.
 Vetting + Quality Control Reviewers need shared criteria before approving resources.

Medium Build Next

Task Workstream Why it matters
Update the partners
Ask Heather if she wants to be one, for example.
 Partners + Outreach Public-facing credibility and community alignment.
Pull existing resources from the set
Source listed: https://ivk.yew.mybluehost.me/
 Resource Data This is likely the fastest way to populate the directory, but still requires vetting.
Develop the partner program
Define what becoming a partner means.
 Partners + Website Needed before creating a clear partner page or inviting more organizations.

Low Schedule After Structure Is Stable

Task Workstream Best timing
Update the People section
Include you and everyone’s roles.
 Website Content After roles are confirmed.
Set up automated monthly newsletter
Email new resources once a month.
 Email + Automation After approved, published, and date-added fields are reliable.
Update form to say who submitted the resource Forms + Airtable During Airtable/form cleanup.
Add submitter feedback field
Why are you submitting it? Can we share with permission?
 Forms + Data During form redesign.
AI agent options
Crawl resource websites for information such as insurance.
 AI + Data Cleanup After required fields are defined.
Notify organizations they were added as a resource Email + Automation After resource owner email field exists.
Create embed instructions
Allow others to embed the website or directory.
 Website + Distribution After the public directory view is stable.
Ask Amanda to see a grant for Diversability again Funding Anytime, but stronger with project plan attached.
Build explainer animation Communications After workflow language is final.
Create backup plan for site Sustainability Before launch or handoff.
Create future-update explainer
How this works for updates in the future.
 Documentation After final system is built.
Decide email contact
What will you use for email contact?
 Email System Move earlier if newsletter or resource-owner notifications begin soon.

Build Sequence

1

Vetting rules

Define what gets approved and what stays hidden.
2

Rubric/checklist

Give reviewers shared criteria.
3

Airtable fields

Status, reviewer, source, owner email, verified date, public yes/no.
4

Import resources

Bring over existing resources, but route them through review.
5

Automations

Newsletter, resource-owner emails, annual reminders, embed-code replies.

Workstream View With Priority Tags

Vetting + Approval

  • Vetting process High
  • Rubric for vetting sites High
  • Default new resources to not public High

Resource Data

  • Pull existing resources Medium
  • Fix categories Suggested high
  • AI agent options Low

Partners + Outreach

  • Update partners Medium
  • Develop partner program Medium
  • Ask Amanda about grant Low

Forms + Submission

  • Who submitted the resource Low
  • Submitter feedback field Low
  • Permission to share feedback Low

Email + Newsletter

  • Email contact decision Low, but dependency
  • Monthly newsletter Low
  • Notify organizations Low

Website Content

  • Update People section Low
  • Embed instructions Low
  • Explainer animation Low

Documentation + Backup

  • Backup plan Low
  • Future-update explainer Low

Priority Note

  • Asana marks “email contact” as Low, but it is a dependency for newsletter and notification automations.
  • Categories are not visible as their own Asana row in the screenshot, but they should be handled early.

Suggested build order: vetting rules → rubric/checklist → Airtable fields → import resources → automations.