Learning material

From Web Education Community Group
Jump to: navigation, search

The overall aim of the Learning material project is to create a comprehensive series of tutorial articles to teach all the W3C technologies, which will constantly be updated so that it remains current and best practice. The main basis of this is currently the web standards curriculum. Below are the activities this project is currently undertaking, or has undertaken.

Current activities

Positioning document for web ed learning material

Migrating HTML material to the Wiki

General section of tips.

First of all, you should find a good HTML to Wiki text converter. http://w-i-k-i.appspot.com/ is really good.

Migrating translations

I also want to get the translations migrated over to this Wiki at some point.

We want to use a separate section for each set of translations, and identify each one via its two (or four, if appropriate) letter language code.

We should work out the best way to do this. Are we able to put translations in separate directories, eg

Or should we just append the language code on to the URLs, eg

Or both?

Thoughts on a postcard please!

Web standards curriculum update

The web standards curriculum originally lived on Opera's http://dev.opera.com site, but Opera decided to move it to the W3C to improve visibility, and find more people to help out with an update. One thing we are currently doing is going through all the original articles and giving them an update to bring them up to date, and adding any new articles that need adding. Chris Mills has been doing this, and recording update made in the discussion page of each article. So if you want to work on this, check first that an update has not already been done. A procedure to follow:

  1. Check the overall plan of what needs to be done on the WSC proposed updates page.
  2. Find an article to update that interests you.
  3. Check that it has not already been updated by looking on the discussion page for the article (see the "discussion" tab at the top left of all Wiki pages).
  4. Do the update. What we want you to do is:
    1. Give it a general update, tidy it up, and make it read better.
    2. Update things that are out of date, for example adding more recent design methodologies, or adding relevant HTML5 and CSS3 features.
    3. Change it from first person to third person, eg, instead of "I did this", change to "we did this" - since the Wiki is mass edited, a single voice is no longer appropriate, even if the vast majority of an article is written by one person.
  5. When you have finished, add a comment to the top of that article's discussion page to say that you have updated it, and what you have done. include the date on which you made the update, and say whether you think it is ready for proof reading/translation.

Articles in progress

Chris Mills is now working on the CSS background images article. He is also considering doing a write up of the new CSS3 text and font stuff, like font-feature-settings, hyphens, etc.

Already updated

But anything else is currently up for grabs. Add a note here saying what you are working on.

Proof reading

Up for grabs:

Mark DuBois has proof read:


Update web design concepts section

The Web design concepts section is currently a bit out of date, and needs an overhaul.

Here's the newest draft of the outline.

  1. Website's main goal : why do i want to build this website ?
    • What is the marketing/communication issue I want to solve?
    • Would a website solve this issue? How?
  2. Targets : who's my website for ?
    • Scoping and user research
  3. Defining my information/content architecture.
    • Defining the content
      • What I want to share
      • What visitors would search for
      • How much ? (ideas, signs)
    • Finalizing the content
    • Building the structure
    • Finalizing the data architecture
  4. Website's anatomy
    • The skeleton
      • Home
      • Header
      • Navigation
      • Content / Context
      • Footer
      • Legals informations
    • Understanding the UX, SEO and Accessibility
    • UI Core concepts
    • Medias (mobile, screen...)
      • Constraints specific to devices
    • The grid
  5. Let's build a prototype
    • Wireframing the website
    • Let's test the usability of this prototype.
  6. Graphic design
    • The grid : act II ;
    • Graphic design and accessibillity (contrast and size) ;
    • Colours sheme and meaning ;
    • Illustrating a content ;
    • Typography on web.


Of course, feel free to expand this and add ideas. I am intending this section to be a high level overview right now. Future courses could go into things like UX and IA in much more detail.

Web design concepts update contributors

  • Lewis Nyman
  • Sébastien Desbenoit

Update accessibility section

The accessibility section also needs a lot of updating, in Chris's opinion. The two articles that are there are very well written, but I think the subject could do with a more granular and structured treatment, along the lines of:

  1. WRITING A PLAN FOR A11Y TESTING, INCLUDING USE OF REAL USER TESTING, CONFORMANCE CRITERIA, AUTOMATED TOOLS, AND GOOD OLD COMMON SENSE
    Some of this is covered in the resources listed under Evaluating Websites for Accessibility, Implementation Plan for Web Accessibility, Improving the Accessibility of Your Website
  2. THE LEGAL SIDE OF THINGS, EXPLAINED IN DETAIL
    W3C generally would not publish legal advice or analysis. Some carefully vetted legal information is linked under Policy Resources
  3. DECIPHERING WCAG, AND OTHER CONFORMANCE CRITERIA SUCH AS SECTION 508
    This should be covered by WCAG Overview, The WCAG 2.0 Documents, and Using WCAG 2. Specific information on Section 508 is outside the scope of what W3C would publish.
  4. ACCESSIBILITY TOOLS, WHAT TO USE AND WHAT TO AVOID. HOW FAR WILL THESE GET YOU?
    This should be covered in Selecting Web Accessibility Evaluation Tools
  5. REAL A11Y TESTING WITH REAL PEOPLE, HOW TO PUT TOGETHER FOCUS GROUPS, WHAT TO LOOK FOR HERE
    This should be covered in Involving Users in Web Projects for Better, Easier Accessibility
  6. COMMON SENSE - SOLUTIONS FOR COMMON ACCESSIBILITY ISSUES - A ROADMAP FOR FIXING ISSUES. START WITH SEMANTIC HTML, THEN GO TO VIDEO AND AUDIO CONTENT, JAVASCRIPT, AJAX, ALTERNATIVES.
    Through the WAI-ACT project, we plan to address this through "application notes"

