Many of you folks probably do not know me - my name is Ketan Umare, and I am the original author of Flyte. Since open sourcing flyte, I have been part of this community and I am grateful to all the amazing folks who have help make Flyte an indespensible part of their Platforms. Today Flyte is used by some of the largest companies in the world to build and deliver their compound AI products. Recently, we decided to make a change, move Flyte docs to the same platform where we host union docs. Below is my rationale, Flyte is, and will always remain, an open-source project under the Apache 2.0 license and a Linux Foundation product. Our commitment to openness and independence remains unchanged. However, maintaining separate documentation sites has become an increasing burden on our small team at Union.ai. Today, Flyte’s documentation is primarily maintained by our team, rather than through broad community contributions. Managing the infrastructure for docs, in addition to maintaining Flyte itself, introduces unnecessary overhead. (Flyte docs are not simply python docs, there are golang, protobuf, python, java, terraform etc) To improve efficiency and focus on making Flyte better, we are moving our documentation to a unified platform at union.ai/docs. This decision is driven by practicality, not commercialization. Why the Move? • We are adopting Hugo, which offers *faster builds, versioning support, and local development capabilities*—major improvements over using pure Sphinx. • Hosting Flyte docs alongside Union docs reduces maintenance costs and simplifies infrastructure. • This transition allows us to improve documentation quality with more frequent updates and enhancements. We’re excited about the improvements this will bring, and you can expect to see major upgrades soon! 🚀 Let us know if you have any questions. Thanks for being part of the Flyte community!

I know you guys already pulled the trigger, but without redirecting to the new docs pages a lot of links (both indexed by search engines) & ones we have pinned internally are broken. Is there any chance parts of this could get remediated?

@busy-lawyer-8908 we are fixing most of these links, we had to do it, to find it

Please let us know which ones, @busy-lawyer-8908? We have redirected some 2-3k links to make sure things continue to work but it seems we missed some... please help us ease the migration for everyone in the community. @powerful-gold-59386 who is capturing and addressing these pretty promptly

Looks like the ones that were broken have been fixed - thanks for the help here

Thank you for rechecking!