---
# System prepended metadata

title: Distributed Press - User Design Work
tags: [distributed press]

---

# Distributed Press - User Design Work

###### tags: `distributed press`

Resources:
* https://uxdi.org/
* Simply Secure's User Testing Resources: https://docs.google.com/document/d/10Zy0vbcV_lp94F6K0ucU1yYReHa41H_lU1h2dnWdoBU/edit#heading=h.fgcctngx1yeh


## 2022/11/23 Design Meeting

### Participants
* Ania, Mai

### Agenda:
* COMPOST theme in Sutty
* Back-end user panel
* Communication strategy: 
    * Collaboration
    * Messaging

### Notes
* UXDI - Moved to the phase of ideation and prototyping
    * Meeting 2x/week
    * Tackling two useability issues they chose
        * 1 - Theme selection redesign: Must integrate the COMPOST theme; Possibilities of each theme; Compatibility with dweb
        * 2 - Panel left-column: Add/filter articles (types of content); To turn it into management of existing content and add new content
    * Strategizing solution for these issues, as well as the toggle
        * 2 redesigns and 1 addition
    * Functional analysis with Dev team on interactions
    * What should it be like for users who don't know what dweb is?
    * A few steps to implement it
    * Prototypes for the "toggle" and redesign this Friday
    * Categorize their themes based on their compatibility with DP
        * Ex. Store -- not possible with DP given payment system, etc.
        * Small titles to indicate which themes are compatible
        * Communicate this in a few places; To have it configurable
* COMPOST theme
    * Deadline Nov 30
    * Finished data structure of V0 and being tested
* Communication strategy
    * Sutty
        * Twitter
        * Telegram
        * Instagram
        * Fediverse
    * DP/COMPOST
        * COMPOST Twitter
        * COMPOST Instagram
        * COMPOST Fediverse
        * DP Twitter
        * >> Create DP Fediverse
    * Announcements/messages
        * Collaboration between Sutty, Hypha/DP/COMPOST
        * Centralized vs decentralized solutions 
            * >> Build out messaging around this
            * >> Dig into the "ecosystem" that's been creating solutions for authenticity, documentation, etc which are Starling, Proof, Witness...
        * FFDW partnership announcement
        * Sutty's story of partnerships with collectives
            * How they build out their templates based on need
        * DP Profile
            * X-post from Sutty and COMPOST
        * Messaging towards end-users/target audience
            * Journalists; environmental activists; artists; community networks
            * Those who've been censored; offline communities
            * Small messages for them: "Have you have issues with website takedowns?"
            * Raising awareness of distributed technologies
            * Engage them in discussions about these issues
            * Which experiences have you had with "the old web" and what do you expect from new developments?
        * Technology considerations 
            * How we decide which paths to go down
            * Ex. DIY >> Do It Together
            * What are other similar projects that are doing this work and what do their solutions look like?
        * Concepts:
            * decentralization does not mean isolation, we should be inter-dependent
    * Goals
        * Build awareness around distributed tech
        * Invite and engage people to shape and reflect on the tech
        * 


## 2022/11/08 Design Meeting

### Agenda: Sutty COMPOST theme
* Language
    * Port from Hugo to Jekyll to be managed through Sutty's CMS
    * Independent development from Issue 02 development
        * >> Parallel path 
    * Enable support for other static site generators
    * If plan is to stay on Jekyll, then port issue 02
    * Publishing Issue 03 through Sutty
    * We need a deliverable date for the port
* Format of the port
    * What components to port?
    * Use this: https://miro.com/app/board/uXjVPF0S5V0=/?share_link_id=36429998933


