-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Further byline changes in develop #1259
Comments
this is needed for rivard report |
In bylines in single posts, are we moving the date down to the main byline, or are we only displaying the date in the main byline if it's the Updated date? The current Largo behavior is to hide the published date with CSS: body.normal.single-post article.post > header .sep,
body.normal.page article.post > header .sep,
body.normal.single-post article.page > header .sep,
body.normal.page article.page > header .sep,
body.normal.single-post article.post > header .entry-date,
body.normal.page article.post > header .entry-date,
body.normal.single-post article.page > header .entry-date,
body.normal.page article.page > header .entry-date {
display: none;
} This is the published date's html: <time class="entry-date updated dtstamp pubdate" datetime="2016-06-02T00:26:14+00:00"><span class="published">Published </span>June 2, 2016</time> This is the updated date's html: <span class="last-modified">Updated June 2, 2016 at 11:29 pm</span> |
The current placement of the date doesn't really work and we should get rid of it and make this the new default. We should either include the published and/or updated date inline with the byline or we should put it on a new line below the byline (depending on how much space we have and how cramped it feels). |
also, that css is insane, let's definitely not do that |
The craziness of those styles is due to #1264
|
method in the Largo byline classgeneric conditional function to check if a post has been updated, by diffing published and updated timeslargo_time
published date if notis_single()
or if it hasn't been updatedThis extends #1126 somewhat
The text was updated successfully, but these errors were encountered: