Adding doc on the new Requests tab in the Console#3030
Merged
Conversation
Signed-off-by: Mark Drake <mark@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
matthewhelmke
approved these changes
Mar 2, 2026
Collaborator
matthewhelmke
left a comment
There was a problem hiding this comment.
I left a couple of non-blocking comments. This looks great! Thank you!!
Approved.
s-stumbo
reviewed
Mar 2, 2026
s-stumbo
reviewed
Mar 2, 2026
s-stumbo
reviewed
Mar 2, 2026
s-stumbo
reviewed
Mar 2, 2026
s-stumbo
reviewed
Mar 2, 2026
s-stumbo
reviewed
Mar 2, 2026
Signed-off-by: Mark Drake <mark@chainguard.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of change
Documentation
This PR adds a new article documenting the Requests section of the Chainguard Console, which allows customers to submit and track requests for new Chainguard resources (container images, packages, and Helm charts). It also adjusts the sidebar weight of the Unique Tags article to accommodate the new page in the navigation order.
What should this PR do?
resolves https://github.com/chainguard-dev/internal/issues/5685
Why are we making this change?
The Chainguard Console recently launched a new Requests section (currently in beta) that gives customers a self-service way to request resources Chainguard doesn't yet offer. Without documentation, customers may not know this feature exists or understand how to use it effectively — including its prerequisites (verified organization membership), the request submission workflow, upvoting mechanics, and the limitations on what Chainguard can build.
What are the acceptance criteria?
How should this PR be tested?