Hi,
I am suggesting a new foreman site map (top-menu), see attached screen-shot.
Why?
Because we are planning to add Katello as a content and entitlement engine,
and we need to make room for the additional content.
Better organize the menu items for easy access. The 'More' menu grue over the years and got too big.
Fit the plugin architecture better by creating a place to add additional menu items.
What changed:
Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
Host, Discovered host and Facts are grouped under Hosts
Configure and Provision sub-menus moved from More to the top-bar
More is now called Administer and keeps the menu items Locations, Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks, Settings and About.
Would you suggest that katello plug into these?
– bk
···
On 10/21/2013 09:42 AM, Amos Benari wrote:
> Hi,
> I am suggesting a new foreman site map (top-menu), see attached screen-shot.
>
> Why?
> 1. Because we are planning to add Katello as a content and entitlement engine,
> and we need to make room for the additional content.
> 2. Better organize the menu items for easy access. The 'More' menu grue over the years and got too big.
> 3. Fit the plugin architecture better by creating a place to add additional menu items.
>
> What changed:
> Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
> Host, Discovered host and Facts are grouped under Hosts
> Configure and Provision sub-menus moved from More to the top-bar
> More is now called Administer and keeps the menu items Locations, Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks, Settings and About.
>
> Thanks,
> Amos.
>
>
I really like this, actually. My only suggestion would be to use nouns, not
verbs (so Monitoring, Hosts, Configuration, Provisioning, Administration).
That feels more natural to me.
+1 overall though
···
On 21 October 2013 14:42, Amos Benari wrote:
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
Context still looks too big for me, but if that fits - why not.
Nice work.
LZ
···
On Mon, Oct 21, 2013 at 09:42:33AM -0400, Amos Benari wrote:
> Hi,
> I am suggesting a new foreman site map (top-menu), see attached screen-shot.
>
> Why?
> 1. Because we are planning to add Katello as a content and entitlement engine,
> and we need to make room for the additional content.
> 2. Better organize the menu items for easy access. The 'More' menu grue over the years and got too big.
> 3. Fit the plugin architecture better by creating a place to add additional menu items.
>
> What changed:
> Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
> Host, Discovered host and Facts are grouped under Hosts
> Configure and Provision sub-menus moved from More to the top-bar
> More is now called Administer and keeps the menu items Locations, Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks, Settings and About.
>
> Thanks,
> Amos.
>
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
In response to the comments:
I changed the order of the main items to be Hosts (Content) Provision Configure Monitor
Kept the 'verb' names for the reasons mentioned in the mail thread and because it is short.
Kept the Administer and didn't change to Admin because it may confuse.
Changed 'All host' to be befor 'Discovered hosts' because it is more commonly used.
Improved the interface for plugins.
Credits:
The design of the site-map is following the guidelines of a design work done by Kyle and others
in the Katello team, this is just foreman side of the implementation.
Interface for plugins:
I didn't go all the way to the fancy interface of Katello, instead I kept the code small and simple.
Every level of the menu creation is a method and can be changed in a plugin see example:
Please comment on the interface here or in the pull-request and I'll do add the needed changes.
Thanks,
Amos.
I like this. For the most part it is very similar to the sitemap I posted
earlier. The only thing I would like to see is Monitor appearing to the
furthest left like the first example. Traditionally a dashboard is meant to
give the user a quick lay of the land which informs decisions. As we have
no actual personas or targeted user information the best method for now is
to mirror basic order of operation not frequency of use. If the user does
not need the dashboard or any overview information to make decisions I
question their existence. Placing it on the right does not save anything it
just breaks expected behavior patterns.
Overall nice work.
···
On Monday, October 21, 2013 9:42:33 AM UTC-4, amos wrote:
>
> Hi,
> I am suggesting a new foreman site map (top-menu), see attached
> screen-shot.
>
> Why?
> 1. Because we are planning to add Katello as a content and entitlement
> engine,
> and we need to make room for the additional content.
> 2. Better organize the menu items for easy access. The 'More' menu grue
> over the years and got too big.
> 3. Fit the plugin architecture better by creating a place to add
> additional menu items.
>
> What changed:
> Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
> Host, Discovered host and Facts are grouped under Hosts
> Configure and Provision sub-menus moved from More to the top-bar
> More is now called Administer and keeps the menu items Locations,
> Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks,
> Settings and About.
>
> Thanks,
> Amos.
>
>
>
While still respecting Greg's input, I would vote to keep the current 'verb' names. I think it matches how people would talk, such as "click on Configure (>) Hostgroups" or "go to Monitor (>) Trends.
I would also shorten "Administer" to "Admin".
Just my 2 cents.
Joseph
···
----- Original Message -----
> From: "Greg Sutcliffe"
> To: "Foreman ."
> Sent: Monday, October 21, 2013 4:47:44 PM
> Subject: Re: [foreman-dev] suggestion for a new foreman site-map
>
> On 21 October 2013 14:42, Amos Benari wrote:
>
> > Hi,
> > I am suggesting a new foreman site map (top-menu), see attached
> > screen-shot.
> >
>
> I really like this, actually. My only suggestion would be to use nouns, not
> verbs (so Monitoring, Hosts, Configuration, Provisioning, Administration).
> That feels more natural to me.
>
> +1 overall though :)
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
> From: "Joseph Magen" <jmagen@redhat.com>
> To: foreman-dev@googlegroups.com
> Sent: Monday, October 21, 2013 10:35:37 AM
> Subject: Re: [foreman-dev] suggestion for a new foreman site-map
>
> Great job Amos. +1 from me.
>
> While still respecting Greg's input, I would vote to keep the current 'verb'
> names. I think it matches how people would talk, such as "click on
> Configure (>) Hostgroups" or "go to Monitor (>) Trends.
>
> I would also shorten "Administer" to "Admin".
+1. I think it also makes sense to move locations/organizations to be under "Configure" although I don't feel too strongly about that either way.
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
I really like this, actually. My only suggestion would be to use nouns, not
verbs (so Monitoring, Hosts, Configuration, Provisioning, Administration).
That feels more natural to me.
> Great job Amos. +1 from me.
>
> While still respecting Greg's input, I would vote to keep the current
> 'verb' names. I think it matches how people would talk, such as "click on
> Configure (>) Hostgroups" or "go to Monitor (>) Trends.
>
> I would also shorten "Administer" to "Admin".
>
I think this could end up confusing since it is common to have an "admin"
user.
···
On Mon, Oct 21, 2013 at 10:35 AM, Joseph Magen wrote:
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
I really like this, actually. My only suggestion would be to use nouns,
not
verbs (so Monitoring, Hosts, Configuration, Provisioning,
Administration).
That feels more natural to me.
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
I really like this, actually. My only suggestion would be to use nouns,
not verbs (so Monitoring, Hosts, Configuration, Provisioning,
Administration). That feels more natural to me.
···
On 10/21/2013 09:48 AM, Dominic Cleal wrote:
> On 21/10/13 14:42, Amos Benari wrote:
>> 3. Fit the plugin architecture better by creating a place to add additional menu items.
> I think a while ago we talked about an API for plugins to register new
> menu items instead of defacing the site. Maybe now's a good time to do
> that?
>
>
>> Hi,
>> I am suggesting a new foreman site map (top-menu), see attached
>> screen-shot.
>>
>
> I really like this, actually. My only suggestion would be to use nouns,
> not verbs (so Monitoring, Hosts, Configuration, Provisioning,
> Administration). That feels more natural to me.
>
+1, but could you please put the most common action as the first dropdown ?
e.g. under Hosts, put All as the first selection?
Ohad
Hosts
···
On Mon, Oct 21, 2013 at 4:47 PM, Greg Sutcliffe wrote:
> On 21 October 2013 14:42, Amos Benari wrote:
>
>> Hi,
>> I am suggesting a new foreman site map (top-menu), see attached
>> screen-shot.
>>
>> Why?
>> 1. Because we are planning to add Katello as a content and entitlement
>> engine,
>> and we need to make room for the additional content.
>> 2. Better organize the menu items for easy access. The 'More' menu grue
>> over the years and got too big.
>> 3. Fit the plugin architecture better by creating a place to add
>> additional menu items.
>>
>> What changed:
>> Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
>> Host, Discovered host and Facts are grouped under Hosts
>> Configure and Provision sub-menus moved from More to the top-bar
>> More is now called Administer and keeps the menu items Locations,
>> Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks,
>> Settings and About.
>>
>> Thanks,
>> Amos.
>>
>>
>> Would you suggest that katello plug into these?
My assumption that we add a new top bar called Content, and for the rest
(Systems, Admin etc) we merge with the existing?
Ohad
···
On Mon, Oct 21, 2013 at 4:56 PM, Bryan Kearney wrote:
> On 10/21/2013 09:42 AM, Amos Benari wrote:
>
>
> > From: "Joseph Magen" <jmagen@redhat.com>
> > To: foreman-dev@googlegroups.com
> > Sent: Monday, October 21, 2013 10:35:37 AM
> > Subject: Re: [foreman-dev] suggestion for a new foreman site-map
> >
> > Great job Amos. +1 from me.
> >
> > While still respecting Greg's input, I would vote to keep the current
> > 'verb'
> > names. I think it matches how people would talk, such as "click on
> > Configure (>) Hostgroups" or "go to Monitor (>) Trends.
> >
> > I would also shorten "Administer" to "Admin".
>
> +1. I think it also makes sense to move locations/organizations to be under
> "Configure" although I don't feel too strongly about that either way.
I think it makes sense to keep locations/organizations under admin menu, as
it should be over all the other actions, it's similar to users administration.
Another way of looking at it could be, let's say every menu section being as a
separate plugin. If I don't have foreman-configure installed, I would not be able
to use orgs/locations for provisioning.
– Ivan
···
----- Original Message -----
> ----- Original Message -----
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
I really like this, actually. My only suggestion would be to use nouns,
not
verbs (so Monitoring, Hosts, Configuration, Provisioning,
Administration).
That feels more natural to me.
First off, I'll admit my knowledge of Foreman entities is cursory at best,
which means that when I look at a menu structure that menu should tell me a
story. That story should be one in which I can logically discover pieces,
and appear in order that makes some sense as a workflow for the application
both left to right and top to bottom. Given that, I realized the old and
proposed menu structures were missing the story for me - I didn't feel like
I understand pieces were contextually related and how I should go about
interacting with them. Thus, I set out to do some research and use my new
found understanding of how the pieces fit and how a user my go about using
each to inspire a proposed organization for links. They are in the order of
left to right for top level navigation and top to bottom for sub-nav.
···
On Wed, Oct 23, 2013 at 3:38 PM, Kyle Baker wrote:
+1 to nouns.
I like this. For the most part it is very similar to the sitemap I posted
earlier. The only thing I would like to see is Monitor appearing to the
furthest left like the first example. Traditionally a dashboard is meant to
give the user a quick lay of the land which informs decisions. As we have
no actual personas or targeted user information the best method for now is
to mirror basic order of operation not frequency of use. If the user does
not need the dashboard or any overview information to make decisions I
question their existence. Placing it on the right does not save anything it
just breaks expected behavior patterns.
Overall nice work.
On Monday, October 21, 2013 9:42:33 AM UTC-4, amos wrote:
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
Why?
Because we are planning to add Katello as a content and entitlement
engine,
and we need to make room for the additional content.
Better organize the menu items for easy access. The ‘More’ menu grue
over the years and got too big.
Fit the plugin architecture better by creating a place to add
additional menu items.
What changed:
Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
Host, Discovered host and Facts are grouped under Hosts
Configure and Provision sub-menus moved from More to the top-bar
More is now called Administer and keeps the menu items Locations,
Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks,
Settings and About.
>
>
>
>
>>
>>> Hi,
>>> I am suggesting a new foreman site map (top-menu), see attached
>>> screen-shot.
>>>
>>> Why?
>>> 1. Because we are planning to add Katello as a content and entitlement
>>> engine,
>>> and we need to make room for the additional content.
>>> 2. Better organize the menu items for easy access. The 'More' menu grue
>>> over the years and got too big.
>>> 3. Fit the plugin architecture better by creating a place to add
>>> additional menu items.
>>>
>>> What changed:
>>> Dashbord, Reports, Statistics, Trends and Audit are grouped under Monitor
>>> Host, Discovered host and Facts are grouped under Hosts
>>> Configure and Provision sub-menus moved from More to the top-bar
>>> More is now called Administer and keeps the menu items Locations,
>>> Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks,
>>> Settings and About.
>>>
>>> Thanks,
>>> Amos.
>>>
>>>
>>> Would you suggest that katello plug into these?
>
>
> My assumption that we add a new top bar called Content, and for the rest
> (Systems, Admin etc) we merge with the existing?
>
I think that's a good starting place, although, splitting out entitlement
related pages to their own section makes sense to me (since entitlements
bridge content and systems).
-Eric
···
On Mon, Oct 21, 2013 at 10:01 AM, Ohad Levy wrote:
> On Mon, Oct 21, 2013 at 4:56 PM, Bryan Kearney wrote:
>> On 10/21/2013 09:42 AM, Amos Benari wrote:
>
>>
>>
>>
>>
>>>
>>>> Hi,
>>>> I am suggesting a new foreman site map (top-menu), see attached
>>>> screen-shot.
>>>>
>>>> Why?
>>>> 1. Because we are planning to add Katello as a content and entitlement
>>>> engine,
>>>> and we need to make room for the additional content.
>>>> 2. Better organize the menu items for easy access. The 'More' menu grue
>>>> over the years and got too big.
>>>> 3. Fit the plugin architecture better by creating a place to add
>>>> additional menu items.
>>>>
>>>> What changed:
>>>> Dashbord, Reports, Statistics, Trends and Audit are grouped under
>>>> Monitor
>>>> Host, Discovered host and Facts are grouped under Hosts
>>>> Configure and Provision sub-menus moved from More to the top-bar
>>>> More is now called Administer and keeps the menu items Locations,
>>>> Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks,
>>>> Settings and About.
>>>>
>>>> Thanks,
>>>> Amos.
>>>>
>>>>
>>>> Would you suggest that katello plug into these?
>>
>>
>> My assumption that we add a new top bar called Content, and for the rest
>> (Systems, Admin etc) we merge with the existing?
>>
>
> I think that's a good starting place, although, splitting out entitlement
> related pages to their own section makes sense to me (since entitlements
> bridge content and systems).
>
No issues from my side, I just aligned whats in katello today.
···
On Mon, Oct 21, 2013 at 5:04 PM, Eric D Helms wrote:
> On Mon, Oct 21, 2013 at 10:01 AM, Ohad Levy wrote:
>> On Mon, Oct 21, 2013 at 4:56 PM, Bryan Kearney wrote:
>>> On 10/21/2013 09:42 AM, Amos Benari wrote:
>
> First off, I'll admit my knowledge of Foreman entities is cursory at best,
> which means that when I look at a menu structure that menu should tell me a
> story. That story should be one in which I can logically discover pieces,
> and appear in order that makes some sense as a workflow for the application
> both left to right and top to bottom. Given that, I realized the old and
> proposed menu structures were missing the story for me - I didn't feel like
> I understand pieces were contextually related and how I should go about
> interacting with them. Thus, I set out to do some research and use my new
> found understanding of how the pieces fit and how a user my go about using
> each to inspire a proposed organization for links. They are in the order of
> left to right for top level navigation and top to bottom for sub-nav.
>
> Original - https://gist.github.com/ehelms/7140844
>
> Monitoring
> - Dashboard
> - Reports
> - Facts
> - Statistics
> - Trends
> - Audits
>
> Hosts
> - Managed Hosts
> - Discovered Hosts
>
> - Provisioning Setup
> - Hardware
> - Architecture
> - Hardware type
> - Software
> - Provisioning Templates
> - Operating System
>
> - Partition Table
>
> Configuration
> - Host Groups
>
> - Global Parameters
> - Puppet
> - Environments
> - Classes
>
> - Smart Variables
>
> Infrastructure
> - Smart Proxies
>
> - Compute Resources
> - Networking
> - Subnets
> - Domains
>
> - Installation Media
> - LDAP Server
>
> Administer
>
> - Organizations
> - Locations
> - Users
> - User Groups
>
> - Roles
> - Bookmarks
> - Settings
> - About
>
>
> Thoughts?
>
>
> -Eric
>
>
> Apologies for posting in the Dev Thread, I'll come clean from the start
and admit I'm just a user but I saw this thread and it piqued my interest.
Let me start off by saying (IMO) the best change proposed so far is
banishing the "more" menu to UI hell, not only did it hide some key
functionality but it was fiddly to get to at speed. If nothing else came
from this discussion but that change, it would still be a success.
Another +1 for nouns they look and sound better, though I can sympathise
with trying to minimise the length of the text.
The Monitoring, Hosts, Configuration, Provisioning, Admin(+1 for Joseph,
Sam & Length) ordering makes sense using Kyle's reasoning but Lukas is
also right with his ordering of a standard "deployment" workflow. I would
take the best of both and use Monitoring, Hosts, Configuration,
Provisioning, (Content), Admin which means that users would work
right-to-left when initially setting things up (including setting Orgs/Locs
in the Admin section) but left-to-right during normal day to day use
and drill-down faulting.
I would be weary of throwing out the baby with the bath water and
completely reorganising everything as per Eric's suggestion, (again
IMO) nothing is actually broken, as Amos' justifications for the changes
show, and you run the risk of needlessly confusing your current user base.
HTH
Charlie
···
On Thursday, 24 October 2013 19:39:23 UTC+1, Eric Helms wrote:
On Wed, Oct 23, 2013 at 3:38 PM, Kyle Baker <kyle...@gmail.com<javascript:> > > wrote:
+1 to nouns.
I like this. For the most part it is very similar to the sitemap I posted
earlier. The only thing I would like to see is Monitor appearing to the
furthest left like the first example. Traditionally a dashboard is meant to
give the user a quick lay of the land which informs decisions. As we have
no actual personas or targeted user information the best method for now is
to mirror basic order of operation not frequency of use. If the user does
not need the dashboard or any overview information to make decisions I
question their existence. Placing it on the right does not save anything it
just breaks expected behavior patterns.
Overall nice work.
On Monday, October 21, 2013 9:42:33 AM UTC-4, amos wrote:
Hi,
I am suggesting a new foreman site map (top-menu), see attached
screen-shot.
Why?
Because we are planning to add Katello as a content and entitlement
engine,
and we need to make room for the additional content.
Better organize the menu items for easy access. The ‘More’ menu grue
over the years and got too big.
Fit the plugin architecture better by creating a place to add
additional menu items.
What changed:
Dashbord, Reports, Statistics, Trends and Audit are grouped under
Monitor
Host, Discovered host and Facts are grouped under Hosts
Configure and Provision sub-menus moved from More to the top-bar
More is now called Administer and keeps the menu items Locations,
Organizations, Users(LDAP, Users, Users group and Roles), Bookmarks,
Settings and About.
Thanks,
Amos.
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
