# Purpose of admin-nav on admin plugins page

**URL:** https://meta.discourse.org/t/purpose-of-admin-nav-on-admin-plugins-page/31714
**Category:** UX
**Created:** [8월 3, 2015, 7:16오후 UTC](https://meta.discourse.org/t/purpose-of-admin-nav-on-admin-plugins-page/31714 "2015-08-03T19:16:20Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [8월 3, 2015, 7:16오후 UTC](https://meta.discourse.org/t/purpose-of-admin-nav-on-admin-plugins-page/31714/1 "2015-08-03T19:16:20Z")

</div>

Is there a purpose to having the stacked admin navigation on the admin\>plugins page? Looking at the code in `plugins.hbs` it seems that all it can do is display one item, and that item is for the page the the user is currently on.

```js
<div class="admin-nav pull-left">
  <ul class="nav nav-stacked">
    {{nav-item route='adminPlugins.index' label="admin.plugins.title"}}

    {{#each route in adminRoutes}}
      {{nav-item route=route.full_location label=route.label}}
    {{/each}}
  </ul>
</div>

```

 ![](https://global.discourse-cdn.com/meta/original/3X/8/7/8790acccacf3a05cda0188c55dd85862b42960d3.png)

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [8월 3, 2015, 11:04오후 UTC](https://meta.discourse.org/t/purpose-of-admin-nav-on-admin-plugins-page/31714/2 "2015-08-03T23:04:01Z")

</div>

If you have plugins that register a page there, such as discourse-data-explorer or discourse-akismet, they will be available in the left tab stack.

(Hmm, idea: have discourse\_docker iframe /admin/upgrade on that page)