* Theme components
    * Top header
        * change the image
    * Expandable (hamburger) menu
        * Worms > lines
    * Front/landing page
        * "Cover" image - lies left of description on browser; takes up whole space on mobile
        * Issue title + description
    * Support us button on top right
        * support us buttons
            * link + text + color like in donaciones.sutty.nl
        * webmonetization
            * add a url to WM to theme.yml / about.yml that goes on `<head>`
        * if web monetization implemented, animated mushroom moves as long as you are in the page
        * if web monetization is not implemented, the mushroom remains still 
            * not a priority to customize the image but nice to have
            * customizable metadata for the mushroom
        * different buttons for different payment methods
    * bake sale
        * hasn't been used as much
        * encourage sites to go to opencollective
        * it pulls from distributed press api
        * not a priority for port, but check current code to see if difficult
        * ~~sutty already has a way to implement this - doubting about the API - defining if this should be running in the 1st version~~ 
        * TBD - how much value and effort does this imply? Define once we've covered all the components.
    * Piece layout on front page and menu: Image and description
        * Add a media/topic category?
    * Text pieces
        * Side notes: https://two.compost.digital/uncivilizing-digital-territories/#footnote-block-3
            * Mobile: Pops up from bottom
        * Section headers
        * (ani)GIFs for breaking up text
        * Special formats?
    * Other media
        * Javascript embeds
    * Footer menu
        * Image for footer
        * CC license
        * Menu - social; support us
* Open questions
    * Font support
    * Image metadata support - image snippets?
    * Authors - How does "adding authors" work?

## 2022/11/01 Design Meeting

### Agenda
* Check ins

### Notes
* Panel re-design
    * Prioritizing the problems, narrowing issues
    * Survey to rank which problems to prioritize
    * Mapping the information architecture
    * Next week: Plan solution for the problems
    * Then next steps: Implementation, testing
    * Staying loyal to the process
* Issue 03 development?
* COMPOST theme
    * Review features
    * Not just technical aspects, think about creative process of pieces
    * UXDI - Small work in that definition + understanding approach
    * Take into account interactions
    * Cohort involvement in DP implementation
        * Which questions or design issues do we want to discuss with contributors?

### TO DOs
* MAI: Issue development >> Sutty?
* Schedule meeting for Tues Nov 8 
* Sutty: Update Github issues 


## Mai - Sutty Panel Feedback
- My sites
    - "Here are all the sites you can edit" >> "Create site" underneath >>> maybe move the Create Site button or move the "Here are all the..." note to the top of the page?
    - Does the "Publish all changes" button need to be on the My Sites page?
- Website posts page
    - Add "Visit page" button on the posts page
    - "Post types" on the left hand side?
    - License posts gets published every time changes are made?
- Editing posts
    - Change to "post description or content warning" ?
    - Post language "Castellano" >> How to change to English?
- Configurations
    - Contact form doesn't appear even when turned on
    - Site not available at WWW URL when toggle is on 
- "Publishing changes"
    - Explain that site will not reflect changes until "Publish all changes" is clicked


## UX Design Research Participants

### Mai's suggestions
- Community/local-first networks
    - Luandro Viera, Digital Democracy
    - Shafali Jain, Janastu/Servelots
- Collectives
    - Stop LAPD Spying
- Journalists
    - ??
- Artists
    - Look at art.coop directory
- Topics
    - Sex workers rights
    - Reproductive justice
    - Trans justice
    - Environmental justice

## 2022/10/25 - UX Workshop Call
- Mai
- Agus

### Agenda
- Redesign of panel
- Project management help

### Notes
- Redesign of panel
    - Finished looking over the website and the panel to review problems
    - Wrote these issues down **in the Notion** https://www.notion.so/Distributed-Press-4d9abe21e95343d8849ed4f39bce7d55
        - >> Write them into Gitlab, then discuss w developers
    - Vote on the issues to prioritize them
    - Problems and solutions were overlapping
    - Will work through these on Friday's internal meeting
    - There are some obvious general problems with the panel that they want to address
    - Solutions to be identified this week, start implementation next week
- Project management help
    - Disconnection between the different parts - designers vs. developers
    - Daily / 2x a week check in on what's happening?
    - Let's work this out during Thursday's weekly sync



## 2022/10/11 - UX Workshop Call

### Attending:
- Mai
- Elian
- Ania

### Agenda
- Change meeting duration
- UX team update

### Notes
- Team update
    - Big cycle / methodology for the long run
    - Parallel work for the shorter cycle -- 5 steps
    - Short cycle of design
        - Publishing panel usability
        - Toggle for publishing to dweb
        - Defined next steps
            - Understand cycle for the next weeks
            - Ideating, prototyping and testing
    - UX design for the Sutty publishing panel
    - Splitting the user design process
        - Functional development: Modification for their panel w/ DWeb toggl
        - Later milestone: Workshop for onboarding
    - Milestone 1: End of February 2023

