mozilla / webliteracymap

A collaborative effort, led by Mozilla, to define the skills and competencies required to read, write and participate on the web.

Web Literacy Map (v1.5)

Mozilla defines web literacy as the skills and competencies needed for reading, writing and participating on the open web. To chart these skills and competencies, Mozilla work alongside a community of stakeholders to create and sustain the Web Literacy Map. Read more about why Mozilla cares about web literacy in this Webmaker Whitepaper.

=====================

The Web Literacy Map is comprised of three strands:

• Exploring - reading the web
• Building - writing the web
• Connecting - participating on the web

If you're interested in using the Web Literacy Map with your app, check out this GitHub repo.

=====================

Contact: Doug Belshaw, Web Literacy Lead, Mozilla Foundation (@dajbelshaw / [email protected])

webliteracymap's Issues

Define skills under 'Security' competency for v1.5

Security
Keeping systems, identities, and content safe

• Recommending how to avoid online scams and 'phishing'
• Managing and maintaining account security
• Encrypting data and communications using software and add-ons
• Changing the default behavior of websites, add-ons and extensions to make web browsing more secure

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Privacy' competency for v1.5

Privacy
Examining the consequences of sharing data online

• Debating privacy as a value and right in a networked world
• Explaining ways in which unsolicited third parties can track users across the web
• Controlling (meta)data shared with online services
• Identifying rights retained and removed through user agreements
• Managing and shaping online identities

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Coding / Scripting' competency for v1.5

Coding / Scripting
Creating interactive experiences on the web

• Reading and explaining the structure of code
• Identifying and applying common coding patterns and concepts
• Adding comments to code for clarification and attribution
• Applying a script framework
• Querying a web service using an API

---

Proposed:

• Reading and explaining the structure of code

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Credibility' competency for v1.5

Credibility
Critically evaluating information found on the web

• Comparing and contrasting information from a number of sources.
• Making judgments based on technical and design characteristics.
• Discriminating between 'original' and derivative web content.
• Identifying and investigating the author or publisher of web resources.
• Evaluating how purpose and perspectives shape web resources.

---

See spreadsheet at http://goo.gl/R1tjj3

Combine 'Web Mechanics' and 'Infrastructure' competencies?

Lets face it, the Infrastructure competency included in v1.1 of the Web Literacy Map doesn't get a lot of love. There's also significant overlap between it and Web Mechanics.

So, perhaps we should:

• Create a new version of the Web Mechanics competency including skills from Infrastructure
• Separate out Design and Accessibility in the Building strand

Would love to hear people's thoughts on this!

Define skills under 'Web Mechanics' competency for v1.5

Web Mechanics
Understanding the web ecosystem and Internet stack

• Using and understanding the differences between URLs, IP addresses and search terms
• Identifying where data is in the network of devices that makes up the Internet
• Exporting, moving, and backing up data from web services
• Explaining the role algorithms play in creating and managing content on the web
• Creating or modifying an algorithm to serve content from around the web

---

See spreadsheet at http://goo.gl/R1tjj3

Iterate on Web Literacy pathways work

