At this moment we have two web properties:
We should decide if we should have two properties that are geared at two different audiences (designers for the style guide and engineers for the demo site) or if we should unify them under one domain as shared communication tool.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T306115 Communication plan about Design System (single) sources of truth | |||
| Invalid | None | T297315 [SPIKE] Consider merging the Design Style Guide and Codex components demo site |
I have an inkling that we can now close this task, @bmartinezcalvo and @RHo. Either that, or we could use it as an epic to group the subtasks that are pending (e.g. migrating missing content from DSG to Codex), beyond the MVP.
As commented yesterday during our DS design sync, I agree with merging the DSG with the new Codex Style guide, but we need to move first the Apps info to some place to avoid missing this information (since it's the only section that is not reflected now in the Codex Style guide).
Let's not talk about that detail on this task as this warrants discussion and planning for the actual planning task. Agree we can close it from r now as tasks to migrate + redirect will be carried out in separate work.