-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Components: Consolidate PostSelector styles for standalone usage #3193
Conversation
<a href="/devdocs/app-components/post-selector">Post Selector</a> | ||
</h2> | ||
<div style={ { width: 300 } }> | ||
<PostSelector |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the simplicity of this. Should we clarify which siteId that is from? Should we use your primary site instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use your primary site instead?
Yeah, I like this idea. Updated the example in the rebased 70ef26e2143ccaa5147694cc629c5d6f5df932f4.
6d853aa
to
70ef26e
Compare
70ef26e
to
34e340b
Compare
Tests out well, and I like the change to the search box as well. LGTM. |
…date-styles Components: Consolidate PostSelector styles for standalone usage
Prerequisite for #303
This pull request seeks to migrate many of the styles applied to the
<PostSelector />
component in the context of the page editor sidebar to more generalized usage. It also adds the component to the DevDocs App Components page as an example app component.Implementation notes:
These revisions also fix an issue where post titles shown in the selector would appear as encoded, e.g.
Ribs & Chicken
instead ofRibs & Chicken
.Design notes:
These revisions also change the search field to be fixed to the top of the non-compact post selector. This is arguably a better user experience, since the search should always be available to the user regardless of search position.
Testing instructions:
Verify that the existing
<PostSelector />
used in the Calypso page editor remains unaffected, aside from the single design note described above.Also verify that the DevDocs App Components page includes a functioning example component that displays well as a standalone component.