---
# System prepended metadata

title: 'Solid Team: Website Revamp'

---

# Solid Team: Website Revamp
## Agenda
* Overview of website (What webpages should go what should stay)
* Desired pages
* Expected timeline
* Responsibilities/Action Items 

## Action Items
- [ ] Marrelle to collect bios from Virginia and Kyra and update her own bio for the Team page on the website
- [ ] Jeff to collect the information about the team (who is an admin, creator, editor, etc)
- [ ] Marrelle and Kay to investigate using Matomo on sp.org for analytics tracking
- [x] Vincent to find prior user research
    - done: https://gitter.im/solid/team?at=60ae71683d43a15a65c9aa5f
- [x] Someone to ask the guy in the community (schriver?) who has been involved in lots of communities, whether he has any community models that he likes that we should investigate
- [ ] Someone to take a look at the IPFS community and see how they structure it, and what we could take away from it

## User Research Action Items
- [ ] Kyra and Virginia to create an outline of the user research plan and share with everyone
    - This will include a schedule for user interviews
    - Jeff, Marrelle, Kyra, Justin, and possibly Vincent have volunteered to be involved
- [ ] Kyra and Virginia to publish doc where everyone can review and contribute questions for the **DEI/Community survey**
- [ ] Kyra and Virginia to publish doc where everyone can review and contribute questions for the **Persona User Interviews**
- [ ] Kyra and Virginia to present user research plan/progress at the next Solid Team meeting


## TL;DR
* The website revamp is coming together - the pages are being updated
    * Justin is testing running the website on community server (Solid)
    * Jeff is implementing a website on a Solid pod that gives all the info about the Solid project process and organization.
* Everyone agreed that user research is needed in order to know how to best move forward with redesigning the website and community
    * We need to develop personas through user interviews
    * We are going to have a DEI & Community survey
    * We are going to investigate adding Matomo to collect more analytics on the website
* We realized that we are in need of advocacy roles in the community, but we're going to need to get our user research done first to determine who these people would be and how to involve them
* We are going to investigate whether there are any communities out there already that we could model after