## 2022/10/4 - UX Workshop Call

### Attending:
- Mai
- Elian
- Agus
- Ania

### Notes
- Internal roles and availability for the project's UX research side
- Specific tasks for people
- Defining the type of user with their persona
- Research on similar apps and utilities
- Miro board: https://miro.com/app/board/uXjVPQ3ag6M=/
- Notion: https://www.notion.so/Distributed-Press-4d9abe21e95343d8849ed4f39bce7d55
- Discussion
    - Better define user persona(s)
    - Specify concrete use cases
- 2x/week meeting before Tuesday sync


## 2022/9/22 - UX Workshop Call

### Attending:
- Ngoc
- Agus
- Mai

### Agenda
- Overview of the projects
    - DP, Sutty
- Questions with Ngoc

### Notes
- Summary
    - DP, Sutty
    - Looking for common working process and methodology
- Sutty
    - Looking at DOTS
- Semi-structured interviewed
    - Dpeneding on who you talk to, dive into different things as they happen
    - Not about formal vs. informal
    - Are the questions culturally sensitive enough?
    - Open ended questions
- TACTICS
    - Stakeholder mapping: Direct, indirect, and core
    - Ask questions based on their workflow
- Stakeholder interview
    - 2-3 people from each constituent group
    - Better to focus on each group
    - More insightful to dive into group perspective
    - Having different groups together might be fruitful if people ask questions that others might not ask
- Workshop about features?
- Separate workflows, 1:1 individual interviews
    - Identity specific pain points, challenges and use cases
    - Document communication, for transparency, to improve workflows
- MAIN QUESTIONS: 
    - What kind of input are we looking for? 
    - What are we trying to understand about the end-users' needs?

## 2022/9/20 - User Workshop Call

### Attending:

### Agenda
- Review discussion from last week
- Draft plan for UX workshop
- Prepare for meeting with Ngoc

### Notes

- What we have
- 1 - Sutty panel
- 2 - COMPOST theme
- They want to improve their panel back end with a UX process
- Assumptions about how we share that theme with other collectives
- This week integrate COMPOST theme in Sutty
- Next week to use the panel to post to DP with COMPOST theme
- How are we thinking about posting to COMPOST?

Rough draft plan for UX workshop
- Intro to the project
- 10 collectives/partners
    - Interviews/interactions
    - Distinct workshop with those aware of tech and those who are not
    - Community use cases: community networks, journalists, activists
    - Ecological, artistic, experimental users
- Milestone 4: Onboarding and integrations
- Five stages of marketing awareness: [LINK]
https://growthmarketer.co/stages-of-awareness/
    - 5 categories of awareness about their problems and your solution
    - (1-5): Aware of problem, Aware of solution
    - Most cases in DWeb space: Product aware, those more soaked into the technical possibilities
    - Possibility of bringing in other types of groups: Represent those who are majority in Latam
    - Split work to include feedback from those who are not as aware of the tech
    - Insights from those who we think need this tech but aren't aware
- What are the indicators we want to look for?
- What are the use cases, the media formats?
- Relationship they have with their territory/ecology, with artistic experimentation, interest/experience working with intersectionally marginalized groups, formats of publishing on the internet, community journalism
    - How to have proper representation through the groups that we work with
    - Global south and/or vulnerable populations? 
    - Who are the target audiences?

Create a site: panel.sutty.nl

### Discussion Questions
1. Who are the collectives/partners?
    - How can we make the most impact through our selection? Create positive change?
2. How do we ensure that this is an intersectional process?

UDIT: Structure vs. casual feedback -- what do they want to talk about? Pursue interests of threads they're wanting to get into, don't impose and invite rich conversation
* LISTEN, have a good conversation
* What is the space we're exploring?
* How broad / specific do we want to make the conversation?
* What are the decisions that have already been made, or haven't been made?
* "Fuzzy frontend process"
* What are the themes we want to hit during the conversation?

TO DO:
- Add elian to element chat
- Mai, Elian/Agus: Think up who we want to interview