-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Labels
scope: docs-infraInvolves the docs-infra product (https://www.notion.so/mui-org/b9f676062eb94747b6768209f7751305).Involves the docs-infra product (https://www.notion.so/mui-org/b9f676062eb94747b6768209f7751305).status: waiting for maintainerThese issues haven't been looked at yet by a maintainer.These issues haven't been looked at yet by a maintainer.type: new featureExpand the scope of the product to solve a new problem.Expand the scope of the product to solve a new problem.
Description
Summary
With #431, we worked on having our own docs in mui/mui-public so we can test docs-infra in this repository while we work on it. To complete the loop, we also need to deploy those docs. In #431 (comment), we discussed how to make this happen, so we created this issue to represent that work.
If we decide to have two Netlify deployments in mui/mui-public, then I believe we have to copy mui/mui-private's configuration. Meaning:
- We can't rely on Netlify to push CI statuses (when multiple sites deploy, the statuses override each other); we have to have Netlify add comments to each PR.
- We have to have some logic to determine when we need to build one of the sites, based on diffs in folders/files (unless the brute force approach of building on every single PR is fast enough).
Examples
No response
Motivation
No response
Search keywords: -
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
scope: docs-infraInvolves the docs-infra product (https://www.notion.so/mui-org/b9f676062eb94747b6768209f7751305).Involves the docs-infra product (https://www.notion.so/mui-org/b9f676062eb94747b6768209f7751305).status: waiting for maintainerThese issues haven't been looked at yet by a maintainer.These issues haven't been looked at yet by a maintainer.type: new featureExpand the scope of the product to solve a new problem.Expand the scope of the product to solve a new problem.