Skip to content

Adding doc on the new Requests tab in the Console#3030

Merged
SharpRake merged 2 commits into
chainguard-dev:mainfrom
SharpRake:reqs-tab
Mar 2, 2026
Merged

Adding doc on the new Requests tab in the Console#3030
SharpRake merged 2 commits into
chainguard-dev:mainfrom
SharpRake:reqs-tab

Conversation

@SharpRake
Copy link
Copy Markdown
Collaborator

@SharpRake SharpRake commented Feb 27, 2026

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?

  • The new article renders correctly at its expected path under the chainguard-images/features/ section.
  • The page accurately reflects the current state of the Requests section in the Console, including the three tabs (My requests, Active builds, Community requests), the required and optional form fields, and the status values.
  • The beta disclaimer is clearly visible.
  • The sidebar ordering is correct after the weight adjustment to unique-tags/index.md.
  • All internal links (e.g., to verified orgs, Catalog Pricing) resolve correctly.

How should this PR be tested?

  1. preview link
  2. Cross-reference the article against the live Requests section of the Chainguard Console to verify accuracy of UI descriptions (tabs, columns, form fields, status values).
  3. Click through to the article and verify it renders without errors.

Signed-off-by: Mark Drake <mark@chainguard.dev>
@SharpRake SharpRake requested a review from a team as a code owner February 27, 2026 20:54
@netlify
Copy link
Copy Markdown

netlify Bot commented Feb 27, 2026

Deploy Preview for ornate-narwhal-088216 ready!

Name Link
🔨 Latest commit 3352f1e
🔍 Latest deploy log https://app.netlify.com/projects/ornate-narwhal-088216/deploys/69a5db0a8f96bd00083e4689
😎 Deploy Preview https://deploy-preview-3030--ornate-narwhal-088216.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.

Copy link
Copy Markdown
Collaborator

@matthewhelmke matthewhelmke left a comment

Choose a reason for hiding this comment

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

I left a couple of non-blocking comments. This looks great! Thank you!!

Approved.

Comment thread content/chainguard/chainguard-images/features/request-resources/index.md Outdated
Comment thread content/chainguard/chainguard-images/features/request-resources/index.md Outdated
Comment thread content/chainguard/chainguard-images/features/request-resources/index.md Outdated
Comment thread content/chainguard/chainguard-images/features/request-resources/index.md Outdated
Comment thread content/chainguard/chainguard-images/features/request-resources/index.md Outdated
Comment thread content/chainguard/chainguard-images/features/request-resources/index.md Outdated
Signed-off-by: Mark Drake <mark@chainguard.dev>
@SharpRake SharpRake merged commit a9b9555 into chainguard-dev:main Mar 2, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants