case_study:indieweb
Differences
This shows you the differences between two versions of the page.
case_study:indieweb [2020/11/29 13:36] – created - external edit 127.0.0.1 | case_study:indieweb [2024/01/20 20:34] (current) – jgmac1106 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | + | Introduction |
- | < | + | |
- | <p>These case studies will evolve as we have switched methodologies</p> | + | These case studies will evolve as we have switched methodologies |
- | <p>IndieWeb is a community of people build and use personal websites as “a people-focused alternative to the ‘corporate web& | + | |
- | <p>By contrast with the other case studies presented in this book, IndieWeb was not built by educators with pedagogy as its primary purpose. Instead, it was created by web developers with the goal of taking control of their online identity. ~It holds lessons for open pedagogy through its members& | + | IndieWeb is a community of people build and use personal websites as “a people-focused alternative to the ‘corporate web’” |
- | <p>Whereas the previous cases highlighted ways in which open pedagogy extends beyond the classroom, IndieWeb lacks formal roots in educational traditions altogether. It is not pedagogy brought into the wild, but instead is of-the-wild in the first place. The learning and knowledge sharing that occurs at this site provide valuable insights about how open pedagogy can thrive beyond the confines of the classroom.</p> | + | |
- | <h2>History</h2> | + | By contrast with the other case studies presented in this book, IndieWeb was not built by educators with pedagogy as its primary purpose. Instead, it was created by web developers with the goal of taking control of their online identity. ~It holds lessons for open pedagogy through its members’ shared practices of creating websites and related tools, which present a model for self-directed learning in a community devoted to openness. |
- | <p>IndieWeb was conceived after co-founders Aaron Parecki and Tantek | + | |
- | <p>The group wanted a more production based approach " | + | Whereas the previous cases highlighted ways in which open pedagogy extends beyond the classroom, IndieWeb lacks formal roots in educational traditions altogether. It is not pedagogy brought into the wild, but instead is of-the-wild in the first place. The learning and knowledge sharing that occurs at this site provide valuable insights about how open pedagogy can thrive beyond the confines of the classroom. |
- | <p>The following year in 2011 the group worked to organize the first IndieWeb Camp event in Portland, Oregon. The event was focused on discussing and building tools to own one's own data on a personal website " | + | History |
- | <p>Amber Case explained why early on IndieWeb camp put such a focus on building from your own site first." | + | |
- | <p>IndieWeb’s commitment to making extends through its communication systems. After the event, a decision was made not to keep in touch via an email list, but instead to use the Web itself. | + | IndieWeb was conceived after co-founders Aaron Parecki and Tantek |
- | <p>IndieWeb has grown significantly in the intervening years. Between 2011 and 2018, IndieWeb' | + | |
- | <h2>Shared Goals as Community</h2> | + | The group wanted a more production based approach " |
- | <p>Overall having your own place on the web is the rallying cry of the IndieWeb. As one member notes, "Have a home, express myself, and internet citizenship" | + | |
- | <p>IndieWeb’s community is oriented around a belief that building personal websites can be a means to empowerment.</p> | + | The following year in 2011 the group worked to organize the first IndieWeb Camp event in Portland, Oregon. The event was focused on discussing and building tools to own one's own data on a personal website " |
- | <p>As one participants notes:</p> | + | |
- | <p>Now I’m not a Web Developer, but I think I’d like to try my hand at it. I don’t need to centralize all of my data but I would like an online presence that I control. Something that I could constantly work on. Something that’s never finished. Much like the web itself.</p> | + | Amber Case explained why early on IndieWeb camp put such a focus on building from your own site first." |
- | <p>The building your own space also connects to the shared value of "show don't tell." The idea of showing before talking became a central organizing tenant of IndieWebCamp. In fact the first principle suggested by the community revolved around self dogfooding:</p> | + | |
- | <p>Eat your own dogfood. Whatever you build should be for yourself. If you aren't using it, why should anybody else? More importantly, | + | IndieWeb’s commitment to making extends through its communication systems. After the event, a decision was made not to keep in touch via an email list, but instead to use the Web itself. |
- | <p>While there is debate to the etymology of the term of " | + | |
- | <p>This driving principle influences much of the early web community. In fact in the community detailed how they were not planning for the masses and specifically noted they "were not designing for all." While this did create inequities and reinforce traditional barriers of access in technology it assumed a smaller platform for testing and developing technology.</p> | + | IndieWeb has grown significantly in the intervening years. Between 2011 and 2018, IndieWeb' |
- | <p>This is why I think it is exciting that the IndieWeb inherently follows this method. Work small, demo, integrate into the whole what works, and you get this emergent structure out of that that’s resilient, with things evolving at the edges out of people exploring new projects. (Case, 2014).</p> | + | Shared Goals as Community |
- | <p>These examples highlight personal empowerment | + | |
- | <p>Overall community is essential in to IndieWeb and much of the energy originally poured into code by key organizers and founders now goes to to supporting the community. There are 3726 mentions of community minus WordPress and Mozilla. 4027 mentions of community when you include allies. 311 mentions of diversity, 113 results for inclusion, | + | Overall having your own place on the web is the rallying cry of the IndieWeb. As one member notes, "Have a home, express myself, and internet citizenship" |
- | <p>" | + | |
- | <p>As well as IndieWeb' | + | IndieWeb’s community is oriented around a belief that building personal websites can be a means to empowerment. |
- | <p>[This] is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future. --<a href=" | + | |
- | <p>This highlights IndieWeb' | + | As one participants notes: |
- | <h3>Membership and Barriers</h3> | + | |
- | <ul> | + | Now I’m not a Web Developer, but I think I’d like to try my hand at it. I don’t need to centralize all of my data but I would like an online presence that I control. Something that I could constantly work on. Something that’s never finished. Much like the web itself. |
- | <li>Defining membership</li> | + | |
- | </ | + | The building your own space also connects to the shared value of "show don't tell." The idea of showing before talking became a central organizing tenant of IndieWebCamp. In fact the first principle suggested by the community revolved around self dogfooding: |
- | <ul> | + | |
- | <li>Operating a personal website with indieauth, webmentions, | + | Eat your own dogfood. Whatever you build should be for yourself. If you aren't using it, why should anybody else? More importantly, |
- | <li>Logging in to IndieWeb.org, | + | |
- | <li>Peripheral communities (use of #indieweb and related hashtags on Twitter); IndieWeb sites can POSSE to communicate with people on various platforms</li> | + | While there is debate to the etymology of the term of " |
- | </ul> | + | |
- | < | + | This driving principle influences much of the early web community. In fact in the community detailed how they were not planning for the masses and specifically noted they "were not designing for all." While this did create inequities and reinforce traditional barriers of access in technology it assumed a smaller platform for testing and developing technology. |
- | <li>Identifying barriers</li> | + | |
- | </ul> | + | This is why I think it is exciting that the IndieWeb inherently follows this method. Work small, demo, integrate into the whole what works, and you get this emergent structure out of that that’s resilient, with things evolving at the edges out of people exploring new projects. (Case, 2014). |
- | < | + | |
- | <li>Requirements to be a builder</ | + | These examples highlight personal empowerment |
- | </ul> | + | |
- | <ul> | + | Overall community is essential in to IndieWeb and much of the energy originally poured into code by key organizers and founders now goes to to supporting the community. There are 3726 mentions of community minus WordPress and Mozilla. 4027 mentions of community when you include allies. 311 mentions of diversity, 113 results for inclusion, |
- | <li>Initially, formal requirements, | + | |
- | </ul> | + | " |
- | <ul> | + | |
- | <li>Cost of operating personal website</li> | + | As well as IndieWeb' |
- | <li>Technical skills for operating personal website</li> | + | |
- | </ul> | + | [This] is about staying in touch with current friends now, rather than the potential of staying in touch with friends in the future. --https:// |
- | < | + | |
- | <li>Models for growth</li> | + | This highlights IndieWeb' |
- | </ul> | + | Membership and Barriers |
- | <p>It is somewhat difficult to draw boundary defining IndieWeb’s community. The creator of indiemap.org, | + | |
- | <p>There are other avenues to legitimate engagement with IndieWeb’s community such as attending IndieWeb Camps, Homebrew Website Clubs, or engaging in conversations online. Furthermore, | + | Defining membership |
- | <p>Operating a personal website requires a personal investment of time, as well as a financial investment to register a domain name and usually to pay for web hosting. This presents a potential barrier for participation, | + | |
- | <p>" | + | Operating a personal website with indieauth, webmentions, |
- | <p>After 2014, when & | + | Logging in to IndieWeb.org, |
- | <p>The relaxation of the membership requirements also aligned with a large increase of press in 2013-2014, | + | Peripheral communities (use of #indieweb and related hashtags on Twitter); IndieWeb sites can POSSE to communicate with people on various platforms |
- | <p>Still, technical barriers existed that made much of the IndieWeb unavailable to the masses. As noted this was by design. " | + | |
- | <p>Designing for "mass adoption" | + | Identifying barriers |
- | <p>It's a form of distraction: | + | |
- | <p>This approach, while drastically increasing barriers to entry also protected the community of developers. There are two main developers and maintainers of all the IndieWeb WordPress themes and plug-ins. The focus on self-dogfooding versus building for the masses ensures tools get iterated and tested by the needs of the maker.</p> | + | Requirements to be a builder |
- | <p>This is related to Indieweb’s commitment to implementation over ‘the best story& | + | |
- | <ul> | + | Initially, formal requirements, |
- | <li>Plurality - build for oneself, support multiple impelmentations interoperating</li> | + | |
- | <li>Plurality as a means of resolving disagreement</li> | + | Cost of operating personal website |
- | <li>Establishes a convention where the ability to build is an important part of having one’s voice heard. Disagreements may be addressed rhetorically through discussion, but if this is insufficient, | + | Technical skills for operating personal website |
- | </ul> | + | |
- | <p>To this end the community has used a model that groups indieweb adopters into " | + | Models for growth |
- | <p>While the Generations page has not been seriously updated since 2014 the community has made strides to redefine loose membership as</p> | + | |
- | <p>"Be able to share and discuss and publish from your own website and ideally from your own domain name in a way that is not adversely controlled by another company" | + | It is somewhat difficult to draw boundary defining IndieWeb’s community. The creator of indiemap.org, |
- | <p>In 2018 the barrier to membership and events was lowered further with a goal of attracting more event organizers. At the 2018 NYC leaders meeting it was decided to add an entry level event of IndieWeb meetup for people who found the word " | + | |
- | <p>Membership in the community was also signified by the use of microformats, | + | There are other avenues to legitimate engagement with IndieWeb’s community such as attending IndieWeb Camps, Homebrew Website Clubs, or engaging in conversations online. Furthermore, |
- | <p>While symbols hold communities together (Dewey) and often unite affinity spaces (Gee) they can also act as walls for potential members who may not understand or choose to adopt these sign systems. In terms of the IndieWeb community discussions around web standards historically reflected an argumentative discourse prevelant. The founders themselves cite the " | + | |
- | <p>While recent efforts have been made to reduce " | + | Operating a personal website requires a personal investment of time, as well as a financial investment to register a domain name and usually to pay for web hosting. This presents a potential barrier for participation, |
- | <p>While the majority of those who self identify as IndieWeb use microformats to connect their website they do now use a membership gateway of " | + | |
- | <p>Overall microformats demonstrate the power of signs and symbols to sustain a community. In terms of socio-technical system the use of microformats also acted as a barrier to membership. While still in compliance with web standards microformats works on websites the same way as CSS, which controls the way pages look such as colors and fonts. This caused large technical difficulties for CMS platforms. A recent proposal (IndieWeb/ | + | " |
- | <h3>Leadership and Barriers</h3> | + | |
- | <p>Given the already stated barriers of access inherent in the community, the access to leadership still aligns well to Gee's Affinity space model. To attend, what was called the " | + | After 2014, when Çelik |
- | <p>Efforts have been made to increase the number of organizers and to diversify leadership. Recently the decision was to change from ' | + | |
- | <p>With so many global events privledge, as in many facets of life, also creates barriers to leadership. Many organizers have professional arrangements with employers or work remotely as digital nomads. While a remote feed is made available hours of household silence maybe impossible in households with children (private citation).</p> | + | The relaxation of the membership requirements also aligned with a large increase of press in 2013-2014, |
- | <h2>Content Creation</h2> | + | |
- | <p>Creation is a central feature of IndieWeb.</p> | + | Still, technical barriers existed that made much of the IndieWeb unavailable to the masses. As noted this was by design. " |
- | <p>Building personal websites requires (at least) two types of creation. First, one must design the site itself, choosing a visual style and information structure that fits one's purpose. Second, one must populate the site with content.</p> | + | |
- | <p>Most of IndieWeb' | + | Designing for "mass adoption" |
- | <p>Although the overall breadth of content on IndieWeb sites parallels that of social media platforms, the scope of any given individual website varies significantly. Determining a unique blend of content-types for one's website eludes to Franklin' | + | |
- | <p>Beyond personal websites themselves, IndieWeb' | + | It's a form of distraction: |
- | <p>Examples of IndieWeb building blocks</p> | + | |
- | < | + | This approach, while drastically increasing barriers to entry also protected the community of developers. There are two main developers and maintainers of all the IndieWeb WordPress themes and plug-ins. The focus on self-dogfooding versus building for the masses ensures tools get iterated and tested by the needs of the maker. |
- | < | + | |
- | < | + | This is related to Indieweb’s commitment to implementation over ‘the best story’ |
- | < | + | |
- | <td colspan=" | + | Plurality - build for oneself, support multiple impelmentations interoperating |
- | <p>Type of building block</p> | + | Plurality as a means of resolving disagreement |
- | </td> | + | Establishes a convention where the ability to build is an important part of having one’s voice heard. Disagreements may be addressed rhetorically through discussion, but if this is insufficient, |
- | <td colspan=" | + | |
- | <p>Example</p> | + | To this end the community has used a model that groups indieweb adopters into " |
- | </td> | + | |
- | </ | + | While the Generations page has not been seriously updated since 2014 the community has made strides to redefine loose membership as |
- | < | + | |
- | <td colspan=" | + | "Be able to share and discuss and publish from your own website and ideally from your own domain name in a way that is not adversely controlled by another company" |
- | <p>Technical standard</p> | + | |
- | </td> | + | In 2018 the barrier to membership and events was lowered further with a goal of attracting more event organizers. At the 2018 NYC leaders meeting it was decided to add an entry level event of IndieWeb meetup for people who found the word " |
- | <td colspan=" | + | |
- | <p>The Webmention standard is used to send ' | + | Membership in the community was also signified by the use of microformats, |
- | </td> | + | |
- | </ | + | While symbols hold communities together (Dewey) and often unite affinity spaces (Gee) they can also act as walls for potential members who may not understand or choose to adopt these sign systems. In terms of the IndieWeb community discussions around web standards historically reflected an argumentative discourse prevelant. The founders themselves cite the " |
- | < | + | |
- | <td colspan=" | + | While recent efforts have been made to reduce " |
- | < | + | |
- | </td> | + | While the majority of those who self identify as IndieWeb use microformats to connect their website they do now use a membership gateway of " |
- | <td colspan=" | + | |
- | <p>Brid.gy is used to syndicate content from personal websites to various social networks. Monocle.p3k.io is used to follow and interact with feeds from other websites</p> | + | Overall microformats demonstrate the power of signs and symbols to sustain a community. In terms of socio-technical system the use of microformats also acted as a barrier to membership. While still in compliance with web standards microformats works on websites the same way as CSS, which controls the way pages look such as colors and fonts. This caused large technical difficulties for CMS platforms. A recent proposal (IndieWeb/ |
- | </ | + | Leadership and Barriers |
- | </ | + | |
- | < | + | Given the already stated barriers of access inherent in the community, the access to leadership still aligns well to Gee's Affinity space model. To attend, what was called the " |
- | <td colspan=" | + | |
- | <p>Plugin for existing software</p> | + | Efforts have been made to increase the number of organizers and to diversify leadership. Recently the decision was to change from ' |
- | </td> | + | |
- | <td colspan=" | + | With so many global events privledge, as in many facets of life, also creates barriers to leadership. Many organizers have professional arrangements with employers or work remotely as digital nomads. While a remote feed is made available hours of household silence maybe impossible in households with children (private citation). |
- | <p>A variety of plugins for adding IndieWeb features to sites built using the popular WordPress content management system.</p> | + | Content Creation |
- | </ | + | |
- | </ | + | Creation is a central feature of IndieWeb. |
- | < | + | |
- | <td colspan=" | + | Building personal websites requires (at least) two types of creation. First, one must design the site itself, choosing a visual style and information structure that fits one's purpose. Second, one must populate the site with content. |
- | <p>Conventions of practice</p> | + | |
- | </td> | + | Most of IndieWeb' |
- | <td colspan=" | + | |
- | <p>Publish on Own Site, Syndicate Elsewhere - A convention for owning one's data while still engaging with various social platforms</p> | + | Although the overall breadth of content on IndieWeb sites parallels that of social media platforms, the scope of any given individual website varies significantly. Determining a unique blend of content-types for one's website eludes to Franklin' |
- | </ | + | |
- | </ | + | Beyond personal websites themselves, IndieWeb' |
- | </ | + | |
- | </ | + | Examples of IndieWeb building blocks |
- | <p>The list above presents a partial view of IndieWeb' | + | |
- | <h2>Agentive Apprenticeship</h2> | + | |
- | <p>There are 785 mentions of "my first" 381 mentions of " | + | |
- | <h2>References</h2> | + | Type of building block |
- | <p>Agre, P. (1997). Computation and human experience. Cambridge ; | + | |
- | <p>Barrett, R. (2017, June). Keynote: Indie Map. Presented at the IndieWeb Summit 2017, Portland, OR. Retrieved | + | |
- | < | + | Example |
- | <div> | + | |
- | < | + | Technical standard |
- | </ | + | |
- | < | + | |
- | < | + | The Webmention standard is used to send ' |
- | <p>There is also a need to indicate that this is a challenge as the network makes it easier for you...and you may not easily be able to connect with your " | + | |
- | </ | + | Web application |
+ | |||
+ | |||
+ | Brid.gy is used to syndicate content from personal websites to various social networks. Monocle.p3k.io is used to follow and interact with feeds from other websites | ||
+ | |||
+ | Plugin for existing software | ||
+ | |||
+ | |||
+ | A variety of plugins for adding IndieWeb features to sites built using the popular WordPress content management system. | ||
+ | |||
+ | Conventions of practice | ||
+ | |||
+ | |||
+ | Publish on Own Site, Syndicate Elsewhere - A convention for owning one's data while still engaging with various social platforms | ||
+ | |||
+ | The list above presents a partial view of IndieWeb' | ||
+ | Agentive Apprenticeship | ||
+ | |||
+ | There are 785 mentions of "my first" 381 mentions of " | ||
+ | References | ||
+ | |||
+ | Agre, P. (1997). Computation and human experience. Cambridge ; | ||
+ | |||
+ | Barrett, R. (2017, June). Keynote: Indie Map. Presented at the IndieWeb Summit 2017, Portland, OR. Retrieved | ||
+ | |||
+ | Çelik, T. (2016, June). State of the IndieWeb. Presented at the IndieWeb Summit, Portland, OR. Retrieved | ||
+ | |||
+ | [a]Thinking about rephrasing this - just marking it for rethinking. rather than " | ||
+ | |||
+ | [b]I like the thinking about the individual...as opposed to the network...or the silos we exist within. | ||
+ | |||
+ | There is also a need to indicate that this is a challenge as the network makes it easier for you...and you may not easily be able to connect with your " |
case_study/indieweb.1606657015.txt.gz · Last modified: 2020/11/29 13:36 by 127.0.0.1