Update Sunlight log information #2019
Conversation
This removes the now-obsolete CT shard info from the ct-logs page. Since Sunlight hosts its own log info, we can just link out to each landing page.
These logs are going to be the more relevant ones soon.
content/en/docs/ct-logs.html
Outdated
| Information about the various lifecycle states that a CT log progresses through can be found <a href="https://googlechrome.github.io/CertificateTransparency/log_states.html">here</a>. | ||
| </p> | ||
|
|
||
| <h2>Sunlight</h2> |
There was a problem hiding this comment.
By virtue of making this an H2, the "Production" and "Testing" H3s are now sub-sections of "Sunlight", rather than being subsections of "CT Logs". Either this should be an H3, or the "CT Logs" section should be moved below this and maybe renamed to "RFC 6962 Logs".
There was a problem hiding this comment.
Switched to H3, which matches where I'd intended to put it hierarchically.
content/en/docs/ct-logs.html
Outdated
| </p> | ||
| <p>Sycamore and Willow are our new production CT logs, accepting certificates from trusted CAs.</p> | ||
| <ul> | ||
| <li>Sycamore: <a href="https://log.sycamore.ct.letsencrypt.org/">log.sycamore.ct.letsencrypt.org</a></li> |
There was a problem hiding this comment.
On the one hand, I love that we don't need to template all of this information in anymore. On the other hand, as long as we have the RFC 6962 logs listed as well, these ones simply disappear in the visual noise. I'm not sure what the right fix is -- at the very least, making their names bold like the names of the Oak shards are. Maybe adding H3 subheadings for "Production" and "Testing", just like the RFC 6962 logs have.
There was a problem hiding this comment.
I've bolded the log names. It does make them stand out more for sure.
I didn't want to touch the RFC6962 logs in this PR, but I intend to update those sections with deprecation notices shortly. I think a fair amount of this page needs a redesign / rework, and I didn't want to hold this PR any longer while I work on that. My priority for today is making sure the obsolete shard information is removed.
There was a problem hiding this comment.
In particular, I want to steal the collapsing design of the /certificates/ page for decommissioned shards, probably turn this into more markdown, and potentially look at automatically fetching/updating the JSON metadata to populate info for the Sunlight shards so it's still on the page for historical reference.
But that's enough work that I don't have time for today, and at least two people have noted the existing stale data here already :)
This removes the now-obsolete CT shard info from the ct-logs page. Since
Sunlight hosts its own log info, we can just link out to each landing page.