-
Notifications
You must be signed in to change notification settings - Fork 196
DISCUSSION: Compact List Post #160
Comments
And when there's no feature image, just keep it as it is right now? I generally don't include feature images on my posts. Related: On my site, on the list post I've increased the number of paragraphs in the summary. And I was thinking of making this value a config param. Additionally, I show the full post if the character length of the content is under 500 (with no "read more"). I was thinking of making a PR for this (and am not offended if it's rejected). And less related: If the post has no Tags, I hide that element rather than show the icon with "None". It's just noise at that point. I was also thinking of making a PR for this. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm working on my website using this theme and found that mobile display is not optimal. Keeping the post meta information next to the title and description is not a good idea as it reduces the available space for both pieces of information. I think it better to show the post meta information below the post title and description. Also for wide screens it is better to limit the width for the post than placing information next to the featured image. |
Why? it always bothers me if I have a widescreen monitor and a website only uses one third of available screen space. |
#252 might be the better solution for this, but would like some thoughts. |
After discussing this in the PR I did some mockups how this could be solved differently or how the proposed solution could be augmented.
On Widescreens and when the image has a more or less "normal" aspect ratio the layout could look like this
When using wide images (e.g. panoramas) it could possibly use up the whole horizontal space like this:
And on mobile it could look like this
Note the visual elements are not final it's just supposed to visualize the idea of the layout of the elements.
Originally posted by @twatzl in #109 (comment)
The text was updated successfully, but these errors were encountered: