Redesign: Blog Page: design

[hdrdavies]

A lot of web-agency blogs present their blogs in squares and allow for click throughs:

Blueegg

Steve-edge

Jump

Jump is my favourite - I think lots of images can be quite busy, and we might not want to spend time trying to find images for each respective blog post!

[iteles]

Agree, especially for the first iteration let's keep this simple.
Relatively low priority as we don't have content yet - keen to get the other pages up first.

[Cleop]

Time estimate based on hard coding solution for time being and simply implementing the design.

Not creating a new issue for this as this one already existed. @harrygfox over to you for designs. Awaiting copy from #5.

• Create 3 columns for copy
• Add placeholder text for the first para of posts (awaiting copy from @markwilliamfirth Blog: Blog Page: Copy / write first blog article #5 )
• Grey background with dwyl teal 'Blog' title
• Load More button

Note: organised by columns not rows:

@harrygfox - as the content appears to be organised in columns not rows, how will this work with chronology? The design makes me envisage the system below (with columns hiding some content which would reveal with the 'load more' button). Is this what you intended?

COLUMN A	COLUMN B	COLUMN C
Blog 18 (most recent post)	12	6
17 (2nd most recent post)	11	5
16	10	4
-------	LOAD MORE BUTTON	-------
15	9	3
14	8	2
13	7	Blog 1 (oldest post)

[harrygfox]

@Cleop it's displayed by columns, but is still meant to be ordered in rows. I think it would be confusing / frustrating for users to see posts of varying ages when they scan across the page, and more so to have to click the load button to find only the fourth most recent article

[Cleop]

@harrygfox - good, that's what I was thinking for users being confused, thanks for clarifying. It will be harder to inject the content into columns if chronologically it's running horizontally as rows but we can give it a shot.

[Cleop]

@harrygfox - just to make sure my understanding is right:

• should the titles of a row of posts be inline with one another vertically?
• How much copy should each blog post show, is it capped at a certain number of characters (because this page is only showing say the first para right? you click on the title to see the full blog post?)?
• Are the names of the authors links? If so, where does clicking on them take you?

[harrygfox]

@Cleop
Everything is determined by content.

• Yes everything is vertically aligned in each column
• I hadn't imagined any programmatic limit to the blurb beneath the title, but rather the post creator would be able to determine what does into the blurb hence the staggered display
• Names could be links if we had somewhere for them to go. One option right now would be to go to the highlighted view of that author on the team page. Another would be to show only the posts by that author. Right now though, not links

[Cleop]

Thanks @harrygfox 👍

[Cleop]

The designs have dwyl with a capital D, but I think it's either DWYL or dwyl but not half half. Generally I thought the consensus was all lowercase. Does this look weird:

[harrygfox]

@Cleop only if you over-think it 🍷

[ghost]

It's always dwyl regardless of where it is in a sentence

This is still under review dwyl/hq#249

[ghost]

Nice! 👍