Move PipeCD docs hosting to Netlify

[rahulshendre]

Currently the PipeCD docs site is managed through the existing infrastructure setup.

Since the docs site is static, maintaining the current setup may add unnecessary infrastructure and maintenance overhead. We should explore migrating docs hosting to a simpler static hosting platform such as Netlify

Things that would need to be handled:

• current deployment workflow
• versioned docs support
• redirects/routing
• DNS/config updates

Feel free to share suggestions, concerns, or alternative approaches before implementation begins.

Note: this would likely be an end-to-end ownership task, so please take it up only if you are serious about handling the migration properly.

[rahulshendre]

@khanhtc1202 PTAL and please verify if the current issue description assumptions look correct before we start working on this

[ObaidAbdullah16]

what we’re optimizing for?
From the repo it looks like the site is currently built into a container + Helm chart (and /docs/ redirects to the latest version). If we move to Netlify, do we want to keep the exact same URL/versioning behavior (including the /docs/ → latest redirect) and also add PR preview deploys for doc changes? Knowing that upfront would make the migration plan much clearer.

[ObaidAbdullah16]

If helpful, we could also add a short list of expected outcomes for this migration (e.g., reduce maintenance, keep URL/version behavior, add PR previews) so it’s clear what “done” looks like.

[harshitghagre]

Hey @rahulshendre @khanhtc1202, I’d like to work on this issue. I have used Hugo and Netlify before and have also contributed to the docs, so I know the setup well. My plan is to add a netlify.toml file in the docs/ folder for builds and PR deploy previews, make sure the versioned docs work the same as they do now, and add redirects so no links break. I will test everything on my fork first before any DNS changes are made. Please assign this issue to me so I can start working on it.

[yashisrani]

i was looking into our current docs setup & wanted to propose moving pipeCD docs hosting from GKE to netlify

right now, the docs are fully static, but we are still maintaining custom go server, docker images, helm charts, ingress, certs, etc. netlify could simplify a lot pf this maintenance overhead.

hugo build process would stay same, instead of building and deploying container, we'd just publish generated public/ directory to netlify.

versioned docs should contiue to work fine since they already exist in the hugo output. we'd only need to replace current /docs/ redirect logic with simple _redirects file.

my suggested rollout

• set up netlify alongside current deployment
• test redirects/versioned docs on preview deployments
• switch DNS after verification
• monitor for a few day
• then remove unused GKE/docs infra

this would also give us automatic PR preview deployments, which should make docs reviews much easier.

i'm happy to handle the migration end to end if everyone agrees with my direction. @rahulshendre