Suggestions for improvements to the existing WAI material is welcome to wai-eo-editors@w3.org !

The accessibility two articles are also out-of-date and contain some material that would not be appropriate published by W3C. EOWG is updating Accessibility Basics and considering what to do about the accessibility testing information, in light of the existing Testing/Evaluation info, which is being updated.

The education and outreach group have some material than can be contributed to this, I'm sure! Of course, feel free to expand this and add ideas.

Accessibility update contributors

  • Shawn Henry and the EOWG

Update CSS sections

The CSS section is fairly complete, but could do with some updates to bring it up to date and add coverage of some of the features not already covered, eg CSS3 stuff. See http://www.w3.org/community/webed/wiki/WSC_proposed_updates#CSS for more info on what needs to be updated, according to Chris. Feel free to add some more ideas.

CSS update contributors

  • Chris Mills: cmills@opera.com
  • Lewis Nyman

Write plan for JavaScript material

At the moment, the JavaScript core skills section has some good material in it, but it is far from complete. The original WSC JavaScript articles were created this way because there was no way I had time to create a complete JavaScript course, so I chose to just cover enough to give basic familiarity with some of the core concepts. But I think the new W3C learning material needs to be more complete.

There are a few ideas recorded at:

But I really need someone to pick this up and write out a decent structure for our JavaScript material, to give us an idea of what we need to cover. I am haoping that we'll be able to adopt some material from somewhere else (for example Mozilla MDN), and not have to write the whole lot out ourselves!

JavaScript material planners

  • Richard D Worth

Write the mobile web course

At the moment, the mobile web development section is very sparse - only one article! Ideally we want to create a much bigger structured course - some notes have been written at

http://www.w3.org/community/webed/wiki/WSC_proposed_updates#Adaptive_design_and_development_for_Mobile_and_other_alternative_browsing_devices

But feel free to update and change this as much as you like.

Bear in mind that quite a lot of "mobile web" content would have already been covered in other places, and we don't need to cover it twice. There is no reason why you can't point to other materials in the learning material for some subjects. For example, there should already be articles on media queries and viewport inside the CSS section.

Articles in progress

Wai Seto is now working on Media Queries and Browser Detection (Feature, UA)

Mobile web course contributors

  • Wai Seto
  • Lewis Nyman
  • Mark DuBois
  • Siddharth Srivastava

Write SVG course

We need volunteers to write SVG material!

There is currently no SVG content in the W3C learning material, but this really needs to change, as it is such an important standard to cover. There are ideas for what material should be written at

http://www.w3.org/community/webed/wiki/WSC_proposed_updates#SVG

Feel free to add more ideas.

Contributors to SVG course

  • Jeremie Patonnier
  • Shwetank Dixit

Write guide to educational theories and terms

  • Activity lead: Panagiotis G. Peteinatos
  • Activity contributor: Chris Mills

The field of educational science is full of different theories and terms (eg Connectivism, Behaviourism), and the whole area is pretty chaotic and hard to digest, especially by non-educational scientists. We are aiming to produce an easy to digest guide to these educational theories, to help web professionals and educators understand these theories, and improve their teaching/learning practices.

Past activities

Migrating material from the general W3C Wiki to the WebEd CG Wiki

November 17th 2011

Before doing any more article updates, we need to move all the web standards curriculum material currently on the W3C Wiki (http://www.w3.org/wiki/Web_Standards_Curriculum) to the main page of the Web Education community group Wiki (http://www.w3.org/community/webed/wiki/Main_Page). The latter is where we will do all of the collaborative work on the W3C learning material.

I have done much of the migration tasks already, but I'd like to ask for volunteers to help me out where these!

To Migrate an article:

  • Open up the article in both the old Wiki and new Wiki, eg http://www.w3.org/wiki/CSS_basics and the CSS basics link on http://www.w3.org/community/webed/wiki/Main_Page.
  • Make sure you are logged in to both locations.
  • Click edit on the old Wiki, and the new Wiki.
  • Copy all the source text from the old to the new, and click Save.
  • Go to the Old Wiki page, and save all the images somewhere on your local drive
  • Go through the new Wiki page, and for each image link
    • Click on it
    • Select the relevant image using the file dialog
    • Click the back button until you get back to the main page, and refresh the page
  • You also need to copy the discussion notes for the article over - do the same thing as you did for the main article, but for the contents of the "Discussion" tabs.
  • Once an article is migrated, mark it with "(MOVED)" like I've done in the old Wiki!

Let me know if you need any help!

Migrating HTML and CSS references

I also want to migrate the awesome HTML and CSS references to this Wiki, see

Can someone pick up the reigns on this subtask?