Skip to content

nonspec: new website build strategy#1329

Closed
zachariahcox wants to merge 0 commit intoslsa-framework:mainfrom
zachariahcox:users/zc/refactor-main
Closed

nonspec: new website build strategy#1329
zachariahcox wants to merge 0 commit intoslsa-framework:mainfrom
zachariahcox:users/zc/refactor-main

Conversation

@zachariahcox
Copy link
Collaborator

@zachariahcox zachariahcox commented Apr 20, 2025

This PR focuses on what the flow would look like after we have a late branch model.

Depends on #1328 where all the devcontiner and late-branching pieces will need to be settled first.

This PR is almost entirely file moves.
It demonstrates what a world would look like if there was only one copy of the spec in a branch and how a www folder + deployment process could be created to flatten versions of the spec from other branches.

Ultimately, it would be nice to store those spec versions in releases and not rely on git shenanigans.
We'd need to settle on a release strategy for that, which is Its Own Discussion 😂

Critical file changes include:

@netlify
Copy link

netlify bot commented Apr 20, 2025

Deploy Preview for slsa failed.

Name Link
🔨 Latest commit ef10969
🔍 Latest deploy log https://app.netlify.com/sites/slsa/deploys/68050350503a120008314ec4

@zachariahcox zachariahcox requested a review from Copilot April 20, 2025 14:34
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR demonstrates a new website build strategy by reorganizing the repository structure and introducing a GitHub Actions workflow to automate the publishing of the SLSA specification as a release.

  • Adds a new workflow (.github/workflows/publish-spec.yml) for release automation that creates a zipped archive of the spec, generates a build provenance attestation, and attaches both to the release.
  • Introduces file moves and minor adjustments to support the single-copy spec and deployment process.
Files not reviewed (1)
  • .devcontainer/devcontainer.json: Language not supported

@lehors
Copy link
Member

lehors commented Apr 22, 2025

Thanks for doing this. I like it. Just some thoughts that came up as I went through this a first time:

What's the reason to change from docs/ to www/ ? It's no big deal but this creating a lot of noise in this PR.

We'll also need to document what steps need to be taken when releasing a new spec (something that's missing today!) One will still need to update files like _data/versions.yml _data/nav/* _redirects among others. Experience with the release of v1.1 just showed that there are quite few bits and pieces all over the place that need updating. We shouldn't need to find those the hard way every time.

We should aim to eventually have combine-versions.sh pull in the list of specs to deploy from one of the config files - I think _data/versions.yml.

Just to be clear: I'm not asking for any of the above to be part of this PR! :-)

@lehors lehors closed this Feb 16, 2026
@lehors lehors force-pushed the users/zc/refactor-main branch from ef10969 to 8a825b8 Compare February 16, 2026 14:22
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Issue triage Feb 16, 2026
@netlify
Copy link

netlify bot commented Feb 16, 2026

Deploy Preview for slsa ready!

Name Link
🔨 Latest commit 8a825b8
🔍 Latest deploy log https://app.netlify.com/projects/slsa/deploys/6993282969cb6c0008c9d933
😎 Deploy Preview https://deploy-preview-1329--slsa.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@lehors
Copy link
Member

lehors commented Feb 16, 2026

Sorry, I tried to update this PR and evidently messed up something. I'll create a new one.

@lehors
Copy link
Member

lehors commented Feb 16, 2026

PR #1578 has now been created and includes all the commits that used to be part of this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants