Segregate theme config
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with the main Tailwind configuration and trace how the website currently defines and uses its theme. The issue proposes moving the color palette and additional Tailwind settings into separate files, but does not identify files or tests. Done means the main configuration imports those files and the website can still use its theme.
Written by the indexing model from the issue text.
Description
We should not have the configuration for the Website's theme situated on the Tailwind's configuration file.
In my opinion, we should have:
- The color palette on a dedicated file, where we define all the colors that are going to be used throughout the website. As a bonus, we could think of some "standard" way of using these colors so that future developers only need to change some values and everything still works.
- Adittional styling should be on a separate file (that must respect Tailwind's configuration format) that is imported and used on the main config file.
This way, we ensure that any styling that is not permanent can be modified and the website adapts to it.
- Dominant language
- Vue
- Stars
- 12
- Forks
- 1
- Avg merge
- 3d 42m
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from semanadeinformatica/website
-
frontend P0
Difficulty 1/5 Under an hour Newbie friendliness 65/100
semanadeinformatica/website#483 ·
-
gamification P1
Difficulty 4/5 3-5 days Newbie friendliness 25/100
semanadeinformatica/website#479 ·
-
frontend gamification P1
Difficulty 3/5 1-2 days Newbie friendliness 62/100
semanadeinformatica/website#478 ·
-
frontend gamification P2
Difficulty 3/5 1-2 days Newbie friendliness 52/100
semanadeinformatica/website#477 ·
-
backend gamification P1
Difficulty 3/5 1-2 days Newbie friendliness 50/100
semanadeinformatica/website#476 ·
All issues in semanadeinformatica/website
Similar issues
-
area:ui good first issue phase:dev priority:p2 type:spike
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Open-Earth-Foundation/CityCatalyst#3395 ·
Maintainers usually reply within 2 days
-
Bug GUI
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SCIInstitute/SCIRun#2907 ·
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
neutraltone/settee#157 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100