The Problem

The new design system, Vocabulary, has been implemented to varying degrees across several Creative Commons web entities, versioning and features do not have full parity and each implementation merits a further investigation, course correction, expansion, and cleanup.

Expected Outcome

Ancillary CC websites implement the current versions and features of the latest Vocabulary codebase in a consistent and stable manner. Necessary new features are identified, built, and implemented upstream into Vocabulary itself where relevant, localized features are implemented into the codebase of each project where necessary.

Contributor Tasks

Identify and catalog features present on current sites, but missing within Vocabulary. Document migration paths between conflicting or missing UX patterns. Rewrite and/or refactor the codebase of each ancillary site, maintaining its original function, while implementing the Vocabulary design system; migrating implementations from NPM dependency chains to more simplistic static code, where needed; building out new features as necessary locally or within the Vocabulary codebase itself. Using simple, standards-compliant, and accessible HTML, CSS, and minimal JavaScript.

Application Tips

• Engage with the ancillary sites and Vocabulary repositories (issues, pull requests)
• Be helpful and welcoming (e.g. answer other contributors’ questions on Slack)
• Applicant Guide

Resources

• Vocabulary Docs
• Vocabulary Repository
• search.creativecommons.org
• Search Portal Repository
• resources.creativecommons.org
• Resources Archive Repository
• opensource.creativecommons.org
• Open Source Repository
• legaldb.creativecommons.org
• LegalDB Repository
• MDN Web Docs: Semantics
• MDN Web Docs: HTML
• MDN Web Docs: JavaScript
• Django Docs
• Lektor Docs