There's lots of interest in @LauraHilliger's Web Literacy pathways prototype (spreadsheet it builds off: http://goo.gl/KQBZUQ)

We should iterate on this and perhaps arrange a separate community call to discuss approaches. There's particular interest in 'skill maps' and non-linear pathways. This may tie in to the way we visually represent the Web Literacy Map for v1.5 (Issue #7)

Related links (from 15th January 2015 community call):

• Lucas Blair | Tell Us Your Story
• Final Fantasy Tactics Advance Jobs
• Path of Exile skill tree

Define skills under 'Collaborating' competency for v1.5

Collaborating
Creating web resources with others

• Choosing a Web tool to use for a particular contribution/ collaboration
• Co-creating Web resources
• Configuring notifications to keep up-to-date with community spaces and interactions
• Working towards a shared goal using synchronous and asynchronous tools
• Developing and communicating a set of shared expectations and outcomes

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Designing for the web' competency for v1.5

Designing for the web
Enhancing visual aesthetics and user experiences

• Using CSS properties to change the style and layout of a Web page
• Demonstrating the difference between inline, embedded and external CSS
• Improving user experiences through feedback and iteration
• Creating device-agnostic web resources

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Composing for the web' competency for v1.5

Composing for the web
Creating and curating content for the web

• Inserting hyperlinks into a web page.
• Identifying and using HTML tags.
• Embedding multimedia content into a web page.
• Creating web resources in ways appropriate to the medium/genre .
• Setting up and controlling a space to publish on the Web.

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Community Participation' competency for v1.5

Community Participation
Getting involved in web communities and understanding their practices

• Engaging in web communities at varying levels of activity
• Respecting community norms when expressing opinions in web discussions
• Making sense of different terminology used within online communities
• Participating in both synchronous and asynchronous discussions

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Search' competency for v1.5

Search
Locating information, people and resources via the web

• Developing questions to aid a search
• Using and revising keywords to make web searches more efficient
• Evaluating search results to determine if the information is relevant
• Finding real-time or time-sensitive information using a range of search techniques
• Discovering information and resources by asking people within social networks

---

See spreadsheet at http://goo.gl/R1tjj3

Decide whether to order skills within each competency by difficulty

We've bumped up against this issue a few times. Lots of people seem to assume that the skills are ordered by difficulty. In fact, many seem to think that the competencies within each strand go from easiest to most difficult.

Whether or not we explicitly communicate the fact, we have a decision to make as to whether we make an attempt to order the skills within each competency by difficulty. What do you think?

Suggestions for string changes

"Exporting and backing up your data from web services"
Should "from" not be "with" or "using" or something ?
I found it in weblitstandard ressource on Transifex.

Separate out 'Design/Accessibility' into two discrete competencies

As mentioned in Issue #10 - would help re-balance after combining Web Mechanics and Infrastructure

Define skills under 'Navigation' competency for v1.5

Navigation
Using software tools to browse the web

• Accessing the web using the common features of a browser
• Using hyperlinks to access a range of resources on the web
• Reading, evaluating, and manipulating URLs
• Recognizing the common visual cues in web services
• Exploring browser add-ons and extensions to provide additional functionality

---

See spreadsheet at http://goo.gl/R1tjj3

Decide how to visually represent Web Literacy Map v1.5

Discussion happening on 22nd January 2015 community call: https://teach.etherpad.mozilla.org/weblitmap-22jan15

Define skills under 'Remixing' competency for v1.5

Remixing
Modifying existing web resources to create something new

• Identifying remixable content
• Combining multimedia resources to create something new on the web
• Shifting context and meaning by creating derivative content
• Citing and referencing original content

---

See spreadsheet at http://goo.gl/R1tjj3

Review 'localization' strategy for Web Literacy Map v1.5

As @alvarmaciel raised in the 15th January 2015 community call, we should review our strategy for localizing the Web Literacy Map.

Sometimes decisions have to be made to substitute words and these should be logged (in English) somewhere.

/ cc @hannahkane

Create skills underpinning re-scoped 'Web Mechanics' competency

We decided on the 29th January community call to merge Infrastructure and Web Mechanics. This has been reflected in the repo (#10). Now we need to come up with the skills for this new, re-scoped Web Mechanics competency.

For reference, v1.1:

• Infrastructure
• Web Mechanics

Define all skills for Web Literacy Map v1.5

Note: this is a meta-issue

---

Below is the list of competencies for Web Literacy Map v1.5. We still need to define the skills underpinning these. Clicking on a competency takes you to the relevant issue. Once we're happy that we've defined all of the skills under a competency, it should be ticked-off here!

EXPLORING

• Navigation
• Web Mechanics
• Search
• Credibility
• Security

BUILDING

• Composing for the web
• Remixing
• Designing for the web
• Coding / Scripting
• Accessibility

CONNECTING

• Sharing
• Collaborating
• Community Participation
• Privacy
• Open Practices

Create glossary for Web Literacy Map v1.5

Let's create a glossary of terms: https://github.com/mozilla/webliteracymap/wiki/Glossary

Define skills under 'Sharing' competency for v1.5

Sharing
Providing access to web resources

• Creating and using a system to distribute web resources to others.
• Contributing and finding content for the benefit of others.
• Creating, curating, and circulating web resources to elicit peer feedback.
• Understanding the needs of audiences in order to make relevant contributions to a community.
• Identifying when it is safe to contribute content in a variety of situations on the web.

---

See spreadsheet at http://goo.gl/R1tjj3

Include 'levels' (e.g. Beginner/Intermediate) in Web Literacy Map v1.5

This was the topic of the discussion in the first community call of 2015: https://teach.etherpad.mozilla.org/weblitmap-15jan15

Build up Privacy pathway badges in P2PU

As detailed in the WG deliverable, we should/need to build up the badges for Privacy and make them available as a proof of concept. Then, we can move on to develop pathways for the remaining competencies.

Deliverable - http://bit.ly/BAWGprivacy

Blog post on the topic - http://bit.ly/1LQfq1K

Review all of the skills for v1.5 of the Web Literacy Map

This is our focus for the February 12th community call: https://teach.etherpad.mozilla.org/weblitmap-12feb15

Here's the epic spreadsheet for comments, etc. http://goo.gl/R1tjj3

Create skills underpinning 'Designing for the Web' competency

We decided on the 29th January community call to separate out 'Design & Accessibility' into two discrete competencies.This has been reflected in the repo (#13). Now we need to come up with the skills for Designing for the Web.

For reference, v1.1:

• Design & Accessibility

Explore skill-level badges

Suggestion from community call 22 January 2015. Could base this on @LauraHilliger's Web Literacy Pathways prototype?

Build out Wikipedia page

I've create a Wikipedia 'stub' for Web Literacy: https://en.wikipedia.org/wiki/Web_literacy

Please help me build it out!

Create skills underpinning 'Accessibility' competency

We decided on the 29th January community call to separate out 'Design & Accessibility' into two discrete competencies.This has been reflected in the repo (#13). Now we need to come up with the skills for Accessibility.

For reference, v1.1:

• Design & Accessibility

Define skills under 'Open Practices' competency for v1.5

Open Practices
Helping to keep the web democratic and universally accessible

• Distinguishing between open and closed licensing
• Making web resources available under an open license
• Contributing to an Open Source project
• Advocating for an open web

---

See spreadsheet at http://goo.gl/R1tjj3

Define skills under 'Accessibility' competency for v1.5

Accessibility
Communicating in a universally-recognisable way

• Using empathy and awareness to inform the design of web content that is accessible to all users
• Designing for different cultures which may have different interpretations of design elements
• Comparing and exploring how different interfaces impact diverse users
• Improving the accessibility of a web page through the design of its color scheme, structure/hierarchy and markup
• Comparing and contrasting how different interfaces impact diverse web users

---

See spreadsheet at http://goo.gl/R1tjj3