WordPress.org

Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 7 months ago

#33766 closed task (blessed) (maybelater)

Updates: Update notice links to an uncompelling codex page

Reported by: ryan Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.3
Component: Upgrade/Install Keywords: update-flow needs-codex
Focuses: docs Cc:

Description

https://make.wordpress.org/flow/2015/08/18/upgradeinstall-update-from-an-update-notice-macnchrome/

The update notice for 4.3 links to https://codex.wordpress.org/Version_4.3. This is an uncompelling page that was out-of-date when 4.3 launched. This page does not encourage me to upgrade. After upgrade I'm presented with a nicely made about.php, but prior to upgrade our efforts are uncrafted.

Change History (13)

This ticket was mentioned in Slack in #core-flow by boren. View the logs.


4 years ago

#2 @johnbillion
4 years ago

  • Keywords needs-codex added
  • Milestone changed from Awaiting Review to 4.4

This is a nice idea. Let's make the codex page for each major release a compelling one, like the About screen.

This ticket was mentioned in Slack in #core by sergey. View the logs.


4 years ago

#4 @wonderboymusic
4 years ago

  • Type changed from enhancement to task (blessed)

#5 @wonderboymusic
4 years ago

  • Owner set to jorbin
  • Status changed from new to assigned

@jorbin help is figure out a plan here at some point

#6 follow-up: @jorbin
4 years ago

1) I think we should move this to a meta ticket to create a page on .org
2) I think that we should move the strings for the about page into it's own file that we can then include and essentially create a page on .org for each release that pulls in that releases about page strings.

Thoughts?

#7 in reply to: ↑ 6 @samuelsidler
4 years ago

Replying to jorbin:

1) I think we should move this to a meta ticket to create a page on .org
2) I think that we should move the strings for the about page into it's own file that we can then include and essentially create a page on .org for each release that pulls in that releases about page strings.

Thoughts?

Depending on where the page should live, it doesn't need to have a meta ticket at all. Just create it (like on the Codex). Eventually, I think this should live in helphub, as an "Introduction to WordPress 4.4" that details features and links off on how to use them. But helphub doesn't yet exist. Once that's done, we could easily create a corrected link in core.

Either way, I don't think we need this ticket.

This ticket was mentioned in Slack in #core by wonderboymusic. View the logs.


4 years ago

#9 @jorbin
4 years ago

  • Owner jorbin deleted

#10 @DrewAPicture
4 years ago

  • Focuses docs added
  • Milestone 4.4 deleted

I don't think this needs to be tied to 4.4, and it doesn't need to be a meta ticket either.

It's effectively a documentation/marketing project. In the near future, our best option is to try to improve the version article, since it's already the canonical source for in-depth information on the next release, and we're already linking to it.

If we want to look at something more polished and complex, that's fine, but that process should operate outside the scope of a release cycle, as basically all user-facing documentation already does.

#11 @SergeyBiryukov
4 years ago

  • Milestone set to WordPress.org

#12 @DrewAPicture
4 years ago

  • Milestone WordPress.org deleted
  • Resolution set to maybelater
  • Status changed from assigned to closed

Closing as maybelater. HelpHub seems like the best eventual home for something like this, but it's still in development. Let's revisit when we have somewhere for it to live.

Note: See TracTickets for help on using tickets.