Make WordPress Design

Tagged: trac Toggle Comment Threads | Keyboard Shortcuts

  • Jen 7:18 pm on September 14, 2011 Permalink
    Tags: admin bar, , header, trac   

    #18197 – New Admin Bar/Header Combo 

    As you know part of the scope for 3.3 was a revised admin bar that would reduce duplication in the admin header. The first draft of it has been posted to Trac.


    It needs a color refresh, some optimization, some decisions about which links going where, etc, but is the starting point we are using. Would like to get it back toward the lighter gray we used in the header before, but with some border maybe so it doesn’t look like browser chrome. Fiddling with the links and stuff will happen on Trac, but if anyone wants to mock up some color variations, we have until Sunday.

  • Jen 3:27 pm on September 10, 2011 Permalink
    Tags: , , trac   

    #17739 – Comment prompt text is misleading 


    Need a better label for email field in default theme comment form so it doesn’t sound like it’s promising peace, justice, and respect for email address privacy by blog author/owner.

  • Jen 3:05 pm on September 10, 2011 Permalink
    Tags: , network admin, trac   

    #18301 – Multisite Theme Activation 


    Goal of this ticket is to make it faster and easier to activate themes in multisite installs. See my comment on the ticket. Looking at a) possible label change, b) adding a highlight state to the themes list table, and/or c) any UI suggestion that would make this process easier. Let’s hash out early ideas and/or mockups here, and when we’ve got something solid, move over to trac.

    • Andrea_R 3:40 pm on September 10, 2011 Permalink | Log in to Reply

      Might want to consider making the themes enabled by default instead. Right now, the process is backwards to how plugins are installed. If you install a plugin, it’s available right away.

      And yes, we have seen the language issue come up with the word “enable” vs “activate”.

      • Jane Wells 4:34 pm on September 13, 2011 Permalink | Log in to Reply

        I think the difference between themes and plugins is that lots of multisite installs have custom themes per site or sets of sites, vs plugins that provide functionality but don’t affect the branding.

      • Ipstenu 5:41 pm on September 13, 2011 Permalink | Log in to Reply

        On the other hand, Plugins are ‘weird’ because you cannot (easily, without another plugin) activate a plugin on JUST one site. The two work in totally separate worlds already.

  • Jen 9:54 pm on May 4, 2011 Permalink
    Tags: , , , , trac   

    #17324 – UI Style Update 

    This thread is for suggestions/questions about the UI decisions in the 3.2 style update, so the trac ticket can be kept clean for ‘this needs to be done’ tasks identified by leads and/or bug reports related to the style code.

    • Ryan Imel 11:38 pm on May 4, 2011 Permalink | Log in to Reply

      First pass looks awesome, psyched to see some of the ideas being implemented.

      Is the idea that Dashboard widgets will be draggable from only the header, still, or will that be workable on the whole of the widget too?

      I’ll be keeping an eye on things. I can contribute patches to help things along as soon as it’s time for that.

    • Chelsea Otakan 12:40 am on May 5, 2011 Permalink | Log in to Reply


      Did another comp trying a shaded box style with light borders. A little more along the line of the style described in the initial post.

      Switched the Right Now numbers to Helvetica. I imagine we’ll be using more sans serif now that we’re
      using Helvetica/Arial instead of Lucida Sans.

      Included a button-ish treatment for the expand/collapse buttons. I know we might nix these on the Dashboard, but there are still collapsible boxes in other parts of the UI

      Bolded the text on the Nav menu.

      The style is a little Apple-ish, let me know what you think :]
      Made the arrow indicator a size between the large and small below.

    • Greenshady 2:03 am on May 5, 2011 Permalink | Log in to Reply

      I don’t have any suggestions and will leave UI to folks that are good at it. But, I just wanted to drop a line and say that you all are doing an awesome job with this. I haven’t been this excited about the UI since we got rid of the old v.2.5 look.

    • Doug 5:09 am on May 5, 2011 Permalink | Log in to Reply

      Questions about names and places:

      1) Could the tops of metaboxes end up being called something besides “title bars?”

      2) The top area, below the newish Admin Bar, was “Admin Header”; will that whole area still be named that now that it’s more obviously two levels instead of one?

      3) For multisite, will the toggle between Site Admin/Network Admin still be in the pipes between Howdy [User] and Log Out?

      This could be a little early because this is still in flux…

    • Ran Yaniv Hartstein 9:20 am on May 5, 2011 Permalink | Log in to Reply

      The new design is gorgeous, but is also very conservative and pale. How about spicing things up a bit with some more color in the default color scheme?

      • Ran Yaniv Hartstein 11:14 am on May 5, 2011 Permalink | Log in to Reply

        Also, minimizing the menu is quite challenging ATM – very hard to locate that right spot on the horizontal separators to click on. Can the vertical separator be made clickable instead?

        • Chelsea Otakan 3:02 pm on May 9, 2011 Permalink | Log in to Reply

          I believe we’re planning to nix the minimize function all together eventually, since you can add and remove boxes from a screen using screen options

    • Ken Newman 8:38 pm on May 5, 2011 Permalink | Log in to Reply

      Footer is broken on many pages. Can markup be changed or is this CSS/Graphics only refreshment? With the layout as it is, the footer likely can be put into #wpcontent

      • Daryl Koopersmith 4:40 am on May 6, 2011 Permalink | Log in to Reply

        Can you provide examples of pages where the footer is broken? Screenshots, active plugins, and browser details would be especially helpful. Thanks.

        • scribu 8:48 pm on May 6, 2011 Permalink | Log in to Reply

          Firefox 4:

          (latest nightly, not trunk)

        • Ken Newman 3:57 pm on May 9, 2011 Permalink | Log in to Reply

          I added a patch to trac. The issue is #adminmenuback’s inheritance of the #wpwrap element’s min-height 100% which doesn’t account for the footer element (by 46px) so the menuback comes up short. It’s only visible when the main content generates scrollbars (meaning you can see it on all pages if you shrink the window.)

          Appears on IE 9, Firefox 4, but not Webkits

          • Ken Newman 4:02 pm on May 9, 2011 Permalink | Log in to Reply

            unfortunately my patch doesn’t correct IE it seems.

          • Ken Newman 4:13 pm on May 9, 2011 Permalink | Log in to Reply

            Putting #adminmenuback up a level (with wpfooter, wpadminbar, etc.) would be a cleaner, easier fix.

          • Ken Newman 5:25 pm on May 9, 2011 Permalink | Log in to Reply

            My brain is mush. Giving #wpwrap overflow:hidden fixes IE 8, 9 and Firefox 4, no adverse effects on Webkit.

            Still a footer issue if the left and right have too much content and line-wrap tho (but that’d be rare).

    • saracannon 9:14 pm on May 5, 2011 Permalink | Log in to Reply

      I’ve been following along with Daryl’s changes in trac and applying the changes to the Blue Admin. (colors-classic.dev.css) I’ve uploaded a diff to the ticket of what I’ve modified so far if you wanted to download it to see what I’ve done so far.

      The colors-fresh.dev.css and the colors-classic.dev.css now match line-for line. There is still more tweaking to be done with colors/borders/menus/widgets. As we go along, I’ll be replacing the patch with modifications following daryl’s modifications.

      Screenshot: http://cl.ly/302k273J0e1l0l1B3v1k

      I will post up for a review all the blue changes here after the grey is set in stone. :]

    • Ken Newman 9:21 pm on May 5, 2011 Permalink | Log in to Reply

      I’d like to make the sidebar “fixed” and let the right side scoll (when necessary), clean up some negative margin hacks, move the footer markup into the wrapper element (probably as deep as wpcontent) while keeping it attached to the bottom when appropriate, and get in a better adminbar bump.

      I’ll be working on a patch tonight for this, contingent on whether markup changes and fixed positioning can be considered…

      • jane wells 11:43 pm on May 5, 2011 Permalink | Log in to Reply

        We would not have the sidebar fixed for usability reasons.

        • Ken Newman 12:11 am on May 6, 2011 Permalink | Log in to Reply

          I had considered the problem of the sidebar getting to large for the window, and concluded that a second scrollbar would appear on the right… but it’s kinda ugly… I guess I’ll work on a plugin for proof of concept.

          • Jane Wells 12:14 am on May 6, 2011 Permalink | Log in to Reply

            We looked at it as a possibility back in 2.7 and it was immediately discarded. Since it’s the same group of leads, it’s unlikely that the team would go for the double scroll.

          • Dean Robinson 1:26 am on May 8, 2011 Permalink | Log in to Reply

            Yeah I’d definitely avoid anything that introduces a double scroll. While I like having the menu fixed in place (which is why I added the option to Fluency) I completely agree that for the default WP collapse/expand style menu it wouldn’t work.

            However, if the menu was fixed in place, the menu length issue could potentially be handled in a way so that if the current screen height was less than the menu height then the menu switched from being fixed to not-fixed – while in theory that could work I think it over-complicates it for the average user.

    • Nasul 7:32 am on May 6, 2011 Permalink | Log in to Reply


      I like what you did with the admin area but have you seen what the guys from Blogger did? http://buzz.blogger.com/2011/03/fresh-new-perspectives-for-your-blog.html
      Will WordPress (core) have something like Infinite scrolling and posibility to download images as you view them, not all at once in advance?
      I like the Blogger Views and it would be nice if you would implement something like this in a future version of WP.

      Best wishes

    • Hugo Baeta 12:29 pm on May 6, 2011 Permalink | Log in to Reply

      Just had the oportunity to check out the UI improvements you’re doing on the new dashboard and one thing that immediately felt strange is the background color being white on the main content area. I played a bit with the CSS in firebug and made some changes, mainly switching the background color to #f9f9f9. I also changes the boxes background color to #efefef and tweaked the border-radius for something more subtle, 4px. (instead of the old 6px).

      Check it out: http://cl.ly/342H3N2n2W1X0z090h3K

    • Travis Northcutt 2:08 pm on May 6, 2011 Permalink | Log in to Reply

      Has a final decision already been made (publicly or not) on full width header vs. as it is right now (header is only to the right of the left nav column)? I think a strong case can be made for a full width header, but I don’t want to waste anyone’s time doing so if it’s already final.

    • Aaron D. Campbell 4:15 pm on May 6, 2011 Permalink | Log in to Reply

      I loved the mockups, but seeing it in actual dashboards the shadow on the admin menu seems excessive (overpowering). Maybe we should lighten up ../images/menu-shadow.png or even just get rid of it? I personally think it looks really nice without it, but I’m probably more minimalist than most.

    • James Dimick 10:16 am on May 7, 2011 Permalink | Log in to Reply

      I kinda wish the new admin menu worked more like this for multi-line top level menu items:

    • Andrew Ozz 5:53 pm on May 7, 2011 Permalink | Log in to Reply

      There are several things that IMHO looked better before:

      Font face, the previously used font looks better and is easier to read at small sizes. If we are staying with Arial think we would need to increase the “normal” size by at least 1px, possibly 2px.

      The background used to be a very light shade of grey (f9f9f9) and all postboxes and other components had white backgrounds. That brought the illusion of the components being on top of the background (as it should be logically). Now the background is white and all components are light grey which is contra intuitive. The difference is very small and it seems to work on subliminal level (feels right vs. feels wrong). I tried swapping the background colors and it “felt right”.

    • tonyjansen_nl 6:26 pm on May 7, 2011 Permalink | Log in to Reply

      Helvetica Neue Light is best used for body copy (on paper), not for on-screen headings and other key element of a UI. Please consider setting those elements in a non ‘light’ typeface or bold.
      If the designer wishes to persist in this misguided way, then please consider setting -webkit-font-smoothing and text-rendering appropriatly.

    • Wayne 7:48 pm on May 7, 2011 Permalink | Log in to Reply

      okay, so i’m like comment #191291023123

      something i’ve been wondering for a while, why is the edit post page limited to 2 columns? I have tons of custom post types that don’t even use the main editor and would love to be able to use 3 or 4 columns…

      is that doable?

    • Andrew G 1:09 am on May 8, 2011 Permalink | Log in to Reply

      I like the existing UI better than what I currently see in trunk. Many of the changes are a step backwards, particularly the decision to use Arial. I mean, seriously, Arial!? Please, please keep the font(s) currently in use. There’s nothing wrong with them. The widgets/menus also look worse than what is in the existing UI.

      About the only thing I like is the option to collapse the sidebar. But then, the sidebar should not reach to the top of the page. It’s better for the header to stretch across the screen, as it does now.

      If you want more color in the current UI, why not make the blue visual scheme the default?

    • Dean Robinson 1:12 am on May 8, 2011 Permalink | Log in to Reply

      I feel that the current shadow used on the admin menu looks a little weird, I think the shadow need to either be a shadow that fades completely into the menu colour, or it needs to be solid colour – not a combination of both which is what the current one looks like examples of each -> http://cl.ly/6Z54

    • Mamaduka 10:26 am on May 8, 2011 Permalink | Log in to Reply

      This style updates looks great. But I think Contextual Help and Screen Options link wrappers don’t fit with new style, so I just changed few things to fit new style -> https://i.imgur.com/lnnH8.jpg

    • Matt Thomas 9:42 pm on May 8, 2011 Permalink | Log in to Reply

      r17324 made me a little sad; I thought the larger icon and headline were important for visual hierarchy. Just my 2¢. 🙂

      • Matt Thomas 9:43 pm on May 8, 2011 Permalink | Log in to Reply

        Uh, duh, sorry, that’s 17833.

      • James Dimick 10:13 pm on May 8, 2011 Permalink | Log in to Reply

        I definitely agree there.

      • Dean Robinson 11:03 pm on May 8, 2011 Permalink | Log in to Reply

        I like the little icons, don’t have any well thought out reason why, I just do. But I agree that the page headline does seem to get a little lost at the smaller size.

        If it is to stay at the small size maybe the font-weight could be bumped up, and/or the white-space above and below the headline increased to stop it blending in?

        • Ken Newman 9:41 pm on May 9, 2011 Permalink | Log in to Reply

          giving a little breathing room above it could make the smaller sizes more comfortable.

      • Ryan Boren 12:05 am on May 9, 2011 Permalink | Log in to Reply

        I’d like to move the 3.1-style icon32 and page title from the h2 up into the h1. Let it be big and beautiful right at the top. What to do with the blog name though. I played around with relocating the blog name over into the “Howdy, $user” user_info block. “Welcome to $blog_name, $user” and such. The blog name would have to be truncated quite a bit and “Welcome to Make WordPress U…, ryan” might not read so well. 🙂 The home url could be used instead, perhaps. “Welcome to make.wordpress.org/ui, ryan” I like it, but I have curiously strong dislike for the way the blog name currently (3.1) has so much weight and takes up so much vertical space.

        • Erik Teichmann 11:59 am on May 9, 2011 Permalink | Log in to Reply

          I think it’s important for the blog name to be prominent — I administer a decent number of WordPress sites, frequently having the admin area of more than one open at a time. A prominent blog title keeps me from making stupid mistakes and changing settings or content on the wrong site.

        • Otto 7:40 pm on May 31, 2011 Permalink | Log in to Reply

          The blog name is far more important. It’s a link to the front end of the site. People click on it to go to the front end of the site. By reducing its footprint, you’ve made it far harder to view the actual site from the admin end of things.

          I click on that link all the time, and am now dismayed to find it harder to find and click on. It hurts usability to reduce that title’s size.

          • Jane Wells 7:45 pm on May 31, 2011 Permalink | Log in to Reply

            Really, “far harder”? It’s not hard. Of all the things people reacted to when we ported te .com (600+ comments) no one was bothered by making the site name smaller. Getting rid of favorites upset people, not having full TMCE toolbar in dfw caused complaint, and people didn’t like the smaller Arial body text, but no one said it was now too hard to click on the site name.

            • Otto 7:47 pm on May 31, 2011 Permalink | Log in to Reply

              It seems to be a fairly common complaint amongst the people I’ve been seeing start to switch to 3.2. I recently started using it and it was the main thing I noticed right away as making the admin more difficult to use. I had to actually search to find a link to get back to the front end of my site. If I have to look for things and have trouble finding them, then I think that’s a bit of a problem.

      • Chelsea Otakan 3:08 pm on May 9, 2011 Permalink | Log in to Reply

        +1 for larger icons. Right now the Blog Header and the Section Headers are competing a little oddly

      • John James Jacoby 8:46 pm on May 9, 2011 Permalink | Log in to Reply

        +1 for larger icons.

      • luffer 11:56 am on July 5, 2011 Permalink | Log in to Reply

        +1, this change has killed my productivity. The site title should be big and obvious, now it’s smaller than the page title below it, which makes the hierarchy look odd. I click on the site title all the time and use it to see which site I’m working on. It’s probably one of my most clicked links in the Dashboard and now it’s one of the smallest!

    • andrew_cpht 10:21 pm on May 8, 2011 Permalink | Log in to Reply

      In the last few nightlies, the link to the Network Admin moved into a dropdown menu next to “Howdy User.” This is incompatible with the iPad (which is my primary means of administrating my site) as the iPad doesn’t support the hover that is being used. It also makes it less obvious that there IS a Network Admin page, unless you happen to notice that little arrow next to your name (which I personally associate with the user profile anyway, not Site vs User admin.

      • andrew_cpht 10:25 pm on May 8, 2011 Permalink | Log in to Reply

        And as long as I’m on the subject of the iPad, is there anyway you could make the widgets admin function on the iPad/other tablets? There is currently no way to drag widgets across the screen.

    • John James Jacoby 9:05 pm on May 9, 2011 Permalink | Log in to Reply

      While putting contextual help into the bbPress plugin, I’ve accidentally logged myself out a few times because of the sensitivity of the user mouse over. Few thoughts:

      1. Delay the menu by a half second or so
      2. Use click instead of hover + use rotated “Collapse Menu” button to identify as button
      instead of lone-triangle
      3. Could use the new “New Post” drop down style up there, instead of another dedicated UI element.

      • jane wells 10:09 pm on May 9, 2011 Permalink | Log in to Reply

        It’s not a button, it’s a toggle. Not adding extra cognitive load and visual density up there by putting a button around it. We are trying flipping the tabs up in the update Daryl is working on.

        • John James Jacoby 2:54 am on May 10, 2011 Permalink | Log in to Reply

          The part that I’m referencing looks like a button: rounded, outward bevel, with a hover state.

          The result of clicking it is a toggle, but it’s styled like a button. Not any different than the HTML/Visual pill-style buttons in DFW. They toggle, but they are buttons.

    • smub 3:26 am on May 12, 2011 Permalink | Log in to Reply

      Not really digging the Bolded Menu Links… maybe its just my eyes, but it seems a bit too aggressive… I like the unbolded version better.

    • c3mdigital 2:02 pm on May 12, 2011 Permalink | Log in to Reply

      UI Suggestions (3.2 beta 1)

      I prefer the old font-stack better and it doesn’t feel like WordPress to me without Lucida Grande.
      The .wrap h2 font should be serif to keep titles consistant.
      The h1 site heading and icon is too small. Maybe 20px or use blue. From a UI perspective users have become accustomed to using this link to access the front end.

      Other than that an icon refresh would be nice.

    • chrishoward 7:45 am on May 16, 2011 Permalink | Log in to Reply

      Stylistically, this is looking great. And these comps look ok. But when I use 3.2b1, it quickly becomes evident that there’s an issue with visual hierarchy once other menus are selected, especially as you head towards the lower menus.

      The selected menu title background is too strong in relationship to its importance. Is it the thing you want the user’s eye always coming back too? No. You want the user’s eye to naturally head to the top of the main area and then comfortably work down through it.

      It works ok on the Dashboard, but others, not so well. E.g checkout Settings. Your eye gets stuck down there alternating between the selected menu title, and the save button.

      The other factor is it is an arrow and arrow says “Look here!” Often “here” is blank space and/or irrelevant to where you really want the user looking.

      Therefore, something has to be done to give the section title or thereabouts a stronger draw for the eye.

      One solution is to employ the design principle of repetition, and match the blog header background to the selected menu title’s background. I’d also tend to lighten both too. The eye then naturally finds its way to the top of the page with feeling the tug of the selected menu title.

      Here’s a bit of a hack of the sort of thing I mean. http://d.pr/XHC2

      Other folks may have even better solutions.

    • Otto 7:37 pm on May 31, 2011 Permalink | Log in to Reply

      Question: Why is the Site Title and WP logo so bloody small? I use that link all the time, and now it’s difficult to find and click on. Suggest doubling its visual height, or at least 1.5’ing it. Also suggest reducing the size of the rather useless Page Title and icon.

      The Site Title is actually important, people click on it to go to the front end view of their site. The name of the page the person is on is redundant. They know what page they’re on, they’re looking at the page. With this shift in sizing, the link people use often is now difficult to click on, while the redundant information isn’t clickable anyway.

      • Jane Wells 7:42 pm on May 31, 2011 Permalink | Log in to Reply

        Core team felt it took up too much room. People know what their site is called.

        • Otto 7:45 pm on May 31, 2011 Permalink | Log in to Reply

          People on multi-site find it handy to know what site they’re on at a glance, and having a big and obvious link to the front of the site is a good thing.

          Do I need to write a plugin to correct this, or is there still room for debate on it before 3.2 ships?

        • luffer 11:49 am on July 5, 2011 Permalink | Log in to Reply

          Core team are showing how little they know about how people actually use WordPress then! I use the site title all the time to get onto my site, this “minor” change has had massive repercussions for the way I work!

    • luffer 11:47 am on July 5, 2011 Permalink | Log in to Reply

      The new font in the HTML editor is terrible and unreadable. Why was this changed? How can I get the old “Sans” style back? My productivity has taken a massive hit today, I’m not impressed!

  • Jen 6:44 pm on April 29, 2011 Permalink
    Tags: , right now, trac   

    #17283 – Color coding off in multisite Right Now box 

    Multisite adds:

    Storage Space 100MB Space Allowed 0MB (0%) Space Used

    …and “Space Used” is green by default. It should be gray since it doesn’t denote an action has applied a positive status. Gray until the ‘almost near limit’ color kicks in.

  • Jen 6:15 pm on April 29, 2011 Permalink
    Tags: , , , , links, trac   

    #17282 – Dashboard Recent Comments “View All” update 

    The “View All” buttons on the dashboard boxes are weird b/c they are buttons, but they aren’t actions, they are links. Would like to start switching over to a standard where buttons are mostly reserved for action/commitments, not just links to another screen.

    Suggestions for Recent Comments box: instead of “View All” button, replace with links to the various views of the comments screen. So:

    View All | Pending (24) | Approved | Spam (6) | Trash (3)

    …where the link styles are the same as on edit-comments.php

  • Jen 6:01 am on April 16, 2011 Permalink
    Tags: , , list-pages, pages, trac   

    Trac UI challenge:
    Probably not that much of a challenge, necessarily, but would need approved mockups for someone to want to start a patch. Collapsible page hierarchy on edit.php?post_type=page.

  • Jen 10:01 pm on April 2, 2011 Permalink
    Tags: alerts, , trac   

    Made a ticket for something that has been on our radar since 2.7 was in development, but just never got any kind of prioritization because it was minor compared to more serious UI things. That said, since it’s kind of minor, would be a nice thing to whip out.

    Ticket #17028 – Move the “last edited at” text and saved/updated/published notices in post/page editor
    1. The timestamp of the last save is currently displayed at the bottom right of the editor box. It would make more sense for this information to be tied to the Publish box instead.
    2. The yellow alert boxes that appear at the top of the page are weird. a) They should appear closer to the button that caused the action (general usability/accessibility best practice), so probably by the Publish box. b) Once you edit anything on the screen, the “post updated” (or saved, etc) text should go away, because it is no longer current.
    Am thinking we could combine these two things into one flexible status message that’s located in or adjacent to the Publish box.

    • Wiki Chaves 5:23 pm on April 4, 2011 Permalink | Log in to Reply

      Great idea to move the notices and make them disappear. Also it would be great if is technically possible to remove the ‘&message=1’ string.

      I would love to start contributing on the UI group with minor tasks 🙂


    • Chelsea Otakan 6:47 pm on April 5, 2011 Permalink | Log in to Reply

      Pretty simple comp that adds “Draft saved” and “Last edited” information to the Publish box and moves alerts above the Publish box and into the right column.

      Did Ben Dunkle also design the calendar icon for “Publish”? Would it be worth looking into making icons for all the publish info for better visual cues?


    • Andew Ryno 1:01 am on April 18, 2011 Permalink | Log in to Reply

      If a comp for this gets approved I’d be interested in working on implementing it.

      As for moving the yellow notice boxes, I agree on the point that they should be close to the button that performed the action. However, it would also make that notice bar appear differently on different pages, making it inconsistent. Is this something where general UX might trump consistency?

      • chexee 10:42 pm on April 18, 2011 Permalink | Log in to Reply

        I think so. IMO, consistency is important because it contributes to UX by giving users a good expectation of behavior. If that behavior is expected, but still unclear, then its not really contributing to UX anyway. Consistency should contribute to UX, not hinder it.

  • Jen 2:38 pm on January 6, 2011 Permalink
    Tags: ok/cancel, reset form, scheduled posts, timestamp, trac   

    #16068 – Reverting from Scheduled post t… 

    #16068 – Reverting from Scheduled post to Publish Immediately.
    Related older ticket: #8368 – Scheduling post time behavior and language refinements

    See ticket for description of problem, pro/con of implementing. The Publish box is kind of a mess that we want to look at in 3.2 anyway, so it wouldn’t hurt for people to start playing around with the best way to incorporate a ‘reset’ feature if we decided 90% of users really need it.

  • Jen 1:58 pm on January 6, 2011 Permalink
    Tags: , email, , settings, trac, username, users   

    Ticket #15942 – Username vs. Email for I… 

    Ticket #15942 – Username vs. Email for Identifying Users

    Reported Problem: “When I create a new blog in a network, I am asked to enter the Admin Email. This is rather useless to me because all our accounts come from an LDAP directory. So I have to remember the site admin’s email address, which is not always consistent across my organization. It would be nicer if I had an autocomplete-style field where I could enter the user’s ID.”

    The issues of selecting existing users vs. adding new users and doing so by email address vs. username touches more admin interactions than just this one. We’ll need to address it as a whole rather than just focusing on this one person’s complaint, but using this ticket as a starting point for discussion.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar