WordPress.org

Make WordPress Core

Opened 13 years ago

Last modified 4 months ago

#6479 assigned enhancement

Encourage people to change default tagline

Reported by: markjaquith Owned by: markjaquith
Milestone: Future Release Priority: normal
Severity: trivial Version: 2.5
Component: Administration Keywords: has-patch
Focuses: Cc:

Description

A lot of people don't change the default tagline, especially if using a theme that doesn't display it. But it still displays in their feed. We should check to see if they still have the default tagline and if so, put a little contextual help in Settings - General that (nicely) encourages them to change it.

Props to Chris Silver Smith for bringing this issue up at WordCamp Dallas.

Attachments (2)

6479.patch (3.9 KB) - added by RyanMurphy 9 years ago.
6479.2.patch (3.2 KB) - added by tyxla 5 years ago.
Adding tagline field to installation main step.

Download all attachments as: .zip

Change History (29)

#1 @Denis-de-Bernardy
12 years ago

  • Component changed from General to UI
  • Owner anonymous deleted

#2 @Denis-de-Bernardy
11 years ago

  • Keywords needs-patch close added
  • Milestone changed from 2.9 to Future Release

suggesting wontfix

#3 @scohoust
11 years ago

+1 wontfix

Any problem this is causing to require users change it?

#4 @westi
11 years ago

  • Keywords close removed
  • Owner set to markjaquith
  • Status changed from new to assigned

This sounds like a good idea.

Maybe it should be promoted to an Install time configurable?

@RyanMurphy
9 years ago

#6 @RyanMurphy
9 years ago

  • Keywords has-patch added; needs-patch removed

Attached patch adds the tagline as an install time option. Patch also sets the default tagline to (i.e. none) (#18552).

#7 @SergeyBiryukov
9 years ago

Closed #20761 as a duplicate.

#9 @kovshenin
8 years ago

Two cents: In 6479.patch the new argument to wp_install should be the last in the list, otherwise you might break existing calls to wp_install. It should also be an optional argument. In schema.php the empty string should not be passed through the translation functions, in fact I don't think it should be an empty string at all. The default value for the tagline should remain as is -- the ticket says "encourage" people to change the default tagline, not "force" :)

#10 @ocean90
8 years ago

  • Keywords needs-patch added; has-patch removed

What kovshenin says.

#11 @SergeyBiryukov
8 years ago

The empty string came out of #18552. A more recent suggestion: ticket:18552:10.

#12 @DrewAPicture
8 years ago

  • Component changed from UI to Administration

#13 @chriscct7
6 years ago

  • Keywords ux-feedback added

I don't think this is just limited to the tagline. Many users never edit the time settings to their correct time. Maybe the UX team has an idea about how to improve the settings so users are encouraged to go through all settings

@tyxla
5 years ago

Adding tagline field to installation main step.

#14 @tyxla
5 years ago

  • Keywords has-patch added; needs-patch removed

The recent patch above follows the notes from @kovshenin.

#15 @hyperbrand
4 years ago

Why don't we direct users to the settings page after the installation process? Like other websites do after registering. Why should the dashboard be the starting point and not the settings page first?

#16 @karmatosed
4 years ago

To me, the dashboard makes sense to be the place if the information on it leads people to discovery as part of the NUX. This is actually something I think could be improved, that's outside the scope of this ticket though I would suggest. I think having encouragements like this make sense, even if we have a NUX flow that includes a prompt, people skip flows.

#17 @lukecavanagh
4 years ago

@karmatosed

So it might more sense for having reminders on the dashboard, if a user has not updated the site tagline from default or add a new page or post from default content.

#18 @karmatosed
4 years ago

@lukecavanagh if that's the end of the NUX flow then yes. I do note that whilst I don't know if planned I think the next release was focusing on NUX a little. This could be something to bring to that.

#19 @lukecavanagh
4 years ago

@karmatosed

Awesome then it would make total sense.

Last edited 4 years ago by lukecavanagh (previous) (diff)

#20 @SergeyBiryukov
4 years ago

#38316 was marked as a duplicate.

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


3 years ago

#22 @melchoyce
3 years ago

Taglines feel pretty anachronistic at this point, especially as WordPress is used for many different kinds of sites. I'd be a +1 for removing the default tagline, as suggested in #38316.

This ticket was mentioned in Slack in #design by boemedia. View the logs.


2 years ago

#24 @boemedia
2 years ago

We discussed this ticket in today's design triage. Summarizing, we can conclude 3 things:

  1. Not all themes display the tagline
  2. Not everyone changes the default tagline
  3. When people don't see the tagline in their theme, they don't realise it's still visible in feeds (and search results as well?)

I'm not even sure if a lot of website owners want a tagline in the first place, or have one at all. This could typically be a maybe later and then be forgotten.

I'd suggest making this a 2-step process while installing WP, but check if people see these fields while they use hosting services to install WP:

  1. ask if people want a tagline on their website (+ info: what is a tagline, where is it displayed, examples, why have one -> maybe link to some blog post on .org?). If checked yes, then:
  2. open conditional field where people can fill out the tagline.

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


11 months ago

#26 @karmatosed
11 months ago

  • Keywords ux-feedback removed

As this has ux-feedback, removing keyword.

#27 @khag7
4 months ago

  • Severity changed from normal to trivial

Any thoughts on changing the default tagline to an empty string?

Note: See TracTickets for help on using tickets.