Web Platform Wednesday: text adornment

Why, oh why, would you want to use text without adornment on a webpage? That’s so 1990’s. This week we focus our Web Platform Wednesday work on some more CSS properties that take plain text and make it stand out in a crowd. We’ve selected a little over a dozen CSS properties from the CSS3 Text, the CSS Exclusions Module Level 1, and the CSS Line Layout Module Level 3 specifications, and we’re looking for volunteers to create, edit, and review the reference content for each of them on Webplatform Docs.

Sure, this is just a subset of what you can do with text using CSS, but I’d like to think that these properties enable the tasteful accessorizing of text, adding just the right touch to your work (without going so far as to be tacky, a la the CSS WG’s April fool’s joke from 2012).

And so this is where you come in. You’re unique; you have that certain je ne sais quoi about you. Bring that panache, that élan, and use it to help document the web. And as you can see, a number of the properties are either obsolete or unsupported and require minimal documentation, so this week’s group is fun and easy!

Let one of the coordinators know which CSS properties you are interested in documenting. Make sure you have a user account for Webplatform Docs. And then follow the guidelines on the Web Platform Wednesday page. There are lots of people to help, should you run into any snags. And, voila, you’re documenting the web!

What is Web Platform Wednesday?

There are many contributors doing work throughout Webplatform Docs. Some are working on infrastructure, some on community, some in content, and some lurking in the corners, waiting for the perfect opportunity. Web Platform Wednesday is a way to find a volunteer opportunity for those looking to add some value to the project. In the weekly meetings, we choose areas of priority for the project and then actively solicit help. Right now, we’re working on completing a pass on our CSS property docs. Join in. Bienvenue!

How we’re working, at WebPlatform.org

I thought I’d share some thoughts this week on how we are working towards making web standards documentation rock more here at WebPlatform.org! We knew it would be challenging to deal with this much content, especially as we are mostly volunteers with only a finite amount of time available to work on the project. We’ve already achieved much, working towards our goal of making WebPlatform.org the definitive client-side web technology documentation site, but there is still much more to do. This is why we opened it up to the wider community as an alpha.

The plan has always been to include the public as early as possible. The web does, after all, belong to all of us. To facilitate getting things done, we have a number of communication means at our disposal. We have a number of discussion methods available including IRC and a mailing list. These are mostly used for general communication, such as announcing in-person Doc Sprints, soliciting feedback and discussing current and future work. For focusing on particular tasks, we:

  • Identify specific tasks to work on. To make the work more manageable, we have started to split it into manageable chunks and we work on each item in turn.
  • Discuss these tasks via our regular communication means, and also have more involved discussions at our regular weekly meetings, simultaneously held on teleconference and IRC.
  • Record task priority lists and who is working on each task, at our beta requirements page.
  • Create detailed task plans to outline how the work will be done, with subtasks, and people assigned to complete them.
  • Get on with the tasks!
  • Speed up task progress with intensive bursts of work at Doc Sprint events.

Current priorities

At the moment, the main topics we are focusing on are CSS properties and JavaScript APIs. Our plan is to perfect the topic pages for these two major areas over the next two to three months. This is where you come in! If you are knowledgeable and passionate about these areas, please get in touch with us to find out how best to contribute. If you don’t wish to contribute to either of these focus areas, and wish to work on something else instead, get in touch anyway, as we will be able to find something for you to do.

The next Doc Sprint we have coming up is in Berlin, Germany, this week — we expect to make a lot of progress on our priority tasks there!