Headers content

[ltagliaferri]

For discussion — I wanted to know what we think about the current headers @jamonation @erikaheidi

For example, on the tutorial about how to sign an SBOM, they look like this in markdown:

---
title: "How to Sign an SBOM with Cosign"
type: "article"
description: "Signing software bills of materials with Cosign"
lead: "Use Cosign to sign a software bill of materials"
date: 2022-13-07T15:22:20+01:00
lastmod: 2022-13-07T15:22:20+01:00
draft: false
images: []
menu:
  docs:
    parent: "sigstore"
weight: 620
toc: true
---

On the site it looks like this:

We don't have the lead or description coming into the blog post cards:

But the description I believe will be indexed by search engines.

We also don't have the date coming into the front end.

In terms of authors, we don't have authors either in the headers or on the frontend. And we may want to have that as well as author landing pages. But authorship may be less important for straight documentation.

What are your thoughts?

[erikaheidi]

I agree that the article page and the list page definitely can use a bit more metadata. Author info can be a bit more challenging because we'd need to pull the data from somewhere (or, just use a generic front mater field for author string and display that?).

I think it's gonna be easy to add the other info that's already on the front mater thou. Let me look into that.

[ltagliaferri]

We could start with a generic author string and no author landing page. I think it would be nice long term to collect authors' posts together, there is precedent with the Chainguard blog doing this.

This was how Katy added authors on Sourcegraph Learn in case this is worth reviewing later on: https://github.com/sourcegraph/learn/pull/321/files

[ltagliaferri]

I added contributors based on how it looks in the blog in #24