Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
93 lines (66 sloc) 4.93 KB


Prototypes for the “dynamic pages” project

⚠️ This project is discontinued, and not being actively maintained.
For alternatives, see related projects on GitHub.


“Root” view

With no arguments (or with wrong arguments): /

Lists of entities that are “listable”

  1. All functions: /?f=all
  2. All groups: /?g=all
  3. All specs: /?s=all
  4. All affiliations: /?a=all

Examples of particular Entities

  1. A function: /?f=109
  2. A group: /?g=68239
  3. A charter: /?g=46300&c=155
  4. A spec: /?s=dwbp
  5. A version: /?s=2dcontext&v=20110525
  6. A user: /?u=ggdj8tciu9kwwc4o4ww888ggkwok0c8
  7. A service: /?x=2279
  8. A participation: /?p=1503
  9. An affiliation: /?a=52794


How to test locally

  1. Clone this repository and check out the desired branch.
  2. Edit this couple of lines at the beginning of behaviour.js to use your own API key (and, optionally, to enable debugging, so that useful messages are printed on the JavaScript console of your browser).
  3. Serve the page (index.html and related resources) locally, setting up your web server appropriately.
  4. Use Unitas by visiting http://localhost/unitas/ (assuming that's where it's being served). As all items are inter-linked, you can start anywhere and pretty much navigate your way to any other valid page in the system. But the root page / is a useful entry point.

About the API key

⚠️ the W3C API key embedded in this project will work from the domain only, as it is for demonstration purposes on GitHub pages. Make sure you replace it with your own API to use it with localhost:// or other origins.


Resources are loaded this way:

This cascading is far from optimal, of course. It is useful during development and for debugging, though.

In production, resources will be concatenated and loaded in parallel, and minified/compressed versions of CSS/JS libraries will be used instead.

Related projects on GitHub

  • w3c-api: the W3C API.
    • node-w3capi: a JS client for the W3C API.
    • apiary: a simple JS library to use the W3C API in a declarative way.
  • About [re]design:
    • mailing-list-archives: modernising W3C's mailing list archives.
    • wbs-design: pretiffy the WBS UI (polls and surveys).
    • tr-design: new style sheets used by W3C technical reports in 2016.
    • design: templates, mockups, proposals and design-related material.
  • midgard: dashboard for the dwellers of our world.

Other resources


Copyright © 2016–2018 World Wide Web Consortium.

This project is licensed under the terms of the MIT license.