Opened 6 years ago
Closed 5 years ago
#3609 closed enhancement (maybelater)
Improve design of "Upgrading PHP" support page
Reported by: | flixos90 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | General | Keywords: | 2nd-opinion ui-feedback ux-feedback servehappy |
Cc: |
Description
With #2996, we created a first iteration of the "Upgrading PHP" information page and got it up on wordpress.org. This version is in a good state regarding content, however it never received proper design - the content was simply put on a page.
We'd like to have an improved design for this page, and also allow the page to have a dynamic header, depending on a php_version
GET parameter that can be passed in the URL. If that parameter is passed and contains a PHP version that is considered outdated, a warning message can be shown and simulate better context, for example when WordPress core links to the page because of an outdated version detected. If no such parameter is passed, nothing will be shown, like it is at the moment.
There's an initial mockup for a design that @jaymanpandya created a while ago, which I'll upload as attachment to this ticket.
Here's the next steps we envision for this:
- Get feedback on the mockup from the design team, with emphasis on how this could be integrated with the general make.wordpress.org design.
- Get feedback from the meta team in terms of how freely we can work on the design, as it should probably still be coherent with the general design of make.wordpress.org support pages.
- Implement the dynamic page header using a
php_version
GET parameter as a simple shortcode, or alternatively Gutenberg block. - Implement the design agreed on for both the static page content and the dynamic header.
Attachments (1)
Change History (13)
#1
@
6 years ago
Notes on the above mockup (props @jaymanpandya for it):
- We'll need to iterate to get a design that fits into make.wordpress.org/support/.
- The sharing icons and the contextual bar at the top are not really necessary.
- The scroll-to-top button may be useful, but is also optional, if it requires too many technical changes.
This ticket was mentioned in Slack in #core-php by flixos90. View the logs.
6 years ago
This ticket was mentioned in Slack in #design by flixos90. View the logs.
6 years ago
#4
@
6 years ago
Drop by #docs, this seems like something that should be discussed alongside the HelpHub project which also includes a bit of designs for the support theme for standalone pages, and already has design team members on board.
This ticket was mentioned in Slack in #docs by clorith. View the logs.
6 years ago
This ticket was mentioned in Slack in #design by michelemiz. View the logs.
6 years ago
This ticket was mentioned in Slack in #docs by clorith. View the logs.
6 years ago
This ticket was mentioned in Slack in #meta by tellyworth. View the logs.
6 years ago
#10
@
6 years ago
@alexdenning and @jaymanpandya will be looking at the design and make a plan for the page.
This ticket was mentioned in Slack in #design by karmatosed. View the logs.
5 years ago
#12
@
5 years ago
- Resolution set to maybelater
- Status changed from new to closed
We've discussed in Design triage today and agreed to close this ticket as the Update PHP page had already been in HelpHub's design template.
initial "Upgrading PHP" page design mockup