• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)

this will cross link with cloud.google.com/documentation

Currently blank

• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)

Add in addition stuff around slsa, Nist, sigstore, sboms.

In the right sidebar when viewing the github repo.. add a description and a link to the project website

Hi folks, do you plan to translate the website in other languages (french for example) ?

Based on the best practices site, is there a section where we can add in reference implementation of the architecture of what the best practices would look like in software supply chain security. We have been working on an OpenSSF project known as FRSCA that would be great to demo to the community and add as an implementation that people can explore. FRSCA utilizes Tekton and follows the CNCF Secure Software Factory Ref Arch.

Also needs clarity on how to present this type of info -- currently it's a subsection under Learn and also Resources.

This would cover topic related to corporate governance, e.g., augmenting supply chain related topics as described here

We had a boilerplate content template in the Learn sections that included a header and a reference to ‘associated DORA capabilities’. Where this header has been retained, we should verify that it is relevant to the content of the sub-chapter and, if so, ensure that any references to DORA have been appropriately reconciled in the narrative.

• #4 (comment)
• #4 (comment)
• #4 (comment)

The left sidebar jiggles about when you reduce the window size. Video attached.

Probably under resources section -- for content published by vendors or via blogs that won't be hosted directly on CDF site, can we provide a curated and categorized table contents to help people find examples that could be relevant to their circumstances

want to get the bulk of the latest content migration merged so we can better collaborate on improvements, making an issue so we don't lose track of any IP feedback:

• #4 (comment)
• #4 (comment)
• #4 (comment)
• #4 (comment)

Descriptions:

The goals, translate te web site to Spanish

Work Proposal:

1. Fork the repository.
2. Set up the project locally (Docker).
3. Switch to the i10n branch and navigate to the es folder.
4. Make updates or modifications in the "es” folder and validate how this view.
5. Create a pull request (PR) to update the i10n branch or Create pull request using GitLocalize to track the progress of translation process.

Questions:

What do you think about step 5 and the work proposal in general?

Relate issues

• #27

Continuous Integration and Continuous Testing were recently noted but all should be reviewed.

Our Hugo installation is quite stale, so we should look at upgrading the site to be compatible with a later version.

Can / should a section be added to the continuous deployment best practices page for progressive delivery using feature flags.

Projects like OpenFeature have lots of expertise that we can lean on here.