Make WordPress Core

Opened 14 years ago

Closed 11 years ago

#14099 closed enhancement (wontfix)

Links to Codex from within WordPress should be standardised

Reported by: johnbillion's profile johnbillion Owned by:
Milestone: Priority: normal
Severity: minor Version: 3.0
Component: Text Changes Keywords:
Focuses: Cc:

Description

There are various links to pages on Codex throughout the admin screens. Some of them say things like "More information", some say "see bla bla on Codex", some aren't clear where they link to.

It would be nice if:

  1. All Codex links were styled in a way that makes them different from other links, for example if they had a different foreground/background colour or if they had a Codex icon prepended/appended to the link.
  2. All Codex links followed similar terminology (string change).

Ideas/suggestions?

Change History (13)

#2 @nacin
13 years ago

  • Keywords ux-feedback added
  • Milestone changed from Awaiting Review to Future Release

#3 @johnbillion
13 years ago

I wonder whether this could make it into 3.2 as part of the UI refresh? If we gave every Codex link a class name (eg. 'codex') and prepended or appended a nice little Codex icon I think it would make Codex links much clearer.

Thoughts?

#4 follow-up: @jane
12 years ago

I'm usually all in favor of standardization, but in this case I'm not completely sold. What problem does it solve?

#5 @jane
12 years ago

  • Keywords ux-feedback removed

#6 in reply to: ↑ 4 @DrewAPicture
12 years ago

Replying to jane:

I'm usually all in favor of standardization, but in this case I'm not completely sold. What problem does it solve?

From a standardization standpoint, I think stylizing or adding a icons next to Codex links would promote more use of the Codex and result in easier first-stage troubleshooting. "Having an issue? Often times the information you seek can be found via the Codex links in the Dashboard." <- Or something.

A lot of newer users don't fully realize that A) the Codex exists and B) That there's a wealth of helpful information to be had there.

By standardizing the way Codex links are styled, we would promote recognition that there is immediate help to be had by clicking them. My 2¢.

Last edited 12 years ago by DrewAPicture (previous) (diff)

#7 @DrewAPicture
12 years ago

  • Cc xoodrew@… added

#8 follow-up: @jane
12 years ago

Given that the most frequent feedback we get is that the Codex is confusing, I don't know that we should clutter the admin ui with UI elements meant to push people toward the Codex. The push should be toward publishing, not researching functions. The links are just there as a resource. Even if the Codex was the most brilliant encyclopedia of all knowledge in the world, I wouldn't want to put distracting pushes toward it in the admin.

#9 in reply to: ↑ 8 @DrewAPicture
12 years ago

Replying to jane:

Given that the most frequent feedback we get is that the Codex is confusing, I don't know that we should clutter the admin ui with UI elements meant to push people toward the Codex. The push should be toward publishing, not researching functions. The links are just there as a resource. Even if the Codex was the most brilliant encyclopedia of all knowledge in the world, I wouldn't want to put distracting pushes toward it in the admin.

I see your point, but I still agree with johnbillion on finding a way to standardize the links. Can you think of a way to do it sans-icon that wouldn't be distracting?

Version 0, edited 12 years ago by DrewAPicture (next)

#10 @jane
12 years ago

Any link we deem worth including in the admin has equal importance. Codex links don't need a special class.

#11 @johnbillion
12 years ago

I think the reason I originally brought this up was that there are links in various places in the UI and there's no distinction between ones which link to other screens and ones which link to an external URL. There aren't many, but I thought it might make things clearer if external links were visually distinct and/or the link text made it clear what it linked to.

#12 @SergeyBiryukov
11 years ago

  • Component changed from UI to Text Changes

#13 @johnbillion
11 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Wontfix based on Jane's comments.

Note: See TracTickets for help on using tickets.