Opened 3 months ago

Last modified 5 weeks ago

#22774 needs_information enhancement

Figure out how much of each blog post to display on the index (front) page

Reported by: arma Owned by: hiro
Priority: Medium Milestone:
Component: Webpages/Blog Version:
Severity: Normal Keywords: ux-team
Cc: linda Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

On the old blog, we put the entirety of each blog post on the index pages. It was a conscious design choice -- it meant fewer posts got listed per index page, but you could actually read the posts by reading the index pages.

Now we have some subset of each post, and sometimes it's just a few lines, and sometimes it's "just" the first 35 bullet points of the changelog we're announcing.

We should figure out if we want to put all of each post, or just a teaser. And if we choose teaser, we should build code or policy that makes us more uniform in how much teaser we pick.

I'm including keyword ux-team because this is another one where they'd be helpful.

Child Tickets

Change History (3)

comment:1 Changed 3 months ago by arma

I think we should pick "put the whole post there", since that way people can read the posts by reading the blog, without having to click on every blog post individually.

But we might want to find a way to fit more than 1-ish of them on the page -- the font size and whitespace and stuff makes this harder than it needs to be. Maybe that part will get better when we address the tickets around use of whitespace?

comment:2 Changed 5 weeks ago by hiro

Cc: linda added
Status: newneeds_information

There is a problem with the way drupal breaks a html post vs a normal-text post. In normal text posts it's possible to just display a teaser. With html posts it doesn't break tags so it displays a number of words/chars that depends on the current opened tag.

I haven't find a way to fix this. Not sure what the best approach could be.

Maybe the ux team could help w/ this.

comment:3 Changed 5 weeks ago by linda

Provided that the blog posts are short enough to fit 2-3 on a page, I don't see a problem with displaying all of the post in the page to save a click. This "short enough" part is the tricky part. We can definitely try to work with the whitespace issue.

As for the implementation weirdness with showing snippets, I don't know of a technical resolution (i.e. how to make drupal cooperate), but I think that it would be good to be consistent between how we show posts. If we show a snippet of some but all of another, it may seem like we're trying to emphasize certain posts over another, which I don't think is the intent (unless all posts with html are more important than text).

Note: See TracTickets for help on using tickets.