Making WordPress.org

Opened 7 years ago

Closed 6 years ago

#872 closed enhancement (fixed)

DevHub: Add support for a blog

Reported by: coffee2code Owned by: atimmer
Milestone: Priority: normal
Component: Developer Hub Keywords: has-patch


Having a blog wasn't in the original design for developer.wordpress.org and hasn't really been requested until just recently.

Obviously, support for a blog is built into this WordPress thing we're using. However, the theme doesn't explicitly style for it (though it looks sane presently, with a few template tweaks) and the IA doesn't account for it.

Some things to address:

  • Templates and styling for blog posts, comments, blog archives, etc
  • Changes to the front page to display post(s) and link to the blog
  • Link to blog from other areas of the site (e.g. code ref, handbooks)?
  • Permalink structure (prepend with "/blog" or just do traditional date format?)
  • Existing templates will have to be assessed to ensure code ref-related templates and/or handling aren't applied to blog-related views unnecessarily
  • Since comments serve as "user contributed notes" for the code ref, likely some changes will need to be done to ensure comments and user notes are handled and rendered separate from one another
  • Breadcrumb structure (assuming default is unsatisfactory)

This can be a tracking ticket for the effort and related discussions.

Attachments (3)

872.diff (19.8 KB) - added by atimmer 7 years ago.
872.2.diff (21.8 KB) - added by atimmer 7 years ago.
872.3.diff (21.7 KB) - added by atimmer 7 years ago.

Download all attachments as: .zip

Change History (14)

#1 @coffee2code
7 years ago

In 1267:

developer.wordpress.org: Only use content-reference-archive.php and content-reference.php templates for posts of a parsed post type. See #872

This ticket was mentioned in Slack in #meta-devhub by coffee2code. View the logs.

7 years ago

This ticket was mentioned in Slack in #meta-devhub by siobhan. View the logs.

7 years ago

This ticket was mentioned in Slack in #meta-devhub by coffee2code. View the logs.

7 years ago

#5 @samuelsidler
7 years ago

Let's pick this back up. Here's some answers to questions in comment 0.

  • The "Blog" link should go in the header, on the far right (like make subsites). It should be on every page, including the home page, code reference, and handbooks.
  • No breadcrumb is necessary beyond a link back to the blog. (The current breadcrumbs are definitely not satisfactory.)
  • Permalink structure should be /blog/date/slug (I think; might be /blog/slug)

That leaves the following things to do:

  • Templates for posts, comments, archives
  • Walk through existing templates, ensuring they don't interfere with blog views
  • Comment changes as needed so they work on blog posts (note that we *don't* want trackbacks)

#6 @coffee2code
7 years ago

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

7 years ago

#7 @atimmer
7 years ago

  • Keywords has-patch added; needs-patch removed

872.diff does the following:

  • Add a content-post.php template to handle the post content.
  • Styles
    • Only show user contributed note styles on the parsed post types.
    • Add styles for the single post comments.
  • Shows default comment list and default comment form on the single post.
  • Add a nav_menu position.
  • Show this nav_menu in the top right on all pages.

7 years ago

#8 @atimmer
7 years ago

872.2.diff has the following changes on top of the previous patch:

  • Remove the Comments link from the single post.
  • Add a separator to the archives.
  • Show comment form if #respond is detected in the URL.

7 years ago

This ticket was mentioned in Slack in #meta-devhub by atimmer. View the logs.

7 years ago

This ticket was mentioned in Slack in #meta-devhub by atimmer. View the logs.

7 years ago

#11 @coffee2code
6 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 1675:

developer.wordpress.org: Add support for a blog.

  • Add post-specific template.
  • Add nav menu to house 'Blog' link.
  • Enable general, non-"User Contributed Notes" commenting.
  • Handle post comments distinctly from User Contributed Notes.
  • Comment styling and display scripting.

Fixes #872.
Props atimmer.

Note: See TracTickets for help on using tickets.