ThreeFold.io UX Testing - Potential / Existing DIY Farmers (Persona2) #36

Open
opened 2025-04-03 11:05:12 +00:00 by sashaastiadi · 0 comments
Owner

Website Feedback for Persona 2: Potential/Existing DIY Farmers

🧭 Navigation & Information Architecture

  • Lack of a Dedicated Farming Hub: While farming is a core component of the ThreeFold ecosystem, there is no clear, dedicated entry point in the top navigation specifically for farmers. Currently, farmers must navigate through "Take Action" or FAQs to find relevant content, which could be more intuitively organized.

  • Scattered Content Locations: Key farming resources like the Farm FAQ and the ThreeFold Forum are hosted on separate domains and not clearly linked within the primary site experience. A DIY farmer may not easily discover or know to trust external pages without a centralized information architecture.

  • Overreliance on External Docs: Much of the relevant technical material is located in GitHub repositories or docs.grid.tf, which may be intimidating for non-developer DIY farmers. These resources are critical but need better context and linkage from the main site.

📄 Content Relevance & Technical Depth

  • Insufficient Step-by-Step Onboarding: The site lacks a clearly structured, step-by-step onboarding journey for DIY farmers. There is no single funnel that walks a user from hardware requirements → OS installation → node registration → monitoring → rewards.

  • Hardware Clarity Missing: The site doesn’t provide an up-to-date list of recommended or tested DIY hardware components (CPUs, RAM, SSDs, NICs, etc.). While external vendors sell plug-and-play 3Nodes, the DIY builder community needs confidence that their own builds are compatible.

  • Limited Tokenomics Explanation: The farming reward structure is opaque to a new farmer. The site mentions that TFT rewards are based on capacity, but does not provide an easy-to-use reward estimator, region-based incentives, or clear payout benchmarks based on hardware classes.

  • Underexplained Farming Generations (e.g., V4): The difference between node generations (V2, V3, V4) is mentioned but not fully explained. For DIY farmers evaluating cost vs. reward, understanding why to build for Gen4 or what qualifies a node for Gen3 is essential.

  • No Showcase of Existing DIY Builds: Farmers often benefit from peer inspiration. The absence of a showcase section or gallery of DIY setups, node cabinet builds, or small-scale home racks is a missed opportunity to motivate and reassure.

📢 Community & Support Experience

  • Community Access is Buried: The footer contains links to the forum and Telegram, but a first-time user interested in farming may not realize where to find or ask for help. A "Connect with Other Farmers" section could ease friction.

  • Lack of Peer Success Stories: There's no visible content that showcases real-world farmers, their configurations, their costs and returns, or regional insights. This is especially important for trust-building and motivation.

  • Ambiguous Support Pathways: It’s unclear where a farmer should go when something breaks. There’s no mention of official support channels (e.g., dedicated email, help desk, GitHub issues), which creates a trust gap for new entrants.

🔧 Technical Documentation and DevOps Readiness

  • Zero-OS Documentation is Fragmented: Although Zero-OS is foundational, documentation for installing and troubleshooting it is scattered. There is no beginner-facing landing page introducing it with clear UX.

  • No Clear Update or Maintenance Path: DIY farmers need clarity on how to upgrade nodes, install updates, or ensure long-term support. Currently, version tracking (e.g., ZOS V3) is only mentioned in blog/news updates.

  • Developer/CLI Tools Lack User-Friendly Wrappers: Farmers who aren’t coders may be overwhelmed by the command-line-only interfaces or complex YAML configurations for network registration or workload deployment.

💰 Business Model & Financial Incentives

  • Rewards Need Transparency: There’s no visual tool to simulate TFT earnings based on RAM, cores, SSD size, or uptime. Additionally, information on whether rewards are fixed or variable over time is vague.

  • Token Utility Underexplained: It’s not obvious how TFT can be used (besides trading or holding) or how future INCA tokens will interact with farmer incentives. A "How You Earn & Spend TFT" page would help.

  • No Clear ROI Pathway: Potential DIY farmers likely want to calculate ROI on $500-$2000 hardware investments. No example breakdowns or projections exist.