## Meeting Notes
* Jeff has made [a diagram](https://github.com/solid/process/issues/132#issuecomment-848628989) to help understand the Solid team structure

### Overview of Website
* Rewriting the About page
* Developer page - there are subpages that have updated images now
* We are changing how we store the Solid application, so the page will be changed to reflect that
* Community subsection that has the events, forums, gitter, etc
  * The newsletter isn't changing
  * Maybe we should include a blog page where community members and the Solid team can publish blogs
* Reorganize the Teams page to make more clear/less daunting
* About Solid page
    * Four subsections: Specs, How to engage, Origin Story, Team
    * Teams page needs to be updated for additions and changes in roles
        * Bios for Marrelle, Virginia and Kyra are forthcoming
* There needs to be a list for who is an admin, a creator, an editor, etc
    * The process repo has some of this in it, may not include everybody
    * It's out of date, so we should update it
* Justin is testing running the website on community server (Solid)
    * If we're representing the team structure in RDF, the home for it will be solidproject.org.
    * We can store the RDF there that can be used as source, and we can use some generation from it as well
    * There are some things like directory indexes and pretty urls where an nginx proxy can turn it into a webserver, but we can also use it as a pod for data operations separately
    * What Jeff is working on lives on a Solid pod, so we can have it as soon as it goes into main in github, it goes live on the site
    * What's the authoritative source for this info? It should be linked data on the site itself
    * It will run off CSS so it will be like a big pod
* **Action Item:** 
    * Jeff is implementing a website on a solid pod that gives all the info about the solid project process and organization. There's a central place where everything is stored using linked data and the website is generated from that
        * So you can say, "show me all the executive teams, show me all the members of them"
    * Action item is collecting all this information

### Desired Pages for the Website
* There are lot of pages, let's condense them/clean 'em up
    * For example, the page for the Solid Team where it has Community, Forum etc, it could be a contact us page that has all the links there
* Justin isn't as concerned with the number of pages as long as they are helpful
    * We can be more consice
    * In terms of developers and users - a lot of users are developers, so it's more about what you're looking to do. Do you want to develop something, or use applications (splitting by persona)
    * Specficiation page has been slotted to be updated for a while to actually explain the spec in a TLDR format (i.e. this is what it includes, this is what's coming)
    * Could use an explanation of the security model of solid, and an explanation of the roadmap
    * If people want to know about Solid and understand it, we don't do enough explanation of explaining solid and the core values around it
* Oz asks who is the target audience 
    * We've done a kind of "everyone" approach, but we should specify more detailed target audience to address those needs
        * Developers
        * Pod Providers
        * Learning about the Spec
        * People who want a pod because they're checking it out
    * Inrupt's website is organized around Enterprises, developers and users, but Solid is a larger group of people
* Kyra suggests doing user testing like navigation and card sorting to determine what pages are useful and how to navigate to them 
* Kay wonders if we have analytics on the pages to see how used they are
    * Our community doesn't like it when we use analytics/tracking software
    * We could use Matomo (which is used by Inrupt)
        * Marrelle and Kay know how to use it and set it up
* Marrelle suggests Solid is more of an ecosystem
    * There are about [six communities](https://www.canva.com/design/DAEfdLjqr2Y/nIKnXYosrR-HGL4Qny4kjQ/view?utm_content=DAEfdLjqr2Y&utm_campaign=designshare&utm_medium=link&utm_source=sharebutton)
        * Privacy & Security
        * Legal
        * General Use
        * Developers
        * Academics
        * Commercial
* There are 3 different things on the website:
    * What Solid is
    * What's going on 
    * How you can get involved
        * Jeff would like to see this section become more of a main focus
            * (many people nod in agreement)
    * It's not just that we have a legal community, it's how do we (and they) get involved, what can they do here

* **Action Item**:
    * Figure out who the different groups are in the community and the pathways they are working in the space by doing user research
    * Come up with script to query users in the different communities we're looking at in order to develop personas
        * Volunteers:
            * Marrelle 
            * Jeff
            * Kyra can help out with structuring the user research 
    * Marrelle can create a doc to collaborate on the user research questions
    * Then triage the questions, prepare the script, go out and research and come back and data analysis
        * Marrelle to create doc
        * Everyone else to add questions
        * Marrelle to create Typeform for survey
    * User Interviews
        * Jeff, Marrelle, Kyra, Justin, possibly Vincent

* Oz questions whether there are any communities out there already that we could model after
    * Solid is so unique and different that it is difficult to find similar communities to emulate
    * There's a guy in the community (schriver?) who has been involved in a lot of different communities, and he's given some examples of other communities -- he might be a good resource
    * IPFS community could be interesting to look at
* Kyra suggests this might be the starting point for personas, and that maybe we can go out and talk to them to see how they are interacting in the community
    * Can come up with a script to go out and talk to people
    * Vincent says there is prior user research on card sorting and user testing that we can look into

* Action Item:
    * Vincent to find prior user research - done: https://gitter.im/solid/team?at=60ae71683d43a15a65c9aa5f

* Oz asks whether it's even a good idea to have a "one stop shop" for all these personas
    * Usually people mean the "developer" community when referring to the Solid community
    * Others refer to the specification community
    * There's value in having it all in one place, but maybe it becomes too overwhelming
* Marrelle realized that it's hard to have many voices, and there should be a leading voice in all these communities
    * For example, Inrupt is a leader in the commercial space
        * Ruben is a leader in the academic space
        * Vincent, Nicolas promote applications etc in the developer community
    * It's time for people to have a voice, a leading voice. It can't just be one person for everything
    * Who is the Solid team if we are not the leading voices in these communities?
        * First step would be identifying who the leading voices in the different constituencies are (ideally representative of the wider community, i.e. not just from a single community).
* Oz: We (=Inrupt) have people/customers in different verticals (i.e. Sweden) that could become involved
* The area of outreach to other communities is something we don't have a position in the organization for
    * Maybe there should be another team that outreaches to other communities
    * Is this something the DEI team could do? 
        * Possibly- Jeff thinks DEI is slightly different than outreach and advocacy, since it involves a bit more in terms of involvement in different communities
* We are in need of advocacy roles, but it's going to circle back to personas (dev advocates, legal advocates)
    * And even within that, there will be different advocates, for example, for different languages (Python, Go, etc)
* How do we get advocacy in different areas?
    * We'll have to do some research
* Kyra suggested that the DEI time is planning on creating a survey, so we should put the community survey questions in with that
    * Everyone agrees
* Action Item:
    * Kyra and Virginia to create a place to accept questions for the DEI/Community survey
* Let's plan to make these action items happen in the next two to three weeks
* Kyra and Virginia to present user research effots at next Solid Team meeting

