Ensure docs site styles use the same build config as MFEs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
from https://openedx.atlassian.net/wiki/spaces/BPL/pages/4912316417/2025-04-02+Meeting+notes
[Brian] Open question, thoughts on how to get the styles for both the Paragon docs site and MFEs using the same build configs to avoid discrepancies?
[Adam] Can we pull frontend-build configs in in some way when deploying the docs site?
[Brian] Maybe break config into parts that can be used by both webpack vs gatsby configs?
Example issue that this would resolve: https://github.com/openedx/paragon/issues/3514
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Paragon docs site and MFE build configuration, including the frontend-build configs and the webpack versus Gatsby configurations mentioned in the issue. Review issue #3514 for the discrepancy this work should address. Done means the docs site and MFEs use compatible shared build configuration without the reported style differences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, documentation, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100