Skip to content

fix(docs): update broken acknowledgment link in README#4766

Open
willswire wants to merge 1 commit intozarf-dev:mainfrom
willswire:patch-2
Open

fix(docs): update broken acknowledgment link in README#4766
willswire wants to merge 1 commit intozarf-dev:mainfrom
willswire:patch-2

Conversation

@willswire
Copy link
Copy Markdown
Contributor

Description

Updates the broken acknowledgement link in the README.

Related Issue

Fixes #

Relates to #

Checklist before merging

…chool

Signed-off-by: Will Walker <william@defenseunicorns.com>
@willswire willswire requested review from a team as code owners March 31, 2026 12:41
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 31, 2026

Deploy Preview for zarf-docs canceled.

Name Link
🔨 Latest commit 7d9e331
🔍 Latest deploy log https://app.netlify.com/projects/zarf-docs/deploys/69cbc0e0093e5000085aa488

## ⭐️ Special Thanks

> Early Zarf research and prototypes were developed jointly with [United States Naval Postgraduate School](https://nps.edu/) research you can read [here](https://calhoun.nps.edu/handle/10945/68688).
> Early Zarf research and prototypes were developed jointly with [United States Naval Postgraduate School](https://nps.edu/) research you can read [here](https://calhoun.nps.edu/entities/publication/d92c5122-6793-41df-b603-9c4faed1911f).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you clarify how this link is broken?

The original redirects me to your fixed link automatically - albeit I am seeing 500 errors for either periodically.

I'm still open to changing this if one of the references is more correct.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Reading around on the handle system - I'd wager the original URL is the most correct. It’s the repository’s persistent identifier, which is generally a better fit for long-term historical references than an application-specific page URL.

That is provided there is not some crucial error I am missing.

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

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants