Automattic / Automattic/Picard
Identify components to componentize
- Dominant language
- CSS
- Stars
- 622
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Let's figure out some components! CC @kwight
Initial ideas that come to mind that follow the standardish class structure pretty nicely:
```
|- masthead
|-- site-title
|- navigation
|- hentry // for post and pages?
|--- entry-title
|--- entry-meta // and maybe components for the stuff that lives here
|--- entry-content
|- comment-box
|--- comment-form
|--- comments
|----- comment
|------- author ingo/meta stuff?
|------- comment-content
|------- comment-actions // reply/favorite/etc
|- widget
```
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue lists possible theme components but names no files, tests, or entry points. Start by locating the existing React theme structure and compare it with the proposed masthead, navigation, hentry, comment-box, and widget boundaries; done requires an agreed componentization plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, react
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100