Page MenuHomePhabricator

Governance & Guidelines: Design System Code Repo
Closed, ResolvedPublic

Description

Background/Goal

There is a clear place that Design System code exists so it is easy to locate and use code related to the Design System.

User stories
  • As a front-end developer, I can easily locate the Design System code.
Considerations
  • There are multiple potential tools to use, may need to discuss current state vs target future state (ex: GitLab)
  • Many of our users will use the version of Codex within MediaWiki. Information on how to use Codex within MediaWiki is captured on https://www.mediawiki.org/wiki/Codex, but we should at least link to this from the Codex docs site to send people looking for that information in the right direction.
Requirements
  • There is a single source of truth for Design Systems code (ex: repo on GitLab)
  • The Design System Repo MUST include the following:
    • READ ME - intro on contents and link outs to other relevant documents (ex: Design Systems wiki)
  • There is a single source of truth for each user story (aka artifact)
  • All source of truth documents/artifacts are available via Design System Portal/Wiki
Acceptance criteria
  • There is a single source of truth for each user story (aka document)
  • All documentation should link back to a central Design System Portal/Wiki
  • Code should be:
    • easy to read (limited jargon)
    • clear to follow (has comments)
  • Access to artifacts should NOT be restricted for viewing by target users (aka remove or update permissions as necessary)
Test scenarios

[N/A]

Open questions

[N/A]

Event Timeline

Change 832354 had a related patch set uploaded (by Anne Tomasevich; author: Anne Tomasevich):

[design/codex@main] docs: Call out icons package in README

https://gerrit.wikimedia.org/r/832354

Change 832354 merged by jenkins-bot:

[design/codex@main] docs: Call out icons package in README

https://gerrit.wikimedia.org/r/832354

AnneT changed the task status from Open to In Progress.Sep 14 2022, 9:42 PM
AnneT subscribed.

I personally think this task can be considered complete. The two main sources of information here are the Codex docs site and the Codex page on mediawiki.org. Both of these sources link to each other, making it clear that the docs site is for Codex in general and the mediawiki.org page is for Codex use within MediaWiki.

The docs site names the gerrit repository as the official repo in the contributing docs, but also links to the GitHub mirror which is easier to read. The distinction between the two is explained on the landing page under "resources". In the future when we move to GitLab, we won't have this duplication anymore.

Both the docs site landing page and the README give basic critical information and link to further information.

Agree with @AnneT.

We've got several entry points for devs:

  • doc.wikimedia.org
  • Gerrit
  • CodeSearch
  • mediawiki.org
  • GitHub

On all of above Codex is already findable. Is it findable under every possible term? Not yet, but we've been building out to spread the word across documentation.
Don't think there are any other big steps needed right now. The only thing that could lift prominence is putting Codex aside of OOUI into CodeSearch. Github's start page for everything Wikimedia is auto-generated by favorites. For me that point is sufficiently achieved at the moment.

Change 849191 had a related patch set uploaded (by VolkerE; author: VolkerE):

[mediawiki/core@master] Update Codex from v0.2.1 to v0.2.2

https://gerrit.wikimedia.org/r/849191

Change 849191 merged by jenkins-bot:

[mediawiki/core@master] Update Codex from v0.2.1 to v0.2.2

https://gerrit.wikimedia.org/r/849191