-
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
Jetpack Plugins: add settings link #82
Comments
This is related to #447 |
Related #2206 but still not implemented. Jetpack plugins in Calypso don't have a settings like to go directly to wp-admin settings for that plugin. |
Hey @jeherve we're thinking of adding something like this for at least the most popular plugins. Do you know if any effort was made to get this added to core? |
I'm not aware of any work on that, I'm afraid. |
Here's my suggestion for the design. The proposed method in #6267 will pull more than just a settings link. wp-admin: my design: |
I would put the settings link in a secondary button underneath the plugin icon/name/author. I would put any other links with the other links to the left of the ratings chart. |
@MichaelArestad the design you mention is in the OP of this thread. |
@rickybanister I know, but I want the button to be under the icon, too. |
The Jetpack PR for the API is close to being merged. When we start working on this, let's make sure to add a stat for when the settings links are clicked. Ref: #11063 |
This is great, but an interesting point came up today during an in-person discussion about AT with @drw158: Immediately after installing a new plugin, I'd have to imagine the most common thing someone wants to do is configure that plugin (by accessing some sort of settings link). This design is optimized more for accessing that settings link later. We should do a mockup that overlays some kind of success banner that includes a link to configure settings (if we have access to the appropriate link). |
@rickybanister or it could just highlight the settings link somehow, but I see your point. |
That's a good idea, although we don't have much data to work with. We get the link url and the link name (localized), so we could see if the url has something like |
* Adds plugin ‘action links’ buttons to the plugin detail view. Fixes #82 * Add rel attribute for external link.
post: propagate `id` and `slug` when post is added
Add a settings link to each plugin card, using the new Button component.
Before we can expect that link that work, we need to make sure we catch each plugin. That could be tricky as it really depends on when and how the plugin decides to add the url to the plugins filter. Currently there is no standard way of doing this.
It might be easier to open a ticket in Core first, and suggest a new filter/function that would allow plugin devs to define where the canonical settings URL when the plugin includes one.
The text was updated successfully, but these errors were encountered: