Conversation
Whether you should or should not I won't say :) I don't think it'd be an overkill, in component frameworks it's common to have small components. Number of repetition is not the only criteria ~ also readability & being able to locate easily where to change things. Even if something is used just once ~ if it looks like a lego piece to human mind, then it'd most likely qualify ;) |
|
Actually through another PR, I recalled we already have the banner component in Studio & it follows our general banner specs that will apply here too (I confirmed with Tomiwa recently on another opportunity that these spec apply). Would you please use
|
Summary
Adds a banner in the style of the community library "Call To Action" to advertise search recs.
References
Just discussed with Richard and Laura on slack as part of our efforts to promote the feature. no specs.
Reviewer guidance
Code review -- i did not abstract this into a component although I could do so (since we technically now have 3 places of this little component). should I, or is that overkill?
AI usage
I did the initial implementation just duplicating the implementation Alex did for the banner with some manual css adjustments. I then had claude copy to the second spot and add in the local storage. reviewed and manually QA'd all during iterative work and also after.