Here are some example web literacy skills. They may be too big. They may be too small. They may not be useful at all. They may be missing some of the most important skills out there.
But I hope that they can at least illustrate the types of skills I’m thinking of.
Understanding the web
- What is “offline” vs “online”?
- Crap detection
- “View source”
- HTTPS and why/when you should care
- What is permanent and what can be undone?
- The anatomy of a permalink
- What “uploading” entails. Where does it go?
- Ownership/copying/reuse on the web
- etc.
Making
- Basic HTML tags: links, images, etc.
- Take and upload a picture
- How forms work
- Smash two APIs together
- Changing an existing page
- React on user behaviour (clicks, etc.)
- React on the world outside the page (API calls, time of day etc.)
- etc.
Innovating
- Contributing to an open source project
- Building (small) software from scratch
- Taking existing software apart to understand it
- Traditional web programming courses’ items: debugging, etc.
1) Pass by value vs. pass by reference (i.e., give someone a copy vs. give someone a link)
2) Human readable vs. machine readable (which is connected to “models vs. views”, but isn’t quite the same thing)
(Stolen in part from http://blog.jonudell.net/2011/01/24/seven-ways-to-think-like-the-web/)
Hi Michelle, this is a good start! (and I’m enjoying your musings in this space)
I think an important question here is which of these are *procedural* and which are *conceptual*? The former are likely to be predicated upon competencies and the latter upon literacies, which would allow for a hierarchical badge structure.