Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| human_interface_design [2026/09/14 12:34] – [Users & Key journeys] jade | human_interface_design [2026/09/14 23:41] (current) – [Design discovery] sarah | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Design | + | ====== Design |
| - | + | | |
| - | | + | * **Users & key journeys** |
| - | * **Users & key journeys** Main user types and core tasks | + | |
| * Sarah' | * Sarah' | ||
| * Node steward: setting up the node; onboarding when node is operational; | * Node steward: setting up the node; onboarding when node is operational; | ||
| Line 10: | Line 9: | ||
| * Member of the public or community group: encountering nodes in community spaces; learning about the network project; reporting issues; getting help; becoming a contributor; | * Member of the public or community group: encountering nodes in community spaces; learning about the network project; reporting issues; getting help; becoming a contributor; | ||
| - | * **Design principles** | + | * **Design principles** |
| - | * **Identity directions** | + | * **Identity directions** |
| * Initial ideas from August 2026 Solarpunks meetup: | * Initial ideas from August 2026 Solarpunks meetup: | ||
| * Colours: green to signify renewables / resilience. | * Colours: green to signify renewables / resilience. | ||
| Line 19: | Line 18: | ||
| ====== Design creation ====== | ====== Design creation ====== | ||
| - | * **Identity design** Output: Logo, colour palette, typography, icons / illustrations, | + | * **Identity design** |
| - | * **Sketches & wireframes** Output: Wireframes for key screens and flows | + | * **Sketches & wireframes** |
| - | * **Copy & microcopy** Output: Onboarding text, labels, buttons, messages | + | * **Copy & microcopy** |
| - | * **Visual design** Output: High-fidelity screens and simple style guide | + | * **Visual design** |
| - | * **Usability and accessibility review** Output: Prioritised issues, required design changes | + | * **Usability and accessibility review** |
| ====== Design evolution ====== | ====== Design evolution ====== | ||
| - | * **User testing & feedback** Output: Prioritised issues and improvements | + | * **User testing & feedback** |
| - | * **Design backlog & governance** Output: Ongoing list of UX/UI decisions and future work | + | * **Design backlog & governance** |
| ====== Jade's Thoughts (not gospel) ====== | ====== Jade's Thoughts (not gospel) ====== | ||
| Line 49: | Line 48: | ||
| **Member of the Public** | **Member of the Public** | ||
| - | A potential user who stumbles across us, and may wish to learn about what we do. This is an important category for us in the near term to support adoption. | + | * A potential user who stumbles across us, and may wish to learn about what we do. This is an important category for us in the near term to support adoption. |
| **Site partner** | **Site partner** | ||
| - | Our nodes are all likely to go in locations not run by us. The people running those locations are key partners. There is some similarity to member of the public, in that both might want to learn about how the system is going, but it seems like site partners in particular will benefit from learning about the value they are creating by hosting a node. | + | * Our nodes are all likely to go in locations not run by us. The people running those locations are key partners. There is some similarity to member of the public, in that both might want to learn about how the system is going, but it seems like site partners in particular will benefit from learning about the value they are creating by hosting a node. |
| **Other volunteers** | **Other volunteers** | ||
| - | This should probably be broken up. However, if we look in the moderately near term, at the first two milestones on [[https:// | + | * This should probably be broken up. However, if we look in the moderately near term, at the first two milestones on [[https:// |
| **Unknown Region governance roles** | **Unknown Region governance roles** | ||
| - | Region governance is an unknown space. A LoRes region is a set of nodes across a geography like Merri-bek. There may be decisions to make at that scale. It should neither be top-down, nor should it be a process of autonomous nodes doing whatever they like. Services like training, customer support, and content moderation happen at the region level. | + | * Region governance is an unknown space. A LoRes region is a set of nodes across a geography like Merri-bek. There may be decisions to make at that scale. It should neither be top-down, nor should it be a process of autonomous nodes doing whatever they like. Services like training, customer support, and content moderation happen at the region level. |
| - | + | | |
| - | Additionally, | + | |
| ===== Design constraints ===== | ===== Design constraints ===== | ||
| Line 89: | Line 87: | ||
| This colouring works well for the engineering project. It *may* work well for aspects of the user-facing experience, but maybe not. For facing the community in-general, the following concepts feel important: | This colouring works well for the engineering project. It *may* work well for aspects of the user-facing experience, but maybe not. For facing the community in-general, the following concepts feel important: | ||
| - | * Unordered List Item | + | * Not screaming " |
| + | * Emergency resilient, but the good kind (like the way we feel about the country firefighters) | ||
| + | * Community, local, ours (not really present in the LoRes branding) | ||
| + | * Playful, hack-able, participatory - Like the internet that we used to love, back when we built geocities pages and everyone could have a go. Not slick, not corporate. | ||
| + | * Hope. We can do this. It isn't insurmountable, | ||
| + | * Not screaming " | ||