Codeinwp / Codeinwp/otter-blocks
Redoing the CSS Class
Nobody has claimed this yet.
- #1887 by @Soare-Robert-Daniel — closed without merging
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 36
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 30
Description
Description:
The CSS class for the front-end was written for blocks, but as years have passed, WordPress first added Widgets and now FSE, and the class wasn't prepared for it. So to keep up with it, we just kept adding a few more lines of code, and the file has kind of become a mess and can use a redo to make things easier and more modular.
This also includes making clearer methods for Query, FSE & Widgets and adding some caching for FSE methods instead of generating the CSS and fonts on the go if possible.
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 front-end CSS class and its current Query, FSE, and Widgets methods; review how FSE CSS and fonts are generated. Done means the class is modular, those concerns have clearer methods, and FSE work uses caching where possible; check linked PR #1887 for existing context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100