New and improved Docsy-based version of the website

[chalin]

• New and improved version of the TUF website, based on the Docsy Hugo theme, which will allow for easier maintenance and growth of the website.
• Initial work by LFX Term 2 TUF project mentee @Dindihub, who also completed the TUF Documentation Analysis for the CNCF techdocs team. Thank you Sandra, and well done! 🙌🏻 ✨
• Website migration completed by myself (@chalin)
• Contributes to [docsy] Post-LFX T2 mentorship site work #85
• All content from the existing website has a home in this new version of the website.
• Feedback by TUF approvers is welcome.

Preview: https://deploy-preview-105--theupdateframework.netlify.app/

[jku]

Looks nice.

On content/en/spec.md:

• is the idea that spec maintainers should update this page too when they make a specification release? This feels like unnecessary process. I would suggest replacing the list with:
  • Large button to current TUF specification
  • A bit of additional info like: "Specification is maintained at https://github.com/theupdateframework/specification/, full list of releases is available in ..."
• Currently the link for list of releases /specification/list/ is broken: should be /specification/

[jku]

Also header for the "spec" tab seems wrong -- it's got a large image that looks a bit placeholdery. Or is this intended?

Compare partial screenshot from docs and spec tab:

[chalin]

• Approved by @JustinCappos et al.: see Slack #tuf thread, and a Slack message to @lukpueh and myself. Merging now.
• @jku - thanks for your comments. I'll open issue(s) to track those and address them separately.
• All: here's a link to the current version of the website. We can keep this around for reference for a little while, for those times where we wonder "how was it before" :) -- https://pre-lfx-2024--theupdateframework.netlify.app

[JustinCappos]

Yes, this also looks great. I approve!

…

On Sat, Oct 12, 2024 at 1:10 PM Patrice Chalin ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In netlify.toml <#105 (comment)> : > [[headers]] for = "/*" [headers.values] - Content-Security-Policy = "default-src 'self' code.jquery.com fonts.googleapis.com fonts.gstatic.com use.fontawesome.com app.netlify.com netlify-cdp-loader.netlify.app youtube.com; frame-src youtube.com www.youtube.com" + Content-Security-Policy = "default-src 'self' code.jquery.com fonts.googleapis.com fonts.gstatic.com cse.google.com www.google.com use.fontawesome.com app.netlify.com netlify-cdp-loader.netlify.app youtube.com; frame-src youtube.com www.youtube.com" @JustinCappos <https://github.com/JustinCappos> et al.: I wanted to highlight this addition to the CSP, i.e., two google.com sites, which I added while experimenting with custom Google search for the website (#91 <#91>). Please confirm that you are ok with this addition, otherwise I'll roll it back. — Reply to this email directly, view it on GitHub <#105 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGROD6QRJRUCDP4RMK4QFDZ3FJXFAVCNFSM6AAAAABPTHRYFSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGNRUGA2TGNBUGM> . You are receiving this because you were mentioned.Message ID: <theupdateframework/theupdateframework.io/pull/105/review/2364053443@ github.com>

[chalin]

@jku - I created the following issue to track your comments:

• Spec page rework suggestions #107