Trying out Promptless to translate and maintain helm's docs

[prithvi2206]

I was just chatting with @TerryHowe about trying out Promptless to help make it easier to maintain helm's docs. (I'm one of the founders, and a helm user.)

It seemed like this would be helpful for (1) maintaining translations of the docs in all the languages in i18n (sounds like this is the biggest pain point), and (2) detecting doc updates in general when PRs are opened in the helm/helm repo.

If you want to see how it works, we recently onboarded Vitess (another CNCF-graduated project), and you can see Promptless's commits in their docs repo in the last week.

Wanted to start a discussion about trying this out!

[TerryHowe]

@scottrigby and @paigecalvert with this approach, the English documentation would be the source of truth and the other documentation would be automatically updated.

[TerryHowe]

The human approach https://crowdin.com/page/open-source-project-setup-request which might be a good way to get reviews of the work.

[paigecalvert]

Hi @prithvi2206, thanks for reaching out and glad that you and Terry were able to chat. I'd definitely be interested to learn more about Promptless and how it could help keep the Helm docs up to date.

Would the next step be to schedule a demo?

[scottrigby]

Curious about the promptless. We had discussed Crowdin earlier, but didn't come to conclusions yet (I don't think? @paigecalvert, do you recall where we left off with that?).

I know Paige is working with CNCF docs folks and other projects on current processes for i18n maintainability. I like the idea of us trying things out in some kind of coordination and feedback loop along with the other CNCF docs folks and project docs maintainers. It's clearly a pain point we should put effort into addressing - specifically enabling contributors to help with this in ways that are maintainable.

I think one important criterion should be that each commit should help end users more than it's potential to confuse them. The rest of the criteria – eg, to balance contribution experience with maintainability – i think can be qualitative as we experiment.

[paigecalvert]

We had discussed Crowdin earlier, but didn't come to conclusions yet (I don't think? @paigecalvert, do you recall where we left off with that?)

@scottrigby I also recall that we briefly discussed Crowdin after seeing it in the Docusaurus docs, but I think it only amounted to noting it as a potential option for the future versus having any specific action items.

[prithvi2206]

Hi @paigecalvert sorry for the delay! I missed the comment tagging notification. You can use this link to schedule a quick demo with us here: https://cal.com/team/promptless/30m-all

[paigecalvert]

Hi @prithvi2206 , we (me, Terry, and Scott) just booked a 30 min time slot with you at 2pm mountain time tomorrow. talk to you then!