Making WordPress.org

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#1290 closed enhancement (wontfix)

Standardize the user login form on all w.org sites headlines

Reported by: ramiy's profile ramiy Owned by:
Milestone: Priority: normal
Component: General Keywords:
Cc:

Description (last modified by netweb)

w.org has many sites. They all have the same header.

But the 'headline' is not identical (For example, the blog has no headlines at all).

More important, the user login form on right side of the headline is different across different site.

Lets standardize the login forms view, and add the user login to all w.org pages!

Attachments (11)

showcase.png (40.5 KB) - added by ramiy 10 years ago.
theme.png (40.5 KB) - added by ramiy 10 years ago.
plugins.png (44.3 KB) - added by ramiy 10 years ago.
mobile-apps.png (40.3 KB) - added by ramiy 10 years ago.
forums.png (41.6 KB) - added by ramiy 10 years ago.
codex.png (42.6 KB) - added by ramiy 10 years ago.
make-wp.png (41.8 KB) - added by ramiy 10 years ago.
about.png (41.7 KB) - added by ramiy 10 years ago.
blog.png (85.4 KB) - added by ramiy 10 years ago.
plugins-login.png (10.8 KB) - added by ramiy 10 years ago.
forums-login.png (8.9 KB) - added by ramiy 10 years ago.

Download all attachments as: .zip

Change History (18)

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

@ramiy
10 years ago

#1 @samuelsidler
10 years ago

  • Keywords close 2nd-opinion added

I'd actually prefer not to do this. As more sites move to running WordPress-proper, login information should be on the top right of the page, in the admin bar.

Further, removing the subhead from the Blog was a design decision from a couple of years ago when they revamped it. I don't see any reason to change that.

#2 @netweb
10 years ago

  • Description modified (diff)
  • Keywords close 2nd-opinion removed
  • Summary changed from Standardize the user login form on all wp.org sites headlines to Standardize the user login form on all w.org sites headlines

We should do this, the admin bar isn't actually shown until you're logged in, a login link should included where it is currently missing

#3 @netweb
10 years ago

  • Description modified (diff)

#4 follow-up: @Otto42
10 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Yeah, no. You can't login everywhere because in most places, logging in there doesn't actually make any sense. The blog does not need to know your login, for example. You can't write on it, and you don't need the admin bar.

The system may be inconsistent, but it is *correct* for all locations. Consistency we can address as needed, on an individual basis. But unification is not on the table.

Not in this particular way, anyway. Long term, some other method must be devised for unified logins. I like the login.wordpress.org idea, personally. But making logins consistent in the header areas is a no go because we'd like to eliminate those, not add more.

Last edited 10 years ago by Otto42 (previous) (diff)

#5 @ramiy
10 years ago

Can we at least make the same UI in those pages where you can login? (Forum and Plugins)

#6 in reply to: ↑ 4 ; follow-up: @netweb
10 years ago

Replying to Otto42:

Yeah, no. You can't login everywhere because in most places, logging in there doesn't actually make any sense. The blog does not need to know your login, for example. You can't write on it, and you don't need the admin bar.

Right, makes sense to only included them when needed.

The system may be inconsistent, but it is *correct* for all locations. Consistency we can address as needed, on an individual basis. But unification is not on the table.

Right, we need one for themes then for adding theme favourites https://wordpress.org/themes/

#7 in reply to: ↑ 6 @coffee2code
10 years ago

Replying to netweb:

Right, we need one for themes then for adding theme favourites https://wordpress.org/themes/

#1050

Note: See TracTickets for help on using tickets.