spinnaker/spinnaker.io

spinnaker.io website content

Hosted by CD Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

spinnaker/spinnaker.io has 20+ stars and 150+ forks on GitHub, is written in HTML, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 23 minutes ago
Added to GitGenius on October 15th, 2026
Created on June 3rd, 2020
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 151
Total Stargazers: 22 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 hours
Mean response time: 9.3 days
90th percentile: 19.6 days
Tracked items: 4

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (8)
  • to-be-closed (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Spinnaker.io is a documentation and community website built with Hugo and the Docsy theme.

The project serves as the central hub for Spinnaker documentation and community resources, hosting Markdown-based documentation files that are rendered into a static website. It uses Hugo as the site generator with Docsy as its theme, and leverages Hugo Modules to automatically pull in theme dependencies without requiring manual submodule setup. The build process involves Node.js for asset transforms like PostCSS and autoprefixer, alongside Go to resolve Hugo Module dependencies.

Developers contributing to or maintaining this documentation site need Node.js v24 or later and Go 1.25 or later. The project includes a contribution workflow where branches are created from master, pull requests trigger Netlify preview builds for verification, and merges to master automatically deploy to the live site. The README points to additional guidance in docs/website-contributing.md for content authoring, shortcodes, homepage configuration, and theme customization. Recent work has focused on reorganizing installation documentation into clearer Install and Configure categories.

The project maintains active engagement with documentation updates and structural improvements to the content organization. Contribution guidelines are clearly documented with an automated preview and deployment pipeline in place.