git ssb

0+

Zach! / ssb-onboarding-DEFUNCT



forked from business-zach / ssb-onboarding-DEFUNCT

Commit 4257c9899f3051a9e26cf652d06a1826eb51165d

Added Revamp Sketches

I began to add documentation on how to revamp scuttlebutt.nz.  This is
the start of that documentation
Zach committed on 10/30/2017, 1:53:02 AM
Parent: 19b4a42210c21c02314de286d081a4ff8b891d72

Files changed

non-dev-resources.mdadded
resource-revamp.mdadded
non-dev-resources.mdView
@@ -1,0 +1,137 @@
1+## Proposal for Scuttlebutt Resources for the non-technically minded.
2+
3+# Goal
4+
5+This project will develop a set of resources that articulate the spirit of Scuttlebutt and all its
6+awesome potential, but targeted to people who are not developers or technological hobbyists. With
7+these resources, our network is accessible to a larger group-- who can get onboarded and active
8+without needing to understand github, node dependencies, or the malleable and nuanced definition of
9+a pub.
10+
11+These resources would proudly display our existing, beautiful solarpunk weirdness, so people are
12+drawn to the culture of this community as much as to the promise of its tech.
13+
14+# How it Would Work
15+
16+We would create a set of videos, articles, and other illustrative materials that succintly
17+articulate what scuttlebutt is, why it's unique, and why someone would want to join. We would also
18+create an equally rich set of materials that help people once they've joined, to help them make
19+sense of the space and quickly feel at home. These resources would all live on scuttlebutt.nz so we
20+have a simple link to give friends interested in Scuttlebutt, but would be clearly separate from the
21+existing tech documentation already there.
22+
23+While the resources would work together to give a nuanced, helpful introduction to our 'verse; they
24+would also be designed to work on their own and without any context. In this way, each piece could
25+be shared through the old internet's existing channels as interesting standalone pieces, but they
26+would lead people to scuttlebutt.nz and all the other riches to be found there.
27+
28+# Examples of Resources to be Made with this Grant
29+
30+**Introduction to Scuttlebutt in Less than 3 Minutes**
31+
32+A video that explains the key, cool concepts of Scuttlebutt, and how its different from other social
33+networks. This video would be 3 minutes or less, and offer a bright and humorous entry point to our
34+world to encourage folks to learn more (and lead them to longer, more in-depth videos like "an SSB
35+love story")
36+
37+**Revised Landing Page for Scuttlebutt.nz**
38+
39+A simpler homepage for scuttlebutt that succintly explains the spirit of our community. This page
40+would then invite people to learn more on either two paths: one path is if you want to join this
41+community, and another would be for if you want to build stuff for this community. With this, we
42+can more clearly delineate the awesome technical stuff from the awesome non-technical stuff, and not
43+overwhelm the curious with too much information at once.
44+
45+**Simple Animation Explaining what to Expect when you first join Patchwork**
46+
47+Patchwork is the most accessible of our clients, currently, but can still be confusing to new
48+people. But we can build a simple GIF that shows what you can expect when you first install and
49+open it, what you'll see when you join a pub, and how to start talking. This GIF could then live on
50+our revamped page, so people have context for this client their currently downloading, and what
51+they'll want to do next.
52+
53+**What It Means to "Send a Message" or "Post an Update" on a Centralized Network**
54+
55+In the same spirit of writing accessible introductions to the technical processes of Scuttelbutt, we
56+should write how analogous things work on a centrallized network. These networks have obfuscated
57+their technical side so that it all just seems like simple magic, It's harder than to express why
58+exactly a decentralized network is important to someone who doesn't understand how their facebook
59+feed is "centralized" in the first place. This would be a video/article that breaks down step by
60+step what happens when you send a FB message to your grandma, and what happens when you post
61+a status update about your feelings on twitter. Through these illustrations, the core flaws of
62+these programs will be made more clear, and offer better context for discussing why the technical
63+aspects of SSB are important.
64+
65+**How to Throw an SSB Party**
66+
67+An awesome way to get started with SSB is to have a bunch of your friends all join on the same local
68+network and you see how the tech works on a personal level. Also, there are many users who find SSB
69+on their own and then want to get their own friend group on board. This article would detail a good
70+way to throw an SSB party, and things to consider beforehand, and the proper preparations to take.
71+The list would be written in a humorous style so it can be enjoyed on its own, though each point
72+will still be valid.
73+
74+**Markdown Style Guide**
75+
76+An easy-to-miss stumbling block for our clients is not knowing how to properly write messages in
77+them. Markdown is common in tech, but not as common outside of it. Producing a markdown style
78+guide that can be incorporated into our clients would help people confidently post. This guide
79+would be short and sweet but incorporate SSB's peculiarities (how to attach your own images, for
80+example, or how to mention different channels and people) and the examples of the guides would give
81+a way to share our culture in small silly ways.
82+
83+**SSB Compared to other Clients/Networks**
84+
85+SSB is it's own beautiful thing, which means it's kinda like (but not quite like) a bunch of other
86+things. When I introduce SSB to my friends, I find this often creates a mental blocker for getting
87+started. They will think "Oh! So this can replace our signal group" or "I can use this instead of
88+slack" or some other application, and then are frustrated when it doesn't quite match what they
89+expect. A small guide comparing SSB and its various clients to other well-known
90+messaging/socializing platforms can help people find the right context for joining and keep them
91+from being frustrated that SSB doesn't do something it wasn't necessarily setting out to do (at
92+least yet).
93+
94+**What is Solarpunk?**
95+
96+This identification has gained an incredible life within the scuttleverse, and it is a relatively
97+new genre/marker within the larger world. While the word sounds so nice, it's not immediately clear
98+what "solarpunk" means. Having an article outlining how we define solarpunk and how it's expressed
99+within the network (from Spider-Farm to Dominic coding ssb on a solar-powered computer to our
100+practical discussions of airship manufacturing and governance without oppression) will help people
101+understand this term and encourage solarpunk seekers to be a part of this community.
102+
103+**Tips for Getting Started**
104+
105+Someone can install patchwork, and join a pub, and see a feed starting to fill up...but still not
106+know how to participate or what any of it means. Some cultural tips for getting started on SSB can
107+give that proper foothold. This would be a video/article about how to post, and what to post. How
108+to subscribe to a channel, and what a channel means. The difference between public and private
109+posts, Some popular topics to check out, and other encouragement to help new folks express their
110+unique selves within our unique 'verse.
111+
112+**And more to discover as all these get made!**
113+
114+# Why I Want to Work on this Project
115+
116+I am not a developer, and would not describe myself as technically minded. While I'm definitely
117+interested in technology and how it affects humans and history, that is not what drew me to SSB.
118+Instead, I found out about this protocol while I was on Tumblr browsing through the solarpunk tag
119+and found Andre Staltz' article. I am so thankful for that article because Scuttlebutt has become
120+such an important home for me. And I can remember how intimidating it was to make my first post
121+into this world, and how welcoming everyone was immediately. So I have a personal relationship to
122+the cultural, non-technically specced side of SSB and know the impact it can have ona person.
123+
124+I've worked on articulating SSB in non-technical ways (the SSB Love Story video on scuttlebutt.nz
125+being the most immediate example), and know I have a good aptitude for it, and so want to continue
126+on the path I've found myself on.
127+
128+Lastly, my experience is in art/comedy, and this world is where much of my physical friend group
129+lives. I have a personal attachment to creative scenes, and can see how much the current online
130+systems oppress and depress them. I know so many people would flourish on this network, and am
131+excited about the awesome things we can all build together when devs and non-devs share this space.
132+And so I want to try to reach out to as many different groups as possible and welcome them onboard,
133+so they can help us build the future together.
134+
135+
136+
137+
resource-revamp.mdView
@@ -1,0 +1,85 @@
1+# Scuttlebutt: The Social Network of the Future, Available Today
2+
3+# Summary
4+
5+This article details a way to approach the revamping of scuttlebutt.nz. It aims to set distinct
6+goals for this webpage, then outline new content or design revisions that can help achieve these
7+goals.
8+
9+# Goals
10+
11+1. Scuttlebutt.nz is the most accessible entrypoint for people curious about the wonders of
12+ Scuttlebutt. It's design and content, then, should be accessible and wonder-filled to as many
13+ types of people as possible.
14+
15+2. An incredible culture is forming within the scuttleverse. It is supported by the technical layer
16+ in a way unprecedented in a social network,, but its also supported by people actively seeking
17+ out this type of community. This culture is an antidote to the depressed, competitive panic of
18+ standard social media. Scuttlebutt.nz is a great vehicle to broadcast this culture to people who
19+ are seeking something different, but did not know how to articulate it.
20+
21+3. We have a ridiculous amount of talented developers nad technologists who understand the potential
22+ of Scuttlebutt, and want to help build this future, but are unsure where to start. They are
23+ desiring more technical specs and documentation for how to build in this space. Scuttlebutt.nz
24+ can be the basecamp for these adventurers.
25+
26+# My Vision, In Short
27+
28+We create a classic landing page for scuttlebutt.nz that presents the idea of SSB in as simple and
29+elegant of a way as possible. We remove any auxillary/unnecessary information from this landing
30+page, and remove any formatting that could overwhelm or confuse non-technical vistors. The landing
31+page would then offer two entrypoints into the larger ssb-handbook: One for people curious about
32+a new social network, and one for people eager to build upon this network.
33+
34+For those non-technical but curious, we create resources that communicate the spirit and excitement
35+of SSB without needing to know much technical stuff. Additionally, we make resources that
36+illustrate why this technical stuff is important (i.e. why decentralized matters, and what exactly
37+it means for something to be centralized). We also proudly lean into the culture that's growing
38+here, and use this as defining elements in our content. We do not try to present SSB as a network
39+that works for all people. We present it as radical and lovely and strange as it actually is, and
40+set our audience to be folks looking for their tribe, their people, who didn't realize this type of
41+tribe _could_ exist.
42+
43+For the technical-minded we flesh out the documentation for how all of this works, with tutorials
44+for entry points into development (how to set up your git-ssb repo, how to set up your own pub, how
45+to build a simple module for patchbay, etc.). We consolidate the blog posts and documentation
46+already around the scuttleverse and (with permission) republish it on this central homepage.
47+
48+Lastly, we research how the internet and social media is used by different communities/users today,
49+and document this research. If we want to appeal to artists and generl non-devs, then we should
50+understand more what their life is like now, and build up a body of research around how people
51+interact with the online, and what makes them exhausted and depressed and looking for something
52+else. With these interviews and studies available to many people, we can better build applications
53+that answer the needs of these communities and build instructional content that speaks to their
54+heart.
55+
56+# My Vision, In List Form
57+
58+1. Build a new landing page for Scuttlebutt that elegantly introduces the concept of SSB then offers
59+ two paths to learn more: one for people who want to join this community, and one for people who
60+ want to build for this community.
61+
62+2. Develop stronger, and more accessible, content for the non-dev, non-techie identifying folks who
63+ want to join this community.
64+
65+3. Consolidate our current tech documentation and then flesh it out and make it more accessible to
66+ techie-identifying folks who want to build out the network more.
67+
68+4. Build up a body of research into the lives and needs of different groups of people: artists,
69+ musicians, scene-supporters, fans, to see how they exist online today, and what their dream of
70+ a connected future would be. Use this research to build out our clients and protocols to better
71+ answer the needs of these communities, and to write up content that better speaks to these peer
72+ types.
73+
74+Each of these are rich enough projects to warrant their own grant, but connect together to make an
75+incredible strong whole. I would propose we take on each one individually, but aware of the grander
76+vision. Personally, I know that I could not help much with point 3--but would benefit from it if
77+other people were able to tackle it. I _can_ help with points 1,2, and 4 and in the following pages
78+write out my proposals for each.
79+
80+# Individual Proposals
81+
82+[1. New Landing Page](landing-page-proposal.md)
83+[2. Non-Dev Resources](non-dev-resources.md)
84+[3. Dev Resources](dev-resources.md)
85+[4. Research into Communities](research-proposal.md)

Built with git-ssb-web