Hello everyone: We just went live with the Flyte docs integrated into a single site. • You can access the Flyte version of the docs with the drop down selector at the top of the page • We are be rolling out redirects from the old docs to the new to reduce the number of broken links out in the wild • All old docs content should be present in the new docs. In some cases outdated or redundant content has been reorganized and rewritten but the information should still be there. • The new single-site will enable the docs to be improved and kept up to date much more effectively than was possible before • The community will still be able to contribute. We will be opening up the docs repo soon There will be some rough edges so please use this thread to report anything you may find. Thank you for your patience 🙂

I recently added to the equivalent to this page, will such commits be ported?

yes @cool-lifeguard-49380 cc @powerful-gold-59386

One of the things that steered us away from ClearML was their decision to move docs and features behind a paywall. This feels like a step towards a similar monetization strategy. Is there anything you can share about the long term plans for Flyte, as that impacts our decision to invest in the project.

@brainy-cartoon-98942 Flyte is open and will remain open. For a small team at Union.ai, we have to maintain the docs and this causes a lot of overhead for my team.

Respectfully, this reasoning doesn't hold water. You can unify your docs infrastructure without merging the docs into a single, company-controlled site. Maintaining separate doc sites does not inherently incur more overhead if they're built on a shared infra.

Hi, I'm the docs guy at Union.ai. It's not just about unifying infra. In fact it is mostly about making the docs maintainable. The relationship between Flyte and Union is pretty complex. A lot of the docs are common across the two, but with a lot of exceptions and special cases and so forth. And of course there are parts that only apply to one or the other

That's precisely the concern. Aligning Flyte docs so closely with Union's priorities effectively subordinates the open-source project. This makes it seem Flyte's future direction is being dictated by Union’s needs, rather than what's best for the community.

@worried-match-48212 how so?

And we will be open sourcing the docs (both Flyte and Union, since they are in the same repo) so the community contributions will still be possible.

We care about the community deeply and we think the only way to make it work is if we can maintain it more efficiently. Sadly, Union, has to bear the burden of maintaining and get complaints about the docs etc.

I understand Union maintains the docs, but optics matter - does this mean Flyte’s development is now mostly driven by Union alone? If Lyft or the community aren't actively involved, Flyte’s long-term viability does become a concern - it makes it harder for me to advocate for the project internally.

@worried-match-48212 I know you are S**** from metaflow - you did this in the past - I did not want to call it out, but I will share your identity if you do not stay off. Please do not use fake names and spread mis information

I think you are mistaken

I know 🙂

I'd imagine "advocating for the project internally" at Metaflow was a tough sell even before this change 🙂

> @worried-match-48212 : Respectfully, this reasoning doesn't hold water. You can unify your docs infrastructure without merging the docs into a single, company-controlled site. Maintaining separate doc sites does not inherently incur more overhead if they're built on a shared infra. I am unsure how you concluded this without any information about what was done and what was the previous status quo. Your reasoning is flawed and it is indeed more expensive to maintain multiple environments. As the one leading the project, I have first-hand knowledge of this project and can state, for a fact, that reducing both infra and human costs for creating, curating, and publishing/managing the content is precisely the tenets of this change. It took us considerable time and resources to make this change and we firmly believe this is in the best interest of the community by providing faster turnaround for documentation, and better content in the end (fresher, more content, and more polished.) And we are not done yet, and hope to keep improving the Flyte OSS developer experience. The community remains welcome to continue contributing to Flyte's documentation.