Skip to content
This repository has been archived by the owner on Feb 12, 2020. It is now read-only.

Moving the location of the plugin settings menu #49

Open
cferdinandi opened this issue May 14, 2015 · 4 comments
Open

Moving the location of the plugin settings menu #49

cferdinandi opened this issue May 14, 2015 · 4 comments

Comments

@cferdinandi
Copy link
Contributor

I'd suggest we elevate the Mashery Plugin settings from a sub-section of the Settings area to it's own dedicated navigation element in the left-hand nav using the add_menu_page() API (docs). This would give it more visibility and make it easier to find.

screen shot 2015-05-14 at 12 25 08 pm

We can even create a custom Mashery icon to be displayed with it.

Thoughts?

@jpollock
Copy link

This is inconsistent with plugins, though. I don't think this makes sense, respective of plugin configuration.

@cferdinandi
Copy link
Contributor Author

Many plugins do this, which is why there's an API for it. Notable examples include WordPress/Automattic's own Jetpack plugin, and ZenCache.

In particular, if we start to include more options and settings for users and need more than one page to accomplish it, it's a more organized way to handle things. Plugins can and do place there settings menu in various places depending on what they do. Sometimes it's under Settings, sometimes Tools, other times Appearance, and sometimes as it's own menu page. There is no standard place for plugin settings.

From my perspective, we're bolting some serious functionality into WordPress, which makes this worthy of it's own menu.

@jpollock
Copy link

Looking at Jetpack in my local wordpress env and thinking about what we're doing, I think we're more in the camp of putting something into the Settings menu. This all depends on scope but currently the scope does not, in my mind, warrant a top tier menu as opposed to a sub menu of Settings. Just my opinion.

@cferdinandi
Copy link
Contributor Author

Current status: I agree.

Once we start getting into doing things like this, I think it gets more complicated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants