Skip to content

Highlight the structure of the WSG in the introduction #97

@mgifford

Description

@mgifford

I do think that we've been discussing the structure of the WSG and what items should go where. This is important, however, it is also something that an individual team may do differently, given their definition of roles. What is important is that the tasks get done, not which category they fall under in the WSG. These are big buckets:

  • User Experience Design
  • Web Development
  • Hosting, Infrastructure, and Systems
  • Business Strategy and Product Management (or just Product Management)

We should highlight the four areas we have divided up the tasks. If we pull out the Business Strategy, that needs to be explained.

The key point is that these categories are mostly a way we have thought about generic web projects. Other teams may think of them differently, and that's fine. The success criteria are important, not which role or function they are written under.

https://w3c.github.io/sustainableweb-wsg/intro.html#the-web-sustainability-guidelines

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions