openedx / openedx/frontend-app-authoring
Enforce "main section" layout rules for all course-authoring MFE pages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 218
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 20
Description
There are discrepancies across the pages regarding their main layout. All of the pages use <Layout> from Paragon if the page requires an aside. However, not all of the margins are identical and if a change is made in one it will not apply to all of the layouts.
Proposal:
Create a generic <PageContainer> that uses <Layout> from Paragon and is used across all pages. This will make is easier to make changes across all pages and reduce the amount of replicated code.
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 locating the course-authoring MFE pages that currently use Paragon's and compare their main-section margins. Define the shared scope from those entry points, then verify that all pages use it and their main layout rules remain consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100