🎨 Design & Visual Experience

  • Important Farmer Content is Visually Underprioritized: The visual language of the site does not distinguish farming content from general marketing. Sections about how to farm are embedded below the fold or require 2-3 clicks to reach.

  • No Interactive Builder Tool: There’s no configurator or wizard that helps a user determine which hardware they can build or buy based on goals (earn TFT, run AI inference, etc.).

  • Minimal Real-World Imagery: While the site has high-end design and visuals, there are no real photos of people farming, 3Nodes in action, racks in homes, or community builds. This weakens relatability.


To-Do List of Improvements for DIY Farmers

🧭 Navigation & Structure

  • Add a dedicated "Farming" section in the top navigation.
  • Centralize all farming-related content (guides, FAQs, videos, community) under one easy-to-find page.
  • Visually distinguish farmer resources from developer/enterprise content.

📄 Content & Educational Resources

  • Create a step-by-step farming onboarding journey (build, install, register, monitor, earn).
  • Publish a DIY hardware compatibility list with specs and tips.
  • Provide updated documentation on node generations (V3 vs V4).
  • Build a visual TFT earnings calculator.
  • Explain Zero-OS with visuals, installation walkthroughs, and troubleshooting.
  • Create guides for upgrading and maintaining nodes.

📢 Community & Support

  • Add a “Meet the Farmers” testimonial section with regional insights.
  • Promote community support spaces more visibly (forum, Telegram, GitHub, Discord).
  • Clarify support escalation paths (who to contact, where to file issues).

🔧 Tools & Documentation

  • Develop a visual builder tool for node configuration.
  • Provide GUI wrappers or wizards for CLI-based actions (e.g., registration, monitoring).
  • Consolidate all documentation into a user-friendly farming docs hub.

💰 Incentives & ROI

  • Add ROI simulations with example hardware builds and projected rewards.
  • Clarify reward mechanisms (capacity-based, uptime, bonus regions).
  • Explain use cases for TFT, and how future tokenomics (INCA, DAO incentives) tie into farming.

🎨 UX & Media

  • Add photos and videos of real DIY farms, both home-scale and rack-scale.
  • Use infographics to explain the full farming cycle.
  • Make farming options more prominent on homepage and landing pages.
