#325 closed defect (bug) (fixed)
Code reference archive pages require styling
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Developer Hub | Keywords: | has-patch |
| Cc: |
Change History (12)
#3
@
12 years ago
- Resolution set to fixed
- Status changed from assigned to closed
Fixed. Specific changes to archive pages require their own tickets.
This ticket was mentioned in PR #437 on WordPress/wporg-mu-plugins by @adamwood.
2 years ago
#4
- Keywords has-patch added
jasmussen commented on PR #437:
2 years ago
#5
Looks good at a glance. The only thing we might tweak is the line-height which can get a bit compact on mobile, but we can ship this as is and revisit if need be.
@adamwood commented on PR #437:
2 years ago
#6
This ticket was mentioned in PR #438 on WordPress/wporg-mu-plugins by @adamwood.
2 years ago
#7
Reverts WordPress/wporg-mu-plugins#437 until we know how to handle these changes on the Documentation site
This ticket was mentioned in PR #439 on WordPress/wporg-mu-plugins by @adamwood.
2 years ago
#8
Reverts WordPress/wporg-mu-plugins#438
Solution for Documentation site TBD
@dufresnesteven commented on PR #437:
2 years ago
#9
We can make documentation look the same as the developer handbook pages since they are essentially the same thing.
Move the breadcrumb down into the content, add the title to the subnav and change the color. I would just ping #docs with that change to make sure everyone is aware.
@adamwood commented on PR #437:
2 years ago
#10
@adamwood commented on PR #437:
2 years ago
#11
The Docs update is now underway, and actually removes the breadcrumbs https://github.com/WordPress/wporg-documentation-2022/pull/67
jasmussen commented on PR #437:
2 years ago
#12
I have to offer an apology there, the breadcrumbs are meant to be there and I corrected this in the mockups.


pull request submitted w/ exception of 'used by' line. Will discuss functional requirements and then update styles