Show a date about gistlog

[mattstauffer]

I would lean towards "show the creation date and then in a later PR, allow for overriding publish date in YAML front matter."

@adamwathan, thoughts?

Note that we are sort of showing dates here, but I definitely understand the desire to show it up top.

[adamwathan]

Yeah makes sense to me, agreed that a real date makes more sense than a relative date for a blog post.

Only thing I would say is to use gistlog.yml rather than the front matter. Solves the problem of looking ugly on on gist.github.com and is more consistent with how we are doing other stuff.

Could even just use a published_on key to replace our current published key, would allow for queueing up future posts too.

[mattstauffer]

Oops, yah, gistlog.yml is our frontmatter in my head. Thanks.

Interesting about published_on deprecating published. That's a great idea.

[zQueal]

Could even just use a published_on key to replace our current published key, would allow for queueing up future posts too.

I'm thinking of moving my blog posts to gistlog, but I want to be able to recreate the date they were actually first published. If I move them to gistlog, then the "published on date" is the day I migrate them, not when they were actually first published. Is that what you're discussing here, @adamwathan?

[JacobBennett]

@adamwathan @mattstauffer @zQueal @raine with the new GistConfig class in PR #68 we should be able to make this a reality. One oversight that I didn't think of until just now was the fact that I didn't parse the published_on value in the gistlog.yml as a Carbon object. Would be a good idea if it was going to be overriding the published property.

[bakerkretzmar]

Closing as this was implemented in #127 and then removed again here as part of the design overhaul in #130 several months later.

For reference, right now we're showing a relative "Created at" and "Updated at" time at the bottom of every Gist page:

and a relative "Posted" time on the Gists landing page:

As far as I can tell, we are retrieving and parsing published_on from gistlog.yml but not using it anywhere. If we decide again that having a prominent, configurable "Published on" date is a priority, it'll be straightforward to add it again à la #127.