## Website Feedback for Persona 2: Potential/Existing DIY Farmers ### 🧭 Navigation & Information Architecture - **Lack of a Dedicated Farming Hub:** While farming is a core component of the ThreeFold ecosystem, there is no clear, dedicated entry point in the top navigation specifically for farmers. Currently, farmers must navigate through "Take Action" or FAQs to find relevant content, which could be more intuitively organized. - **Scattered Content Locations:** Key farming resources like the [Farm FAQ](https://www.threefold.io/farmfaq/) and the [ThreeFold Forum](https://forum.threefold.io/c/farming) are hosted on separate domains and not clearly linked within the primary site experience. A DIY farmer may not easily discover or know to trust external pages without a centralized information architecture. - **Overreliance on External Docs:** Much of the relevant technical material is located in GitHub repositories or docs.grid.tf, which may be intimidating for non-developer DIY farmers. These resources are critical but need better context and linkage from the main site. ### 📄 Content Relevance & Technical Depth - **Insufficient Step-by-Step Onboarding:** The site lacks a clearly structured, step-by-step onboarding journey for DIY farmers. There is no single funnel that walks a user from hardware requirements → OS installation → node registration → monitoring → rewards. - **Hardware Clarity Missing:** The site doesn’t provide an up-to-date list of recommended or tested DIY hardware components (CPUs, RAM, SSDs, NICs, etc.). While external vendors sell plug-and-play 3Nodes, the DIY builder community needs confidence that their own builds are compatible. - **Limited Tokenomics Explanation:** The farming reward structure is opaque to a new farmer. The site mentions that TFT rewards are based on capacity, but does not provide an easy-to-use reward estimator, region-based incentives, or clear payout benchmarks based on hardware classes. - **Underexplained Farming Generations (e.g., V4):** The difference between node generations (V2, V3, V4) is mentioned but not fully explained. For DIY farmers evaluating cost vs. reward, understanding why to build for Gen4 or what qualifies a node for Gen3 is essential. - **No Showcase of Existing DIY Builds:** Farmers often benefit from peer inspiration. The absence of a showcase section or gallery of DIY setups, node cabinet builds, or small-scale home racks is a missed opportunity to motivate and reassure. ### 📢 Community & Support Experience - **Community Access is Buried:** The footer contains links to the forum and Telegram, but a first-time user interested in farming may not realize where to find or ask for help. A "Connect with Other Farmers" section could ease friction. - **Lack of Peer Success Stories:** There's no visible content that showcases real-world farmers, their configurations, their costs and returns, or regional insights. This is especially important for trust-building and motivation. - **Ambiguous Support Pathways:** It’s unclear where a farmer should go when something breaks. There’s no mention of official support channels (e.g., dedicated email, help desk, GitHub issues), which creates a trust gap for new entrants. ### 🔧 Technical Documentation and DevOps Readiness - **Zero-OS Documentation is Fragmented:** Although Zero-OS is foundational, documentation for installing and troubleshooting it is scattered. There is no beginner-facing landing page introducing it with clear UX. - **No Clear Update or Maintenance Path:** DIY farmers need clarity on how to upgrade nodes, install updates, or ensure long-term support. Currently, version tracking (e.g., ZOS V3) is only mentioned in blog/news updates. - **Developer/CLI Tools Lack User-Friendly Wrappers:** Farmers who aren’t coders may be overwhelmed by the command-line-only interfaces or complex YAML configurations for network registration or workload deployment. ### 💰 Business Model & Financial Incentives - **Rewards Need Transparency:** There’s no visual tool to simulate TFT earnings based on RAM, cores, SSD size, or uptime. Additionally, information on whether rewards are fixed or variable over time is vague. - **Token Utility Underexplained:** It’s not obvious how TFT can be used (besides trading or holding) or how future INCA tokens will interact with farmer incentives. A "How You Earn & Spend TFT" page would help. - **No Clear ROI Pathway:** Potential DIY farmers likely want to calculate ROI on $500-$2000 hardware investments. No example breakdowns or projections exist. ### 🎨 Design & Visual Experience - **Important Farmer Content is Visually Underprioritized:** The visual language of the site does not distinguish farming content from general marketing. Sections about how to farm are embedded below the fold or require 2-3 clicks to reach. - **No Interactive Builder Tool:** There’s no configurator or wizard that helps a user determine which hardware they can build or buy based on goals (earn TFT, run AI inference, etc.). - **Minimal Real-World Imagery:** While the site has high-end design and visuals, there are no real photos of people farming, 3Nodes in action, racks in homes, or community builds. This weakens relatability. --- ## To-Do List of Improvements for DIY Farmers ### 🧭 Navigation & Structure - [ ] Add a dedicated "Farming" section in the top navigation. - [ ] Centralize all farming-related content (guides, FAQs, videos, community) under one easy-to-find page. - [ ] Visually distinguish farmer resources from developer/enterprise content. ### 📄 Content & Educational Resources - [ ] Create a step-by-step farming onboarding journey (build, install, register, monitor, earn). - [ ] Publish a DIY hardware compatibility list with specs and tips. - [ ] Provide updated documentation on node generations (V3 vs V4). - [ ] Build a visual TFT earnings calculator. - [ ] Explain Zero-OS with visuals, installation walkthroughs, and troubleshooting. - [ ] Create guides for upgrading and maintaining nodes. ### 📢 Community & Support - [ ] Add a “Meet the Farmers” testimonial section with regional insights. - [ ] Promote community support spaces more visibly (forum, Telegram, GitHub, Discord). - [ ] Clarify support escalation paths (who to contact, where to file issues). ### 🔧 Tools & Documentation - [ ] Develop a visual builder tool for node configuration. - [ ] Provide GUI wrappers or wizards for CLI-based actions (e.g., registration, monitoring). - [ ] Consolidate all documentation into a user-friendly farming docs hub. ### 💰 Incentives & ROI - [ ] Add ROI simulations with example hardware builds and projected rewards. - [ ] Clarify reward mechanisms (capacity-based, uptime, bonus regions). - [ ] Explain use cases for TFT, and how future tokenomics (INCA, DAO incentives) tie into farming. ### 🎨 UX & Media - [ ] Add photos and videos of real DIY farms, both home-scale and rack-scale. - [ ] Use infographics to explain the full farming cycle. - [ ] Make farming options more prominent on homepage and landing pages.
sashaastiadi added this to the OW Website & Wiki Project 2025 project 2025-04-03 11:05:58 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ourworld_web/HOME#36
No description provided.