Congrats on the launch! Would love to chat sometime on getting a Mintlify integration going.
Thanks! Some of our early customers use Mintlify (we're big fans), which is an easy integration since there's always a Github sync. Let's chat soon!
Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
21–30 of 62 posts
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#22This is awesome! If you email me (greg@readme.io), we should do something together!
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#23Very needed! I’ve worked on platform teams and API docs were always rushed last second to push out a release—-but in many ways they are the product.
Another pain point was creating guides/examples for integrating 3rd party tools. Could be worth exploring
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#24This is awesome! If you email me (greg@readme.io), we should do something together!
Will do Greg!
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#25Very needed! I’ve worked on platform teams and API docs were always rushed last second to push out a release—-but in many ways they are the product. Another pain point was creating guides/examples for integrating 3rd party tools. Could be worth exploring
For sure. It can be challenging to inculcate a culture of treating docs as a product, but since great docs can drive revenue growth and bad docs can increase churn, it's a very important mindset.
In terms of creating guides/examples for third-party tools, do you have a particular use-case in mind? e.g. if you're something like Zapier with hundreds of connections?
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#26I'm curious, does it get triggered when a PR is opened or when it is merged? Because if it is when it is opened, updates to the PR could still get made which I assume would cause updates to the doc changes. Also, what if 2 PRs are opened at the same time? What if a PR is opened but never merged?
Great questions! It is possible to get Promptless to run only when PRs are merged, or when commits are made on `main`, but pretty much everyone wants the doc updates to be drafted when PRs are opened, because they'd like to review the doc updates in parallel (i.e. before it's actually released). If two PRs are created at the same time, Promptless will review them separately (and potentially create two docs PRs, if bo…
Why not have a flow that automatically adds/updates stuff to the PR itself?
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#27Earlier quoted context omitted.
Great questions! It is possible to get Promptless to run only when PRs are merged, or when commits are made on `main`, but pretty much everyone wants the doc updates to be drafted when PRs are opened, because they'd like to review the doc updates in parallel (i.e. before it's actually released). If two PRs are created at the same time, Promptless will review them separately (and potentially create two docs PRs, if bo…
Why not have a flow that automatically adds/updates stuff to the PR itself?
If you're asking about when there are new commits on the source code after a PR is opened, yes that's what happens! It just updates the existing docs branch.
If you're asking if Promptless should just add doc updates to the same PR as the code PR, that's definitely an option, but people tend to just want them separate both because it fits better with their workflows and it's less contingent on CI/CD processes, if that makes sense.
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#28Very needed! I’ve worked on platform teams and API docs were always rushed last second to push out a release—-but in many ways they are the product. Another pain point was creating guides/examples for integrating 3rd party tools. Could be worth exploring
For sure. It can be challenging to inculcate a culture of treating docs as a product, but since great docs can drive revenue growth and bad docs can increase churn, it's a very important mindset. In terms of creating guides/examples for third-party tools, do you have a particular use-case in mind? e.g. if you're something like Zapier with hundreds of connections?
Re: 3rd party integrations, think glue code for enterprise platforms (I previously worked on the developer platform at Shopify).
For example, a guide to integrate Shopify's Storefront API with Sanity CMS. These are usually a marketing/product thing more than developer docs... and almost always become obsolete after the next release and forgotten about.
Would've loved to generate a bunch of these guides and then automatically keep them up-to-date with code examples, and help serve both purposes for growth and developer docs.
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#29Aside, but what do you recommend for internal docs? Particularly if your internal docs are all Markdown?
Hmm, are you thinking about this in the context of, say, code documentation in Github repos, like README.md files? Or are there types of internal docs that you typically see in markdown?
Re: Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
#30Earlier quoted context omitted.
For sure. It can be challenging to inculcate a culture of treating docs as a product, but since great docs can drive revenue growth and bad docs can increase churn, it's a very important mindset. In terms of creating guides/examples for third-party tools, do you have a particular use-case in mind? e.g. if you're something like Zapier with hundreds of connections?
Re: 3rd party integrations, think glue code for enterprise platforms (I previously worked on the developer platform at Shopify). For example, a guide to integrate Shopify's Storefront API with Sanity CMS. These are usually a marketing/product thing more than developer docs... and almost always become obsolete after the next release and forgotten about. Would've loved to generate a bunch of these guides and then autom…
Yes, absolutely! Someone mentioned a similar situation where they had 100+ integration-specific landing pages in webflow (mostly for SEO) that became stale within months.
Definitely would love to pick your brain more about this if interested. prithvi@gopromptless.ai