Audience and scope

The glossary is an open, collaborative, and rolling project for people working with content in UX fields. "Rolling" meaning there is no end point to refining the definitions. The goal is to assemble and normalize in writing a core set of common, practical terms that may benefit collaborators across borders and UX professions. If nothing else, it's a fun excuse to interact with others and learn the ropes of a versioning control system like GitHub.

Audience

We'll distinguish between target audience and glossary collaborators.

Target glossary users

Target users of this glossary are:

1. People working across different UX fields who collaborate on content in various ways.
2. People new to a given content/UX field (e.g. students and industry cross-overs).
3. People in different roles who may need a reference to the vocabulary we use (managers, recruiters, journalists...).

Glossary collaborators

We assume people interested in collaborating on the glossary will work in content-as-service fields across the UX domain, but may also be new to GitHub. If you are new to GitHub, great. GitHub is as useful for content collaboration as it is for code collaboration. We want to help you see that with this opportunity to learn GitHub basics in a friendly and supportive way, while you help create something useful for target audiences in return. See Collaboration roles and hierarchy for more about roles, rights, and attribution.

Experienced GitHub users are welcome too, of course, and feel free to use git on the command-line, if you prefer.

Scope

The scope of the glossary is an undefined number of terms suitable for describing any number of contemporary and forward-looking scenarios of content handling, collaboration, and use. That does not mean creating a dictionary of every conceivable word. Nor should the glossary be biased to a given discipline, like technical communication or content marketing.

Collaborators should work out any further questions regarding scope as part of glossary development and Using issues and Using issue labels.